Changes on cancel-landed-runs touching .flow/pipeline.kdl · 19
See as swimlanes (independent work side by side)
cancel-landed-runs has 68 heads. The graph shows their union; heads are marked.
dist: release the hub server for Linux x86_64 on PostgreSQL
api-unknown-fieldscancel-landed-runsdiffusion-pin-bookmarkdraft-readyoh-comment-body-fileproposal-list-fastv0.6.0v0.6.1v0.7.0v0.8.0v0.9.0v0.9.1v0.9.11v0.9.15v0.9.2v0.9.3v0.9.4v0.9.5v0.9.6v0.9.7v0.9.8v0.9.9
head
Flow: the hub's tests on PostgreSQL too, in the new build image
cancel-landed-runsoh-comment-body-file
head
ci: one build identity for CI states, so cached targets stay fresh (refs andymccall/oxygenflow#52)
api-unknown-fieldscancel-landed-runsdiffusion-pin-bookmarkdraft-readymainoh-comment-body-fileproposal-list-fastv0.5.0v0.5.1v0.5.2v0.6.0v0.6.1v0.7.0v0.8.0v0.9.0v0.9.1v0.9.11v0.9.15v0.9.16v0.9.19v0.9.2v0.9.20v0.9.21v0.9.22v0.9.23v0.9.24v0.9.3v0.9.4v0.9.5v0.9.6v0.9.7v0.9.8v0.9.9
head
ci: keep each build job's target from its last passing run (refs andymccall/oxygenflow#28)
cancel-landed-runsoh-comment-body-filev0.5.0v0.5.1v0.5.2v0.6.0
head
Pin the build image with the coverage tools (7705d699). refs #113
clear-waitingclose-proposal-140image-checkjob-waitsrun-one-jobwiki-says-sov0.4.1v0.4.2
CI builds without debug info or incremental state
clear-waitingclose-proposal-140image-checkjob-waitsrun-one-jobwiki-says-sov0.1.0v0.2.0v0.3.0v0.3.1v0.4.0v0.4.1v0.4.2