Skip to content
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

Closed
o-orand opened this issue Jan 12, 2018 · 0 comments · Fixed by #75
Closed

[skip ci] is ignored on secrets repo updates and builds are triggered twice #74

o-orand opened this issue Jan 12, 2018 · 0 comments · Fixed by #75
Labels
Milestone

Comments

@o-orand
Copy link
Member

o-orand commented Jan 12, 2018

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)."

@o-orand o-orand added the bug label Jan 12, 2018
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
@o-orand o-orand added this to the 1.8.0 milestone Jan 17, 2018
o-orand added a commit that referenced this issue Feb 7, 2018
We use same principle used in #74: a secrets resource dedicated to write
 operations.

Fixes #94
o-orand added a commit that referenced this issue Feb 7, 2018
We use same principle used in #74: a secrets resource dedicated to write
 operations.

Fixes #94
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
lucaspinto pushed a commit that referenced this issue Jul 11, 2018
We use same principle used in #74: a secrets resource dedicated to write
 operations.

Fixes #94
@o-orand o-orand moved this to Done in CF OPS Automation Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant