|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
We currently managed all of our feature branches through the usage of our Job DSL scripting (which we are peeking at the Workflow plugin set for a next revision of that). What our one-off jobs allow for is to have changesets built that don't exist on our central server. This allows for developers to get some CI system time on their changeset without having to create a specific branch and job for their feature. Just to give a view of scale here, if we had to create a branch build for every story we have in flight, we would have over 200 branch build for just one of our projects. Currently we restrict our branch builds to project teams, which still is around 30.
Anyways, if being able to "hide" or disable this warning is difficult or not in the direction you want to take, no worries there. We have been thinking of writing a script that parses out and removes that warning from the logs via a cron script. That way it can still be generated but we can throw it away since it is noise for us, but maybe not for others.