Start e2e alongside build rather than after it #121
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!121
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-e2e-alongside-build"
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?
Part of #77.
Today's
action_run_jobdata showsbuildande2eeach take about 4.7 min.e2ewaited forbuild(needs: build) even though the suite builds from source and never uses the images, so every PR's gate was a chain of about 10 min.e2ehas noneedsnow, so it starts immediately on PRs and onmain.promotehasneeds: [build, e2e]. It's the only step that uses the published:<sha>, so the guarantee that the image exists before it's retagged is kept where it matters.mainthis also brings:stableforward by about 5 min.The cost: a PR whose build fails (on lint, for example) still spends a runner slot on e2e. Check names are unchanged, so the protection rule is unaffected.
This PR's own run should show
e2estarting at the same time asbuild.Changelog
NONE
🤖 Generated with Claude Code
https://claude.ai/code/session_01StURdiv33xnMfE2XRyg8Lt