-
Notifications
You must be signed in to change notification settings - Fork 6
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 ignored on secrets repo updates and builds are triggered twice #74
Comments
o-orand
added a commit
that referenced
this issue
Jan 12, 2018
`secrets-full-writer` is a new shared resource used by all jobs to commit any changes to the `secrets` repository. We hopes we can share the same resource across jobs. closes #74
o-orand
added a commit
that referenced
this issue
Jan 12, 2018
`secrets-full-writer` is a new shared resource used by all jobs to commit any changes to the `secrets` repository. We hopes we can share the same resource across jobs. closes #74
o-orand
added a commit
that referenced
this issue
Jan 12, 2018
…tency job Fixes concourse error: `jobs.enforce-terraform-cf-consistency has get steps with the same name: secrets-full-writer` related to #74
lucaspinto
pushed a commit
that referenced
this issue
Jul 11, 2018
`secrets-full-writer` is a new shared resource used by all jobs to commit any changes to the `secrets` repository. We hopes we can share the same resource across jobs. closes #74
lucaspinto
pushed a commit
that referenced
this issue
Jul 11, 2018
…tency job Fixes concourse error: `jobs.enforce-terraform-cf-consistency has get steps with the same name: secrets-full-writer` related to #74
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems [skip ci] is ignored when a ressource is updated with a
put
.According to Concourse doc and git resource:
"A build can produce a new version of a resource by running a put step. This version is automatically detected and becomes available in later build steps and later pipeline jobs."
"Note that if you want to push commits that change these files via a put, the commit will still be "detected", as check and put both introduce versions. To avoid this you should define a second resource that you use for commits that change files that you don't want to feed back into your pipeline - think of one as read-only (with ignore_paths) and one as write-only (which shouldn't need it)."
The text was updated successfully, but these errors were encountered: