search

concourse / semver-resource

automated semantic version bumping
Apache License 2.0
97 stars 105 forks source link

Intermittently Using Wrong Version #110

Open charlieoleary opened 4 years ago

charlieoleary commented 4 years ago

Hi,

Since we changed our Docker repository tags to be immutable I've noticed that intermittently Concourse / the semver resource will use the incorrect version between jobs in the pipeline. This ultimately leads to the build failing due to the tag being immutable. Here are some examples --

bump-version job starts and finishes successfully --

image

When we look at the job that includes the get for the version and the Docker build, we see that it's reusing the previous version --

image

Finally, when we look at the output itself, we see that the previous version (-rc.13) belongs to TWO builds, while (-rc.14) has no builds.

image

16239 is using the duplicate tag.

Any idea what the root cause could be here? Most builds finish without an issue, but we will have some that end up with this version collision and are (correctly) blocked from overwriting the tag.

taylorsilva commented 4 years ago

Sorry for the super late response!

This is pretty strange, I'm not sure why this would happen intermittently. Which driver are you using (s3, gcs, git)?

charlieoleary commented 4 years ago

No worries. It’s relatively rare and immutable gags prevents any unexpected changes fortunately. We are using S3 for our storage.

taylorsilva commented 4 years ago

I thought on this a bit but can't come up with any good theories. We'll leave this open and see if anyone else runs into this and has a reproducible case.

skreddy6673 commented 3 years ago

@charlieoleary @taylorsilva I'm also seeing the same issue, intermittently lately, just in couple pipelines.

Concourse Version: v6.5.1 Helm Chart: v 12.0.1 driver: git