1.651.2 LTS not available to Maven ?

33 views
Skip to first unread message

Mike Caspar

unread,
Jun 9, 2016, 12:51:03 PM6/9/16
to Jenkins Developers
Hi there,

Can someone help me out (I may have missed a repo change or something?).

My available options goes as high as 1.645 and then jump to 2.0

My Maven repo is set to..


<parent>
    <groupId>org.jenkins-ci.plugins</groupId>
    <artifactId>plugin</artifactId>
    <version>1.642</version>
</parent>

I would like to be able to dev/test on the latest LTS 1.652.1

Can someone help ?

Thanks

Mike



Mike Caspar

unread,
Jun 9, 2016, 12:54:52 PM6/9/16
to jenkin...@googlegroups.com
Correction..

I meant 1.651.2 (latest LTS from May).

Mike
--
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/3lRzi1S30f8/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/a4ca6de8-962a-4c02-a596-70520141c8c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Stephen Connolly

unread,
Jun 9, 2016, 1:46:53 PM6/9/16
to jenkin...@googlegroups.com
I assume you are referring to the plugin parent pom. We switched to a version number that is independent of Jenkins core.

Basically always use the latest plugin parent.

Specify the jenkins baseline version using the <jenkins.version> property in your pom. The new parent will work as far back as 1.580 (if you tweak the correct properties) and it makes testing with hpi:run easier against different versions (to make sure your plugin will also work on latest jenkins)

--
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/57599F58.8040701%40caspar.com.

Mike Caspar

unread,
Jun 9, 2016, 1:57:06 PM6/9/16
to jenkin...@googlegroups.com
Yes,

I test different version by simply changing the parent POM.

The problem is that the repo itself is not listing all the versions.

I can use 2.0 all the way up to current.

I can also use 1.424.x and any number in between.

The Parent POMs between 1.645 and 2.0 don't appear in the repo.

Specifically, the LTS 1.651.2 isn't there to test against.  (setting the parent POM to 1.651.2 doesn't download as it can't be found  (resolve).

Does that help ?

Mike

Mike Caspar

unread,
Jun 9, 2016, 2:11:38 PM6/9/16
to jenkin...@googlegroups.com
Hi,

I figured out what you were talking about.

You are referring to

<parent>
    <groupId>org.jenkins-ci.plugins</groupId>
    <artifactId>plugin</artifactId>
    <version>2.2</version>
</parent>

from the page...  

https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-pom.xml

That helped.

Thanks

Stephen Connolly

unread,
Jun 9, 2016, 5:34:06 PM6/9/16
to jenkin...@googlegroups.com
I'll try again.

The way the parent pom works has been changed. It's versioning was decoupled from the Jenkins core version as of 1.646 or so IIRC

The new recommendation is to always use whatever the very latest plugin parent is and to control the version of jenkins that it uses as a baseline with the following in your pom

<properties>
  <jenkins.version>1.651.2</jenkins.version>
</properties>

Please look at the readme for the parent pom: https://github.com/jenkinsci/plugin-pom

Mike Caspar

unread,
Jun 9, 2016, 6:03:47 PM6/9/16
to jenkin...@googlegroups.com

Got it.
Thanks !


Sent from my Samsung Galaxy smartphone.
Reply all
Reply to author
Forward
0 new messages