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
Currently concourse prod ci is using same windows worker for running both dev and releasing tasks. If the concourse dev version advanced e.g from 4.2.2 to 5.0.0, the dependencies on the windows worker also got updated eg golang 1.14.2 to 1.14.4.
However if there is an issue of 4.2.2 and a patch release is needed, one would have to manually revert the dependencies back for running releasing tasks of 4.2.2 again, which could potentially block the dev work of 5.0.0 and slow down the releasing of the patch.
What would make this better?
A separate windows worker that holds the dependencies of 4.2 (or last released version)
The text was updated successfully, but these errors were encountered:
What challenge are you facing?
Currently concourse prod ci is using same windows worker for running both dev and releasing tasks. If the concourse dev version advanced e.g from 4.2.2 to 5.0.0, the dependencies on the windows worker also got updated eg golang 1.14.2 to 1.14.4.
However if there is an issue of 4.2.2 and a patch release is needed, one would have to manually revert the dependencies back for running releasing tasks of 4.2.2 again, which could potentially block the dev work of 5.0.0 and slow down the releasing of the patch.
What would make this better?
A separate windows worker that holds the dependencies of 4.2 (or last released version)
The text was updated successfully, but these errors were encountered: