Hi Vincent, As the sole purpose of this plugin is to update pull request status I am free to choose how exactly I want to structure my pull request builds.
At this time, I'm using the Jenkins Job DSL to create (and destroy) pull request specific builds. This has the advantages over the github pull request builder: I can use the wall display plugin to show passing and failing pull requests, I can track build status historically, and I can track changes just like I would with any other build. In addition, I could imagine someone wanting to mark the status of a pull request at the conclusion of a parameterized build, for example. Thanks. -- H On Wednesday, August 21, 2013 10:49:57 PM UTC-7, Vincent Latombe wrote: > > Hello, > > what is the difference between your plugin and the existing > https://wiki.jenkins-ci.org/display/JENKINS/Github+pull+request+builder+plugin? > > Vincent > > > 2013/8/22 Hawk Newton <[email protected] <javascript:>> > >> Hello everyone, >> >> I've recently authored a new plugin -- github-pull-request-notifier >> >> I've made the initial pom changes outlined here: >> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins >> >> github repo: >> https://github.com/hawknewton/jenkins-github-pull-request-notifier >> >> My jenkins-ci.org account is hawknewton >> >> Thanks! >> >> -- H >> >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
