Browse Source

Add rdoproject gerrit example

Change-Id: I41288260b5faee27397cc55d1df4fc7e0f704ad7
Matthias Runge 2 years ago
parent
commit
449fe4605b
1 changed files with 135 additions and 0 deletions
  1. 135
    0
      examples/rdo-gertty.yaml

+ 135
- 0
examples/rdo-gertty.yaml View File

@@ -0,0 +1,135 @@
1
+# This is an example ~/.gertty.yaml file for use with OpenStack's
2
+# Gerrit.  Most of these options are not required, rather, they
3
+# customize Gertty to better deal with the particulars of OpenStack's
4
+# Gerrit configuration.
5
+
6
+# This file does not list all of the available options.  For a full
7
+# list with explanations, see the 'reference-gertty.yaml' file.
8
+
9
+servers:
10
+  - name: rdo
11
+    url: https://review.rdoproject.org/
12
+    # Your gerrit username.
13
+    username: CHANGEME
14
+    # Set password at https://review.rdoproject.org/r/#/settings/http-password
15
+    # Note, this is not the password for your ID provider!
16
+    password: CHANGEME
17
+    git-root: ~/git/
18
+
19
+# This section adds the colors that we will reference later in the
20
+# commentlinks section for test results.  You can also change other
21
+# colors here.
22
+palettes:
23
+  - name: default
24
+    test-SUCCESS: ['light green', '']
25
+    test-FAILURE: ['light red', '']
26
+    test-UNSTABLE: ['yellow', '']
27
+
28
+# Uncomment the next line if your terminal has a white background
29
+# palette: light
30
+
31
+# Commentlinks are regexes that are applied to commit and review
32
+# messages.  They can be replaced with internal or external links, or
33
+# have colors applied.
34
+commentlinks:
35
+  # This matches the job results left by Zuul.
36
+  - match: "^- (?P<job>.*?) (?P<url>.*?) : (?P<result>[^ ]+) ?(?P<comment>.*)$"
37
+    # This indicates that this is a test result, and should be indexed
38
+    # using the "job" match group from the commentlink regex.  Gertty
39
+    # displays test results in their own area of the screen.
40
+    test-result: "{job}"
41
+    replacements:
42
+      # Replace the matching text with a hyperlink to the "url" match
43
+      # group whose text is the "job" match group.
44
+      - link:
45
+          text: "{job:<42}"
46
+          url: "{url}"
47
+      # Follow that with the plain text of the "result" match group
48
+      # with the color "test-{result}" applied.  See the palette
49
+      # section above.
50
+      - text:
51
+          color: "test-{result}"
52
+          text: "{result} "
53
+      # And then follow that with the plain text of the "comment"
54
+      # match group.
55
+      - text: "{comment}"
56
+  # Match Gerrit change ids, and replace them with a link to an
57
+  # internal Gertty search for that change id.
58
+  - match: "(?P<id>I[0-9a-fA-F]{40})"
59
+    replacements:
60
+      - search:
61
+          text: "{id}"
62
+          query: "change:{id}"
63
+  # Match external references to bugs on Launchpad
64
+  - match: "(?P<bug_str>(?:[Cc]loses|[Pp]artial|[Rr]elated)-[Bb]ug *: *#?(?P<bug_id>\\d+))"
65
+    replacements:
66
+      - link:
67
+          text: "{bug_str}"
68
+          url: "https://bugzilla.redhat.com/{bug_id}"
69
+# This is the query used for the list of changes when a project is
70
+# selected.  The default is "status:open". If you don't want to see
71
+# changes which are WIP or have verification failures, use a query like this:
72
+# change-list-query: "status:open not label:Workflow=-1"
73
+
74
+# If you also want to exclude reviews with failed tests, the query is slightly
75
+# more complex:
76
+# "status:open not (label:Workflow=-1 or label:Verified=-1)"
77
+
78
+# Uncomment the following line to use a unified diff view instead of the
79
+# default side-by-side:
80
+# diff-view: unified
81
+
82
+# Hide comments by default that match the following criteria.
83
+# You can toggle their display with 't'.
84
+hide-comments:
85
+  - author: "^(.*CI|Jenkins)$"
86
+
87
+# This section defines customized dashboards.  You can supply any
88
+# Gertty search string and bind them to any key.  They will appear in
89
+# the global help text, and pressing the key anywhere in Gertty will
90
+# discard the current display stack and replace it with the results of
91
+# the query.
92
+#
93
+# NB: "recentlyseen:24 hours" does not just return changes seen in the
94
+# last 24 hours -- it returns changes seen within 24 hours of the most
95
+# recently seen change.  So you can take the weekend off and pick up
96
+# where you were.
97
+dashboards:
98
+  - name: "My changes"
99
+    query: "owner:self status:open"
100
+    key: "f2"
101
+  - name: "Incoming reviews"
102
+    query: "is:open is:reviewer"
103
+    key: "f3"
104
+  - name: "Starred changes"
105
+    query: "is:starred"
106
+    key: "f4"
107
+  - name: "Recently seen changes"
108
+    query: "recentlyseen:24 hours"
109
+    sort-by: "last-seen"
110
+    reverse: True
111
+    key: "f5"
112
+
113
+# Reviewkeys are hotkeys that perform immediate reviews within the
114
+# change screen.  Any pending comments or review messages will be
115
+# attached to the review; otherwise an empty review will be left.  The
116
+# approvals list is exhaustive, so if you specify an empty list,
117
+# Gertty will submit a review that clears any previous approvals.
118
+# They will appear in the help text for the change screen.
119
+reviewkeys:
120
+  - key: 'meta 0'
121
+    approvals: []
122
+  - key: 'meta 1'
123
+    approvals:
124
+      - category: 'Code-Review'
125
+        value: 1
126
+  - key: 'meta 2'
127
+    approvals:
128
+      - category: 'Code-Review'
129
+        value: 2
130
+  - key: 'meta 3'
131
+    approvals:
132
+      - category: 'Code-Review'
133
+        value: 2
134
+      - category: 'Workflow'
135
+        value: 1

Loading…
Cancel
Save