Pulling latest VCS version in downstream step of build chain
I have three steps in a snapshot dependency build chain. Step C commits and pushes a change to another VCS N. Any concurrent builds running the same chain will have already locked their VCS revisions at the start of the chain, such that they will hit a merge error when they reach step C and try to push to the VCS. This could be avoided if I could configure step VCS N to be exempted from revision locking, such that it would pull the latest rather than locking in the revision when the chain starts. Is this possible? I know I can accomplish this by taking step C out of the build chain, but then I lose the nice features of build chains that I am taking advantage of with VCS M.
VCS M -> A -> B -> C
Please sign in to leave a comment.
Hi Greg,
this isn't currently an option, but you can simply add a starting command line step that pulls the latest revision before continuing the tasks on C. Please note that this will not work if you are using the "Automatic Merge" feature, as it merges explicitly commit run through the chain. In that case you would need to not use automatic merge and run it on a script manually.
This said, if you would like to have this as a feature, please fill a request in our tracker here: https://youtrack.jetbrains.com/issues/TW