I'd argue though that as a maintainer you'd want to download the PR and test it actually works and doesn't break things which would presumably mean dragging it down and testing :)
Having said that it does seem silly to have a Jenkins instance that doesn't give you some of the goodness that Jenkins provides. Richard On 3/10/2014 8:34 PM, "Ivan Kalinin" <[email protected]> wrote: > But there is that fancy 'Release' button that performs mvn release on the > plugin. Why is it there if a plugin owner cant uae it? > I mean, the following workflow seema reasonable: > -- merge a PR > -- click tha button to release the plugin > > Its generally useful to have possibility to release them changes without > having to check out the source code and perform manual mvn operations. > > -- > 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/d/optout. > -- 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/d/optout.
