scmuser created the topic: Hudson with Subversion
A basic question about Hudson and Subversion when having many branches
I have a trunk and many branches.
I want a single Hudson job to control all these things, instead of creating one job for each branch, not to mention the fact that the number of branches will increase in the future.
The most important thing is, when branch A is changed and updated, I want Hudson only to build branch A, not all branches and trunk.
In a word: how can I make Hudson discriminate which directory has been changed and run the corresponding script?
How to implement this?
mnanjala replied the topic: Re:Hudson with Subversion
Hello
You should use parameterized build which and you should later give as ${BRANCH} where ever you call respective branch…
- Use of runtime variables to save into another variable using register in Ansible - September 6, 2018
- Ansible & Ansible Tower Variable Precedence Hierarchy - September 6, 2018
- How to use template in Ansible? - September 6, 2018