apricote/releaser-pleaser
1
0
Fork 0
mirror of https://github.com/apricote/releaser-pleaser.git synced 2026-02-06 17:57:05 +00:00
Code Issues Projects Releases Packages Wiki Activity
releaser-pleaser/docs/explanation/concurrency-conflicts.md

2 lines
28 B
Markdown
Raw Normal View History

feat: run one job concurrenlty to reduce chance of conflicts Each run of releaser-pleaser acts on the same global state in the forge. Therefore parallel runs are unnecessary. This commit also communicates to the GitHub and GitLab CI pipelines that the releaser-pleaser jobs can be cancelled as early as possible. - On GitHub Actions this can be guaranteed through the workflow settings. These settings are copied into each repository that uses releaser-pleaser, so users need to update this manually. I will add a note to the release notes for this. - On GitLab CI/CD this requires the user to configure a project level setting to "auto-cancel redundant pipelines". We will not recommend user to set this, as it is quite invasive and can break their regular CI pipelines.
2025-06-14 13:32:25 +02:00
# Concurrency and Conflicts
Reference in a new issue Copy permalink