1) job per branch is a git plugin/jenkins core issue - feel free to propose good design for handling them and then back to github-plugin. Note, this topic was discussed many times and it is known that build configuration may differ per branches, that's why everybody propose to use "job-dsl?" and store configuration in git.
2) Exposing payload data is the way to not using jenkins/plugin features at all just for your case. Just wrote plugin that will resolve your problem and use it.

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.

Reply via email to