Unable to update plugin using manual upload

[Wei Zheng]

Hi,

I am trying to do a little work on a plugin, but I hit this problem StackOverflowError problem caused circular dependency:

https://issues.jenkins-ci.org/browse/JENKINS-36361

The workaround is to update Subversion plugin to to some higher version using manual update (because the UI of the "Updates" tab to update the plugin is broken by the issue we are trying to workaround). However, after I used "advanced" tab to manually upload the hpi (which I just downloaded from Subversion's plugin page, version 2.6), and after I restart Jenkins, the version always reverts back to the original version (1.45). I have to restart Jenkins server because if I don't the new version 2.6 won't show up either.

What should I do? Or am I doing something wrong?

My Jenkins version is 1.596.2. And I am running on Linux (ubuntu 14.04 trusty).

--

Thank you very much.

Wei

[Daniel Beck]

Wrong mailing list.

> --
> 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/CA%2BnSbNv49CDzJKMGXxpDu%2BERPSAtd4xvidLu4PDi-M4g1jbjUg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

[Jesse Glick]

If you are developing a plugin and using `mvn hpi:run`, just ensure it has appropriate `test`-scoped dependencies to begin with. It was unclear from your message what really you are doing.

[Wei Zheng]

Yes, I am trying to modify an plugin so it is related to developing a plugin.

Regarding "test" scope, is this what you are talking about?

https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope

If the above link is what you meant by "test" scope, how is it related to my original problem? The subversion plugin seems like a bundled plugin, and I am not able to upgrade it to new version.

Thank you again!

[Jesse Glick]

On Thu, Aug 25, 2016 at 11:37 AM, 'Wei Zheng' via Jenkins Developers
<jenkin...@googlegroups.com> wrote:
> Regarding "test" scope, is this what you are talking about?
> https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope

Yes.

> The subversion plugin seems like a bundled plugin, and I
> am not able to upgrade it to new version.

If you declared, say,

<dependency>
<groupId>org.jenkins-ci.plugins</groupId>
<artifactId>subversion</artifactId>
<version>2.6</version>
<scope>test</scope>
</dependency>

that would override the bundled version.

Are you already depending on `workflow-scm-step` somehow? Not sure how
else you would be running into this issue to begin with.