http://repo.jenkins-ci.org/public/org/jenkins-ci/plugins/phabricator-plugin/
On Wed, Jun 3, 2015 at 12:25 AM Laurent Goudet <[email protected]> wrote: > Awesome thanks! Do you know why the plugin does not appear in > http://repo.jenkins-ci.org/public/ though? > > On Wednesday, June 3, 2015 at 7:02:57 AM UTC+10, Aiden Scandella wrote: > >> Wonderful, I successfully refactored to reuse the getAction of Cobertura >> and published 1.0 to maven. <3 Jenkins (and thanks for bearing with me, >> Ullrich... I am not a Java developer) >> >> On Tuesday, June 2, 2015 at 9:43:38 AM UTC-7, Aiden Scandella wrote: >> > aha, I knew I was missing something. I will clean all this up and send a >>> PR before uploading to your maven. Thanks! >>> >> On Tue, Jun 2, 2015 at 9:34 AM, Ullrich Hafner <[email protected]> >>> wrote: >>> >> Of course it is possible to read existing results of other plug-ins. >>>> >>>> All you need is >>>> a) a dependency to the other plugin in your pom.xml >>>> b) a call to getAction(OtherPluginAction.class) on a job or build >>>> instance >>>> >>> Am 02.06.2015 um 18:07 schrieb Aiden Scandella <[email protected]>: >>>> >>>> Awesome, thanks! >>>> >>>> One lingering question I have is how to "include" another plugin inside >>>> mine. Concretely, we provide coveralls-like functionality which tracks >>>> coverage changes over time. I am re-using the Cobertura plugin's classes >>>> for doing this, but I essentially "vendored" the plugin into my repo. >>>> >>>> I am not a Java developer, and I know that the correct solution >>>> involves pointing to maven somewhere, but I haven't been able to get it >>>> right in my spare time. >>>> >>>> Are there instructions somewhere on how I might do this? Or am I >>>> approaching the problem all wrong and there's actually some way for me to >>>> re-use the already-loaded plugin's results? >>>> >>>> https://github.com/uber/phabricator-jenkins-plugin/issues/7 >>>> >>>> On Tue, Jun 2, 2015 at 9:06 AM, Aiden Scandella <[email protected]> >>>> wrote: >>>> >>>> Awesome, thanks! >>>>> >>>>> One lingering question I have is how to "include" another plugin >>>>> inside mine. Concretely, we provide coveralls-like functionality which >>>>> tracks coverage changes over time. I am re-using the Cobertura plugin's >>>>> classes for doing this, but I essentially "vendored" the plugin into my >>>>> repo. >>>>> >>>>> I am not a Java developer, and I know that the correct solution >>>>> involves pointing to maven somewhere, but I haven't been able to get it >>>>> right in my spare time. >>>>> >>>>> Are there instructions somewhere on how I might do this? Or am I >>>>> approaching the problem all wrong and there's actually some way for me to >>>>> re-use the already-loaded plugin's results? >>>>> >>>>> https://github.com/uber/phabricator-jenkins-plugin/issues/7 >>>>> >>>> On Tue, Jun 2, 2015 at 4:04 AM, Ullrich Hafner <[email protected]> >>>>> wrote: >>>>> >>>> >>>>>> Created https://github.com/jenkinsci/phabricator-plugin >>>>>> >>>>>> Welcome aboard! You will receive a GitHub invitation for your >>>>>> repository... >>>>>> >>>>>> Ulli >>>>>> >>>>> Am 18.05.2015 um 19:53 schrieb Aiden Scandella <[email protected]>: >>>>>> >>>>>> Greetings, >>>>>> >>>>>> I created https://github.com/uber/phabricator-jenkins-plugin and >>>>>> have recently open-sourced it. We use it internally at Uber to manage >>>>>> integration with Phabricator. >>>>>> >>>>>> My github username is sectioneight >>>>>> >>>>>> The name is, uninspiredly, "Phabricator Jenkins Plugin", which is >>>>>> descriptive but boring. >>>>>> >>>>>> Please let me know what to do to in order to get this included as on >>>>>> official jenkins plugin. >>>>>> >>>>>> Thanks, >>>>>> Aiden >>>>>> >>>>>> -- >>>>>> 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/b78726d9-f21f-482d-9aaf-79d88c9aea65%40googlegroups.com >>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/b78726d9-f21f-482d-9aaf-79d88c9aea65%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>> >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to a topic in >>>>>> the Google Groups "Jenkins Developers" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/jenkinsci-dev/ERUaNBgtyis/unsubscribe >>>>>> . >>>>>> >>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> [email protected]. >>>>>> >>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/7F78B42B-D121-4042-AACF-E5950180892A%40gmail.com >>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/7F78B42B-D121-4042-AACF-E5950180892A%40gmail.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>>> 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]. >>>> >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFKJaBaQ5F8C%2BLBsLr2%3Da_9jnz5d8yOfZHC3QxPcZ-tRTUpV-w%40mail.gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFKJaBaQ5F8C%2BLBsLr2%3Da_9jnz5d8yOfZHC3QxPcZ-tRTUpV-w%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Developers" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/jenkinsci-dev/ERUaNBgtyis/unsubscribe >>>> . >>>> >>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/8597F956-0949-4D8F-B08A-1D7AC9ADECE3%40gmail.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/8597F956-0949-4D8F-B08A-1D7AC9ADECE3%40gmail.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/ERUaNBgtyis/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/f79a25ad-ffe4-49ba-b1c6-6aab4c8f7688%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/f79a25ad-ffe4-49ba-b1c6-6aab4c8f7688%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFKJaBY3bWRj4yQiOHUa-MddrrQm0gwt2fF2EOiAJiYi3EXsMw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
