!19 Lane board: lead with the runs where the lane could leave jobs out merged · by yy5652-hash · 2026-10-18 20:45 UTC · on GitLab
latest child pipeline 2960842228 · success · 1 pipeline on this merge request
8 of 9 GitLab DevSecOps stages with evidence for this merge request
lit: evidence for the merge request, click it ran and failed no evidence
- plan
- the merge request closes no issue
- create
- !19, opened by yy5652-hash 2026-10-18 20:45 UTC
1 commit by people 2026-10-18 20:45 UTC - verify
- lint-api · test-api · build-web · docs-links · flow-lint 2026-10-18 20:55 UTC
- package
- build-image 2026-10-18 20:55 UTC
- secure
- secret-detection · sast · dependency-scan · iac-scan · container-scan 2026-10-18 20:55 UTC
- release
- deploy-review, staged at mr-19---greenlane-demo-37vmav4mla-lz.a.run.app 2026-10-18 20:55 UTC
deploy-cloud-run on the default branch 2026-10-18 20:58 UTC - configure
- config-drift on the default branch 2026-10-18 20:58 UTC
- monitor
- scheduled monitor passed after the deploy, pipeline 2960977561 2026-10-18 22:25 UTC
- govern
- govern: no agent commits in this change 2026-10-18 20:55 UTC
The jobs of the latest pipeline
13 s
13 s
13 s
10 s
12 s
13 s
18 s
28 s
12 s
43 s
32 s
20 s
44 s
ran skipped failed fixed by the Lane Mechanic · width by the seconds the note charged, never narrower than its name
Staging
https://mr-19---greenlane-demo-37vmav4mla-lz.a.run.app: this merge request's image as its own Cloud Run revision with no production traffic, checked with real requests by deploy-review. The address was taken down when the merge request was merged.
What happened, to the second (UTC, 2026-10-18)
Every point is a commit or a pipeline from the public API; the person's commits are white, the Lane Mechanic's green.
The agents
Lane Steward read the real diff, the pipeline and the job logs and posted its verdict on the merge request.
The agents' audit (govern, success): no agent commits in this change. Carbon budget: no budget (the merge request closes no issue).
The carbon note, from the carbon-account job
| job | ran | seconds | g CO2e | why |
|---|---|---|---|---|
| build-image | yes | 43 | 0.062 | services/api/lane-snapshot.json (api); services/api/lane_board.py (api) |
| build-web | yes | 13 | 0.019 | full run |
| container-scan | yes | 32 | 0.046 | services/api/lane-snapshot.json (api); services/api/lane_board.py (api) |
| dependency-scan | yes | 28 | 0.040 | full run |
| deploy-review | yes | 44 | 0.063 | follows build-image |
| docs-links | yes | 10 | 0.014 | full run |
| flow-lint | yes | 12 | 0.017 | full run |
| govern | yes | 20 | 0.029 | always runs |
| iac-scan | yes | 12 | 0.017 | full run |
| lint-api | yes | 13 | 0.019 | services/api/lane-snapshot.json (api); services/api/lane_board.py (api) |
| sast | yes | 18 | 0.026 | services/api/lane-snapshot.json (api); services/api/lane_board.py (api) |
| secret-detection | yes | 13 | 0.019 | always runs |
| test-api | yes | 13 | 0.019 | services/api/lane-snapshot.json (api); services/api/lane_board.py (api) |
the job log · the summary line: This pipeline: 0.43 g CO2e. Running everything would have been about 0.389 g, so about -11 % was avoided (0 runner-seconds).