Jenkins Plugin (Stephen Connolly) tutorial still valid?

[Kaj Kandler]

Hi,
on the Jenkins Wiki page for Plugin Tutorial, there is a link to Stephen Connolly's tutorial, which does a lot sophisticated mast/remote unification.

As this tutorial is 5 yrs old, I wonder if this is still something that needs to be done?

I have studies some other plugins and can't find similar code, so I think it might have become obsolete by newer versions/apis.

Thanks
Kaj

[Jesse Glick]

On Wed, Oct 23, 2013 at 3:51 PM, Kaj Kandler <KajKa...@conficio.com> wrote:
> does a lot [of] sophisticated mast[er]/remote unification

Like what? Link?

[Kaj Kandler]

Sorry I should have linked to the page I'm talking about https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-Otherresources. In part 2 he starts to unify plugins for Maven jobs with plugins for free-style jobs.

[Jesse Glick]

On Thu, Oct 24, 2013 at 9:01 AM, Kaj Kandler <KajKa...@conficio.com> wrote:
> In part 2 he starts to unify plugins for Maven jobs with plugins for
> free-style jobs.

Probably unnecessary since you can use a regular Publisher from a
Maven job too. (It would just not be as fully integrated: you would
need to configure it manually, even if the relevant information is
available from the POM.)

[Stephen Connolly]

when I finally get around to implementing the coverage plugin, I will probably see about rewriting my tutorial ;-)

TL;DR don't hold your breath

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Kaj Kandler]

Thanks Jesse,
for sharing your insight. How about the parts of the remote/master execution, is that still something to be implemented differently for the different types of jobs? See Part 2 and 3

[Jesse Glick]

On Thu, Oct 24, 2013 at 11:43 AM, Kaj Kandler <KajKa...@conficio.com> wrote:
> How about the parts of the remote/master
> execution, is that still something to be implemented differently for the
> different types of jobs?

I think that was only necessary because of the job-type-specific
implementation of MavenReporter, which is invoked on the remote side,
unlike a Publisher which is always invoked on master (and must
explicitly ask to do operations on the slave if it needs to).