Jenkins Plugin upgrade from 1.454 to 1.651.3

38 views
Skip to first unread message

Panagiotis Labrou

unread,
Feb 6, 2019, 2:45:55 AM2/6/19
to jenkins...@googlegroups.com

Hi there,

 

We have a few custom Jenkins plugins developed for version 1.454 and we want to compile

them for usage with version 1.651.3 or newer.

 

For example one of our plugins pom.xml looks like

 

    <parent>

        <groupId>org.jenkins-ci.plugins</groupId>

        <artifactId>plugin</artifactId>

        <version>1.454</version>

    </parent>

 

    <groupId>ci-release</groupId> <!-- historical -->

    <artifactId>ci-release</artifactId> <!-- historical -->

    <version>2.0.1</version>

    <packaging>hpi</packaging>

 

When I want to go from 1.454 to 1.645 is easy I simply change 1.454 to 1.645 and plugin is built

however when I try to go to a version greater than 1.645 changing 1.454 to 1.651.3 I receive an

error

 

Non-resolvable parent POM: Could not find artifact org.jenkins-ci.plugins:plugin:pom:1.651.3 in repo.jenkins-ci.org (https://repo.jenkins-ci.org/public/) and 'parent.relativePath' points at wrong local POM @ line 3, column 11 -> [Help 2]

 

How can I solve this problem?

 

Best Regards

Panagiotis Lamprou

 

Steffen Elste

unread,
Feb 6, 2019, 4:21:56 AM2/6/19
to Jenkins Users
Hi,
the latest 1.x release of this artefact is 1.645: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/plugin/
Cheers,

Steffen

Panagiotis Labrou

unread,
Feb 6, 2019, 4:44:23 AM2/6/19
to jenkins...@googlegroups.com

Hi Steffen,

 

Thank you for your reply. Yes I agree with this but if I want to install 1.651.3 war file for Jenkins

which one from plugin site should I select in my plugin’s pom file?

 

I have tried the following but it didn’t work

 

  <parent>

    <groupId>org.jenkins-ci.plugins</groupId>

    <artifactId>plugin</artifactId>

    <version>2.0</version>

  </parent>

 

BR/s

Panagiotis

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bdc3e704-a79d-4c5f-aeff-70d55c033470%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Victor Martinez

unread,
Feb 6, 2019, 5:06:12 AM2/6/19
to Jenkins Users
IIUC, you would like to use a WAR file different than the default one, if so, then you might need to use the properties section to enforce the version you'd like to:

...
 
<parent>
    <groupId>org.jenkins-ci.plugins</groupId>
    <artifactId>plugin-pom</
artifactId>
   
<version>2.0</version>
</
parent>
<properties>
    <jenkins.version>1.651.3</jenkins.version>
....


I have not tried though, but something like that it should work I guess so. Other than that, if you got some specific questions about plugin developoment it's worth to ask to the Jenkins Developers mailing list jenkinsci-dev

Cheers

Adrien Lecharpentier

unread,
Feb 6, 2019, 5:54:42 AM2/6/19
to Jenkins Users
If I recall correctly, since `plugin-pom` 2.0, the version of the Jenkins the plugin is built for is set with the `jenkins.version` property, as Victor said. So you could basically use the latest `plugin-pom` (3.37) and stil compile for `1.651.3`. 
It's a minimal core version requirement. Doesn't mean that it won't work on older versions nor it will work either on newer versions.
-- Adrien

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.


--
Adrien Lecharpentier
Reply all
Reply to author
Forward
0 new messages