Multiple drafts created due to GH workflow concurency

[lemeurherve]

From release-drafter/release-drafter#1146

On the Jenkins infrastructure project, we've hit a reproductible case where we have multiple times the same draft created by release-drafter, while we have fixed the tag and release name to the static value next.

There are multiple causes that make it an "edge" case:

we define a static name for the "draft next release" so we expect only 1 at a given time
Jenkins is publishing the draft release to a given tag version, which is a parallel process to the Github workflow builds
we have the release: trigger event for release-drafter's workflow (we have a new "next release draft" published right after Jenkins publishing a given release)

In our case, since we "patch" the release, there are 3 events triggering 3 concurent builds of the GH workflow: it results in 3 different "next release draft":

We are thinking, in the short term, to enable the "concurency" feature of GH action (docs.github.com/en/actions/using-jobs/using-concurrency) so only 1 release-drafter job would be executed at once, streamlining the executions. The 2nd and 3rd builds in our case should pick the previous next release because executed AFTER.

Related:

• buildDockerAndPublishImage fails at GitHub Release stage if there are more than one "next" draft releases pipeline-library#379
• fix: retrive only the last "next" draft release id pipeline-library#380
• fix: retrieve only last next release draft jenkins-maven-cd-action#21