VersionControl:PRs/magenta/445: Difference between revisions
From PickiPedia: A knowledge base of bluegrass, old time psychedelic jams, and other public domain music
Jump to navigationJump to search
cryptograss/magenta#445, as GitHub has it |
cryptograss/magenta#445, as GitHub has it |
||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
|url=https://github.com/cryptograss/magenta/pull/445 | |url=https://github.com/cryptograss/magenta/pull/445 | ||
|author=magent-cryptograss | |author=magent-cryptograss | ||
|state= | |state=merged | ||
|base=main | |base=main | ||
|branch=magent/ramp-tests | |branch=magent/ramp-tests | ||
|opened=2026-11-09 04:20:14 | |opened=2026-11-09 04:20:14 | ||
|pushed=2026-11-09 04:19:59 | |pushed=2026-11-09 04:19:59 | ||
|merged= | |merged=2026-11-09 10:51:42 | ||
|closed= | |closed= | ||
|worked_on_by=magent, justin, re | |worked_on_by=magent, justin, re | ||
| Line 16: | Line 16: | ||
|deploy=redeploy maybelle | |deploy=redeploy maybelle | ||
}} | }} | ||
<pre class="pr-body">Red and green on the ramp (Plan, section 11). Each open row gets a badge for its head commit's newest `branch-tests` run, linking to that run's console: | |||
- **✓ tests** | |||
- **✗ tests** | |||
- **… testing** | |||
- **no ci/test**, for a repository without one yet | |||
**Where the results come from:** Jenkins' public API (`/job/branch-tests/api/json`, read anonymously), keyed by the REPO and COMMIT each run was given. The results are kept for 30 seconds. If Jenkins doesn't answer, the row just has no badge, and the page isn't slowed down. | |||
`JENKINS_URL` defaults to `https://maybelle.cryptograss.live`, so this needs no deploy change. | |||
**Checked against the real Jenkins from hunter:** it reads the three runs so far, #1 to #3, all passed. One of them is this repository's first branch test, #3, for #444: 1800 tests OK on the agent. | |||
**What gets a badge:** only work that went through githouse, because githouse is what triggers the tests. A pull request pushed straight to GitHub has no run, so it has no badge until its branch is pushed to githouse. | |||
Tests: 3 new (the newest run of each commit; cached, and Jenkins down means no runs; items get their head's run). Full suite: 1801 tests, OK. | |||
Deploy: redeploy maybelle | |||
Worked on by: magent, justin, re, in #ramp</pre> | |||
Latest revision as of 16:06, 9 November 2026
| State | 🟣 merged 2026-11-09 10:51:42 |
|---|---|
| Worked on by | magent, justin, re |
| Moods | #ramp |
| Deploy | redeploy maybelle |
| Branch | magent/ramp-tests → main, by magent-cryptograss
|
| Opened · last pushed | 2026-11-09 04:20:14 · 2026-11-09 04:19:59 |
Red and green on the ramp (Plan, section 11). Each open row gets a badge for its head commit's newest `branch-tests` run, linking to that run's console: - **✓ tests** - **✗ tests** - **… testing** - **no ci/test**, for a repository without one yet **Where the results come from:** Jenkins' public API (`/job/branch-tests/api/json`, read anonymously), keyed by the REPO and COMMIT each run was given. The results are kept for 30 seconds. If Jenkins doesn't answer, the row just has no badge, and the page isn't slowed down. `JENKINS_URL` defaults to `https://maybelle.cryptograss.live`, so this needs no deploy change. **Checked against the real Jenkins from hunter:** it reads the three runs so far, #1 to #3, all passed. One of them is this repository's first branch test, #3, for #444: 1800 tests OK on the agent. **What gets a badge:** only work that went through githouse, because githouse is what triggers the tests. A pull request pushed straight to GitHub has no run, so it has no badge until its branch is pushed to githouse. Tests: 3 new (the newest run of each commit; cached, and Jenkins down means no runs; items get their head's run). Full suite: 1801 tests, OK. Deploy: redeploy maybelle Worked on by: magent, justin, re, in #ramp