You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 0f4d7fe
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,9 +21,9 @@
21
21
Jira issues, failed jobs.
22
22
23
23
For every service it reads the latest successful production deployment, walks the default branch down to that
24
-
commit, and writes a static site with one JSON report: a row per merge request or direct commit, newest first, with the tags that
25
-
point into it, the environments running it, the Jira keys its MR mentions, and the failed jobs of its main-branch
26
-
and tag pipelines. With a Jira token, it also reads the summary and status of every key in one batched search,
24
+
commit, or down to its first commit when the service was never deployed to production, and writes a static site with
25
+
one JSON report: a row per merge request or direct commit, newest first, with the tags that point into it, the
26
+
environments running it, the Jira keys its MR mentions, and the failed jobs of its main-branch and tag pipelines. With a Jira token, it also reads the summary and status of every key in one batched search,
27
27
and the GitLab merge requests and commits linked to each issue. GitLab's Jira integration adds those links to the
28
28
issue's Web links whenever a commit or MR mentions it; a link counts only if it starts with
29
29
`RELEASE_SCOPE_GITLAB__ENDPOINT`. The projects they point to are the issue's related services.
@@ -87,7 +87,8 @@ The report is versioned by `schema_version`; the models live in
87
87
Top-level `jira` is `null` without a Jira token; otherwise it holds `issues` by key (summary, status, status category,
88
88
issue type, linked GitLab changes), the `missing` keys Jira did not return, and an `error` if a Jira request failed.
89
89
Each service lists its `candidates`: the tags a release could ship, newest first, each with its pipeline, the number of
90
-
rows it ships, the in-scope Jira keys of those rows, and the compare link from production. One row, trimmed:
90
+
rows it ships, the in-scope Jira keys of those rows, and the compare link from production, or the tag's commit history
91
+
when the service has no production deployment. One row, trimmed:
91
92
92
93
```json
93
94
{
@@ -107,14 +108,14 @@ Besides `report.json`, `collect` writes `index.html` and its script into the out
107
108
installed package and change only with it, so the page always matches the report schema. The page loads
108
109
`report.json` from next to itself; it needs a web server, not a `file://` URL.
109
110
110
-
**Services** lists every service with a production deployment, and every service that failed to collect, as one
111
-
line: what production runs, the picked tag, how many merge requests or commits and Jira tasks it ships, failed jobs
111
+
**Services** lists every service with a production deployment or with rows, and every service that failed to collect,
112
+
as one line: what production runs, the picked tag, how many merge requests or commits and Jira tasks it ships, failed jobs
112
113
with the ones allowed to fail counted apart, and a mark when the range was cut at `RELEASE_SCOPE_MAX_COMMITS`.
113
114
Opening a line shows the service's environments, warnings, merge requests that are not merged yet, and its rows with
114
115
tags and their pipelines, merge requests or commits, Jira keys with their status, environments, and failed jobs; rows
115
116
out of scope are dimmed. Links open in a new tab. Each tag has a **pick** button:
116
117
picking it highlights the rows it ships and closes the line again. A `--jira` report starts with each service's
117
-
release tag picked. Services without a production deployment are left out of the page.
118
+
release tag picked. Services with neither a production deployment nor rows are left out of the page.
118
119
119
120
The address keeps the picks after `#`, as `team/api=2.4.0&team/web=5.12.0`, so sharing or reloading the page keeps
120
121
them. An address with picks replaces the release tags of a `--jira` report; picks that are not in the report, such as
@@ -128,7 +129,8 @@ text box to copy from by hand, since browsers allow the copy button only over HT
128
129
summary and a status badge: grey to do, blue in progress, green done. Copy them one per line or as a JQL
129
130
`key in (...)` clause, each in its own box.
130
131
-**Tag pipelines**: the pipeline of each picked tag, as a Markdown list.
131
-
-**Compare**: a GitLab compare link per service from production to the picked tag, as a Markdown list.
132
+
-**Compare**: a GitLab compare link per service from production to the picked tag, as a Markdown list. A service
133
+
never deployed to production gets the commit history of the tag instead.
132
134
-**Release post**: one Markdown text with a line per picked tag, holding its compare link and pipeline, followed by
<px-show="pickable.length" class="muted">Open a service and pick the tag to release: it ships every merge request and commit from its row down to production. The address keeps the picks, so share it to share them.</p>
0 commit comments