Hello Jesse, Thank you for your reply. Can you please provide the link to the thread where you have discussed the thing you mentioned.
On Friday, March 16, 2018 at 8:47:02 PM UTC+5:30, Jesse Glick wrote: > > On Thu, Mar 15, 2018 at 10:22 PM, martinda <[email protected] > <javascript:>> wrote: > > there there is another model which is to have a job that handles all the > pull requests of a git repo to a given branch. For example say there is a > git repository called jupiter/juno.git (jupiter is the name of the github > org or of the bitbucket project). Then the pull requests destined to the > master branch of the juno git repository could have a correspondig job > called jupiter/juno/master. > > Which is already a standard part of Jenkins 2, including GitHub and > Bitbucket support. The only thing distinct from the proposal as it > stands is that using the default set of plugins, the jobs are > configured from a `Jenkinsfile` whereas you are proposing some YAML > format—easily handled by an existing pair of extension points in > `workflow-multibranch`. I have discussed this is another thread. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b73501a6-64d3-480a-9b32-a3eb36523dc8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
