Replies: 2 comments 2 replies
-
@MMarus unfortunately, it is not possible to pin the image version for a pipeline. But we keep working on speeding up the deployment process to reduce the timeframe when images are different. We receive such issues in this repo from time to time, so we know this long deployment drawback. We have the idea of storing one previous image that can be selected in critical moments when a pipeline is failing and the customer doesn’t have time to fix it right now, but no ETA for now, it is something that we’d like to have in the future. |
Beta Was this translation helpful? Give feedback.
-
I've run into an issue where pinning the runner version would be useful #4241 |
Beta Was this translation helpful? Give feedback.
-
In azure pipelines, we can specify the ubuntu version e.g.:
pool:
vmImage: ubuntu-20.04
However, we are getting a different version of the agent in different stages (the first stage uses Image Version: 20210517.1, and the second stage uses Image Version: 20210524.1)
Is there any possibility to specify also the version of the image, so that we avoid having different versions in different stages?
This is a big problem, for example when we try to do terraform plan in 1st stage and in the 2nd terraform apply. This fails because the versions of terraform are also different.
Beta Was this translation helpful? Give feedback.
All reactions