Description

When defining a project with no update on launch and scm branch overrides enabled, the  project synchronization jobs are hidden from the interface (2.4) and will happen to perform a full project clean followed by the expected switch to either a branch, a commit or a tag.

Depending on the complexity of the repository itself this can be an "invisible" operation or a significant number of calls that can put performance strains on the git host especially when transitioning to a tag instead of a branch.

This synchronization operation will be executed each time the job template is executed making testing features a very expensive operation.

To reduce the number of operations we could use an additional option on the project configuration to keep branch overrides as separate directories with an expiration date like the Cache Timeout for "Update Revision on Launch", this can avoid having to switch target each time a override is needed.

Why the customer need this

Testing multiple branches and tags for features dramatically increase the strain on the git host slowing down even other operations.