v6.1.0 - tagged incorrectly in this repo - Concourse unable to track about concourse-bosh-deployment HOT 2 CLOSED

Here's what happened:

1. With v6.1.x we tweaked our release process so we always ship from release pipelines, rather than shipping releases that "roll forward" (i.e. latest -> latest) from our main pipeline.
2. Release pipelines have a bump-cbd-versions job which created 96dea55 on the release/x.x.x branch of this repo and tagged it as v6.1.0.
   • In the past, these commits have always been for non-latest releases, but this time it was for v6.1.0.
3. The master pipeline also has a bump-cbd-versions job, which triggers whenever a new release appears on bosh.io.
   • Normally, this job wouldn't fire when shipping from a release pipeline, because patch releases of older versions wouldn't trigger the job. In this case, a new 'latest' release was shipped, so it triggered the job in addition to the release pipeline's own 'bump' job.

So, when the main pipeline's bump-cbd-versions job triggered, it created and pushed 022e40a to master, but then it got stuck in a loop pushing the v6.1.0 tag because it already exists. The build ran in a loop for 3 days before finally failing.

It was tempting for me to say "just don't track the master branch - track all branches" but it turns out the order of the versions isn't exactly useful to track - it's chronologically sorted, not semver sorted:

...so, yeah, we'll look into fixing this. It's a little tricky. Maybe we just need to force-push the tag? 🤔

edit: maybe a better idea would be to merge the release/x.x.x branch in. 🤔

from concourse-bosh-deployment.

I've merged release/6.1.x into master, so the tag is there now! I'm going to close this issue and we'll have this flow sorted out for the next release. See concourse/concourse#5633 (comment) for details.

from concourse-bosh-deployment.