After your PR is integrated into https://github.com/jenkinsci/graphite-plugin <https://github.com/jenkinsci/graphite-plugin> you need to run the release command for this repository. In your fork you only change the source code for the fixes, the URLs remain the same as they are...
> Am 12.01.2015 um 09:25 schrieb Michael Patel <mpatel.g...@gmail.com>: > > Further question, > > Currently i'm proceeding as advised, but i'm a little confused. The > distribution management url configuration for the project is currently set to > http://maven.jenkins-ci.org:8081/content/repositories/releases/ > > I'm confused as to whether to maven release on my fork and merge or merge and > then release on the jenkins repo itself ? > > Which is the correct approach ? > > MP > > On Friday, 9 January 2015 16:42:34 UTC, Michael Patel wrote: > Great, will do. > > I'll contact the author aswell jic. > > On Friday, 9 January 2015 16:26:02 UTC, Ullrich Hafner wrote: > >> Am 09.01.2015 um 17:12 schrieb Michael Patel <mpate...@gmail.com <>>: >> >> Hi guys, >> >> I've noticed that the graphite plugin >> https://github.com/jenkinsci/graphite-plugin >> <https://github.com/jenkinsci/graphite-plugin> to send metrics to jenkins is >> currently inactive pending the 1.2 release. >> >> The 1.1 release no longer works as the api to get test results has changed >> slightly. >> >> I'm happy to release from our organization's fork and to add in some extra >> metrics going forward. >> >> github username : patelm5 >> plugin name : graphite-plugin-fork >> fork : https://github.com/betgenius/graphite-plugin >> <https://github.com/betgenius/graphite-plugin> >> >> Is this the correct way to go about reviving zombie projects ? > > Actually no. We recommend to integrate your changes as pull request in the > existing plug-in. We can give you commit rights so you can integrate these > changes on your own (seems that the irc bot currently is down). > And if there is no active maintainer anymore (did you contact the authors?) > then you can take over the ownership of the plugin… > >> >> Cheers, >> MP >> >> >> -- >> 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 jenkinsci-de...@googlegroups.com <>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/604d43d5-a7f6-4080-9e7c-e830e0871175%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/604d43d5-a7f6-4080-9e7c-e830e0871175%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <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 jenkinsci-dev+unsubscr...@googlegroups.com > <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/17d247fb-6c7a-4656-8f24-305aa8e5f227%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/17d247fb-6c7a-4656-8f24-305aa8e5f227%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/62BE7B82-4D10-4D60-B5E9-F885A4DF189C%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
