Currently when using promotion all repository revisions are fetched from original build and used in new one when checking out repositories. We'd like to make this behavior optional (checkbox in promotion maybe?).
Scenario:
We have "rebuild" promotion to rerun build with some variables changed - one is 'tools repository' branch name. We use this promotion for confirmation if changes on tools test branch are working correctly with latest configuration. With current approach this variable is ignored and repository is checked out with same revision as in original build. We have to start build normally and copy-paste all other prompted variables, or use workaround described below.
Workaround:
In Pre-queue script we are setting all repositories revisions to null. Snippet below
groovy: repositories.getAll().each { it.setRevision(null) }
Description
Currently when using promotion all repository revisions are fetched from original build and used in new one when checking out repositories. We'd like to make this behavior optional (checkbox in promotion maybe?).
Scenario:
We have "rebuild" promotion to rerun build with some variables changed - one is 'tools repository' branch name. We use this promotion for confirmation if changes on tools test branch are working correctly with latest configuration. With current approach this variable is ignored and repository is checked out with same revision as in original build. We have to start build normally and copy-paste all other prompted variables, or use workaround described below.
Workaround:
In Pre-queue script we are setting all repositories revisions to null. Snippet below
groovy: repositories.getAll().each { it.setRevision(null) }