CI concept: what runs when, and why #663
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung#663
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follows up #561 and #31. Absorbs the earlier idea of skipping the repeated full check after a merge; links
fast-release-tag-steps.md,pr-preview-images.md,signed-release-tags.md,lint-gaps.md,browser-test-layer.md,timing-bound-tests-async.md.Problem
The CI grew step by step, and one change now passes through more runs and gates than it needs:
push →
check-fast→ manual promote →check-full-promote→ merge →check-fullagain →build-and-publish(compiles the app forimage-tags) → tag →release(compiles the app again inrelease-files).check-fasthas become fast enough that its split fromcheck-fullmay no longer pay off.mix deps.getand compiles several times (lintin dev, the tests in test,image-tags,release-files), and the steps run one after another..drone.jsonnet), production runs 18.6 (docker-compose.prod.yml).concurrency: { limit: 1 }queues every repetition behind Renovate and other branches.Goal
Write down from scratch what should run on which event, with its reason, and map today's setup to it: keep, change or drop each part. Then implement it.
Principles (to agree on)
Proposed matrix (draft)
WIP:)fast-release-tag-steps.mddeps.auditQuestions to settle
pushandpull_requestfor it. Options: a first step in the push pipeline asks the Forgejo API for an open PR from this branch and ends the run withexit 78(successful skip); or branches get CI only through PRs.origin/mainbefore testing, or require branches to be up to date before merging (Forgejo branch protection).HEAD^{tree}), without trusting the shared cache.check-fastandcheck-full(Drone history) and decide whether one check with all tests is enough for every PR run.MIX_ENV; decide whetherwait_for_postgresanddeps.getrepeat per step.lint-gaps.md), browser tests (browser-test-layer.md), PR images (pr-preview-images.md), signed tags (signed-release-tags.md). Which of them belong in which row.Acceptance criteria
docs/ci.md) states the matrix, the reason for each row, and which status checks branch protection requires..drone.jsonnet, and every part of today's setup is either in the matrix or removed.mainimage, and from tag to draft release is measured before and after.