I’m using a pipeline like this and image tag change didn’t take affect.
--- resource_types: - name: jenkins type: docker-image source: repository: concourse-jenkins-resource tag: v1 resources: - name: jenkins-job type: jenkins source: host: jenkins.example.com job: /job/test jobs: - name: FetchResult plan: - get: jenkins-job
- I modify something then build and push concourse-jenkins-resource:v2
- Change pipeline tag from v1 to v2
- Using fly set-pipeline to update pipeline
- Manually trigger job FetchResult is still using v1
I think in step-4, it should running job FetchResult with v2. Did anyone hit the same issue? Or did I use it wrong?
Plus: The second time I manually trigger this job is working fine and using v2.