Abort pipeline executions after artifacts are published in case of a new build is triggered - Githubissues

camunda / camunda-bpm-platform

Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Quarkus, Spring, Spring Boot, CDI.

https://camunda.com/

Apache License 2.0

4.11k stars 1.55k forks source link

Abort pipeline executions after artifacts are published in case of a new build is triggered #3023

Closed yanavasileva closed 1 year ago

yanavasileva commented 1 year ago

Acceptance Criteria (Required on creation)

In case of a new build is triggered, abort current pipeline execution after artifacts are published
Cover master and maintenance versions, main-ce and main-ee, Assembly and Distro-EE stages, non-PRs only

Hints

Links

part of https://github.com/camunda/camunda-bpm-platform/issues/2783

Breakdown

yanavasileva commented 1 year ago

Decision: With changes planned and made in #3021, #3022, and #3023, we find that will bring unnecessary complexity to add logic for milestones in assembly and distro-ee stage. We prefer now to abort fast, we can reevaluate if we find need to push the artifacts before aborting the builds.