You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Concourse tasks run on container images, declared with image_resource. When a new version of my task's image_resource is published, sometimes my task starts to fail because of a change in the image.
When that job fails, I have no indication that my build was broken by an update to the docker image.
What would make this better?
There is a workaround for this, it's just annoying and has a high up-front cost. The workaround is to explicitly declare every image used by my tasks as docker-image-resources and specify them as inputs to my job. Then I can look at the build view and see that a new version of my image was used for a given build.
I wish I automatically had some way to see in the build view when builds ran on a new image version. Task image_resources are actually resources, as their name suggests. They should appear in the build view in some way without me needing to explicitly specify them as pipeline inputs.
Are you interested in implementing this yourself?
Unfortunately, I don't have the bandwidth.
The text was updated successfully, but these errors were encountered:
andrewedstrom
changed the title
image_resource versions should be visible in the pipelineimage_resource versions should be visible in the build view
Mar 29, 2019
What challenge are you facing?
Concourse tasks run on container images, declared with
image_resource
. When a new version of my task'simage_resource
is published, sometimes my task starts to fail because of a change in the image.When that job fails, I have no indication that my build was broken by an update to the docker image.
What would make this better?
There is a workaround for this, it's just annoying and has a high up-front cost. The workaround is to explicitly declare every image used by my tasks as docker-image-resources and specify them as inputs to my job. Then I can look at the build view and see that a new version of my image was used for a given build.
I wish I automatically had some way to see in the build view when builds ran on a new image version. Task
image_resource
s are actually resources, as their name suggests. They should appear in the build view in some way without me needing to explicitly specify them as pipeline inputs.Are you interested in implementing this yourself?
Unfortunately, I don't have the bandwidth.
The text was updated successfully, but these errors were encountered: