|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
"100% guaranteed bug free cleaning and zero work in maintaining it" - There is no free lunch. If these are your requirements, then yes, you are stuck using a full clean, but I still maintain that it's bad practice to rely on that. Your scripts/project files should all be cleaning up things properly, volatile or not.
If you don't want the old branches removed, then just put them all in your client spec and only build the branch you want. If you are worried about the additional sync time, then put the branch parameter in the View Mask, and select Use View Mask for Syncing.
"If we had to set up new jobs all the time it would be a constant maintenance headache." - I'd recommend using templates. I've currently got a system which reads a list of branches from source control, and automatically creates/updates the necessary jobs from a template. It's a heck of a lot more organized than cramming multiple branches into a single job.
The only issue I see with your solution is if you are using the same client for all branches. This is extremely bad practice, and frequently causes issues. So if you aren't already, I'd recommend adding your branch parameter to your client workspace name to avoid these issues.