Migrating the Jenkins plugin archetype to Workflow

48 views
Skip to first unread message

Rafael Ribeiro Rezende

unread,
Aug 7, 2015, 11:13:26 AM8/7/15
to Jenkins Developers
We wish every plugin to be compatible with Workflow, right? (at least those plugins that make sense to be there)...

So, wouldn't be a good idea to have the Jenkins archetype also ready to use with Workflow?

Daniel Beck

unread,
Aug 7, 2015, 11:54:48 AM8/7/15
to jenkin...@googlegroups.com
In what way would you change it? Have HelloWorldBuilder implement SimpleBuildStep?

On 07.08.2015, at 17:13, Rafael Ribeiro Rezende <rafael...@gmail.com> wrote:

> We wish every plugin to be compatible with Workflow, right? (at least those plugins that make sense to be there)...
>
> So, wouldn't be a good idea to have the Jenkins archetype also ready to use with Workflow?
>
> --
> 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/426c5a68-af68-4847-9feb-941a40d0e2cd%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Rafael Ribeiro Rezende

unread,
Aug 7, 2015, 12:07:01 PM8/7/15
to jenkin...@googlegroups.com

Yes. The migration is very simple, but might save beginners the trouble of doing so in a later stage, since they are compelled to override the more generic perform(...) which works for both freestyle and workflow.
Just an idea.

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/0dqXhbjRhYs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7FC2F072-446F-4014-B43F-DB72ED7676C4%40beckweb.net.

Jesse Glick

unread,
Aug 11, 2015, 10:23:00 AM8/11/15
to Jenkins Dev
On Fri, Aug 7, 2015 at 12:06 PM, Rafael Ribeiro Rezende
<rafael...@gmail.com> wrote:
> Yes. The migration is very simple, but might save beginners the trouble of
> doing so in a later stage, since they are compelled to override the more
> generic perform(...) which works for both freestyle and workflow.
> Just an idea.

Good idea, thanks!

https://github.com/jenkinsci/maven-hpi-plugin/pull/20

Rafael Ribeiro Rezende

unread,
Sep 4, 2015, 6:41:18 PM9/4/15
to Jenkins Developers
I've noticed this change is available for maven-hpi-plugin 1.114, but if I don't specify the plugin version maven will automatically use 1.114-cloudbees-1 instead, which does not implement the SimpleBuildStep. Is there any reason for not implementing it?
Just wanted to know about possible risks... If you say there is some, I'll recommend people in our company to specify the version then.

Rafael Ribeiro Rezende

unread,
Sep 4, 2015, 6:48:45 PM9/4/15
to Jenkins Developers
Oh, just noticed that the 1.114-cloudbees-1 was released before the update. So, I'll specify the version...
Still, let's be aware that running the maven-hpi-plugin as described in the Plugin tutorial (as newcomers would do as they follow it) won't bring the workflow-compatible version of the Hello World yet.
Reply all
Reply to author
Forward
0 new messages