cloudfoundry / cloudfoundry/cf-deployment-concourse-tasks
build-docker-image job runs twice every time
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 24
- Forks
- 76
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 1
Description
Every time the build-docker-image job is triggered by a dependency update, the pipeline will push an updated dockerfile to the repo which will actually re-trigger the pipeline again.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the build-docker-image job and the pipeline build linked in the issue, then trace how a dependency update causes the Dockerfile commit and subsequent trigger. Confirm the fix by verifying that one dependency update produces one Dockerfile push and does not start the job again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- build-system, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100