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
Hello, I'd like to ask if it would be possible to introduce release tags.
We are using your image in our Jenkins running in Kubernetes cluster. Recent docker upgrade to 19.03.9 brings API version upgrade as well 1.39 -> 1.40. We needed to upgrade all our worker nodes to latest docker version immediately.
It would be good to stick with some version and plan the upgrade more in advance :-). I would be happy to help with maintenance.
The text was updated successfully, but these errors were encountered:
Thanks for raising this issue, good to see that the image is valuable for actual users :)
I must confess that it was not intended to have the antique docker version in the image for so long. The idea was to be always up to date with docker, docker-compose and jenkins.
On the other hand I did not anticipate that the update would break anything, I am really sorry for that.
I am not sure how tagging could work out, since it would require a matrix of jenkins and docker versions. Do you have suggestions?
I would like to learn more how you use this image. Could you describe your setup esp. in combination with kubernetes and show an example pipeline?
Hello, I'd like to ask if it would be possible to introduce release tags.
We are using your image in our Jenkins running in Kubernetes cluster. Recent docker upgrade to 19.03.9 brings API version upgrade as well 1.39 -> 1.40. We needed to upgrade all our worker nodes to latest docker version immediately.
It would be good to stick with some version and plan the upgrade more in advance :-). I would be happy to help with maintenance.
The text was updated successfully, but these errors were encountered: