-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[skip ci] is not respected for put #196
Comments
Is anyone working on this issue ? |
+1 for this. create another resource for that is also a waste, since it requires a further running container for each resource modified for each pipeline defined. nowadays it's a fairly common practice to have pipelines to update a version-pinning file (e.g. Pipfile.lock in pipenv/python world), I wouldn't consider it a corner use case. would this example work? https://stackoverflow.com/questions/42607033/how-to-commit-changes-to-git-in-concourse-build |
This issue is impossible to fix in the I've opened concourse/concourse#3463 so there's something more concrete to point to, but I'm going to close this again as there's nothing we can do on the |
Thanks @vito |
Commits with
[skip ci]
should not update version of the resource if disable_ci_skip is enabled.In case of pipeline like this:
gitrepo_resource -> GET -> something_doing_job -> PUT -> gitrepo_resource
The PUT updates the version and
something_doing_job
is triggered again.There is a workaround described in #18, however this makes pipeline messy and harder to read.
The text was updated successfully, but these errors were encountered: