[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
Alex Lehmann created JENKINS-13129:
--------------------------------------

             Summary: Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
                 Key: JENKINS-13129
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
             Project: Jenkins
          Issue Type: Bug
          Components: core
    Affects Versions: current
         Environment: jenkins 1.457-snapshot, tomcat 7.0.25, java 1.6.0-31 running on windows vista
jenkins 1.455, tomcat 7.0.26, java 1.6.0-31 running on ubuntu 11.10

            Reporter: Alex Lehmann


I still cannot update cvs or subversion plugins without manually creating a .pinned file.

When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

This is probably related to JENKINS-12514, but wasn't fixed then


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160387#comment-160387 ]

sogabe commented on JENKINS-13129:
----------------------------------

JENKINS-12514 will be fixed in 1.456. See http://jenkins-ci.org/changelog.
               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.457-snapshot, tomcat 7.0.25, java 1.6.0-31 running on windows vista
> jenkins 1.455, tomcat 7.0.26, java 1.6.0-31 running on ubuntu 11.10
>            Reporter: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.
> This is probably related to JENKINS-12514, but wasn't fixed then

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Lehmann updated JENKINS-13129:
-----------------------------------

    Environment:
jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista



  was:
jenkins 1.457-snapshot, tomcat 7.0.25, java 1.6.0-31 running on windows vista
jenkins 1.455, tomcat 7.0.26, java 1.6.0-31 running on ubuntu 11.10


    Description:
I still cannot update cvs or subversion plugins without manually creating a .pinned file.

When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.



  was:
I still cannot update cvs or subversion plugins without manually creating a .pinned file.

When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

This is probably related to JENKINS-12514, but wasn't fixed then



issue is still present in 1.456
               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160449#comment-160449 ]

Alex Lehmann commented on JENKINS-13129:
----------------------------------------

i think i found the cause, there is problem with the isBundled property in plugins, I will write a patch tomorrow.


               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160840#comment-160840 ]

Alex Lehmann commented on JENKINS-13129:
----------------------------------------

https://github.com/alexlehm/jenkins/commit/2453985ca5f4cb2c824466d132fe3658020b72fe

[Fixed JENKINS-13129] Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

changed bundled plugin detection, added unit test


               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160841#comment-160841 ]

Alex Lehmann commented on JENKINS-13129:
----------------------------------------

I should note that this is not a specific Windows issue, I have had the same problem with 1.456 on linux as well


               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Lehmann reassigned JENKINS-13129:
--------------------------------------

    Assignee: Alex Lehmann
   

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>            Assignee: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JENKINS-13129 started by Alex Lehmann.

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>            Assignee: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160968#comment-160968 ]

SCM/JIRA link daemon commented on JENKINS-13129:
------------------------------------------------

Code changed in jenkins
User: Andrew Bayer
Path:
 core/src/main/java/hudson/PluginManager.java
 test/src/test/java/hudson/PluginManagerTest2.java
http://jenkins-ci.org/commit/jenkins/860cc9eb61a6a3212e4b8589ac11a74b59b1fcf7
Log:
  Merge pull request #418 from alexlehm/master

Fixed JENKINS-13129: Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup





               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>            Assignee: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160975#comment-160975 ]

dogfood commented on JENKINS-13129:
-----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1623|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1623/]
     [Fixed JENKINS-13129] Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup (Revision 2453985ca5f4cb2c824466d132fe3658020b72fe)

     Result = SUCCESS
alexlehm : [2453985ca5f4cb2c824466d132fe3658020b72fe|https://github.com/jenkinsci/jenkins/commit/2453985ca5f4cb2c824466d132fe3658020b72fe]
Files :
* test/src/test/java/hudson/PluginManagerTest2.java
* core/src/main/java/hudson/PluginManager.java

               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>            Assignee: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Lehmann resolved JENKINS-13129.
------------------------------------

    Resolution: Fixed

fixed in jenkins_main_trunk#1623

               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>            Assignee: Alex Lehmann
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

     [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kohsuke Kawaguchi updated JENKINS-13129:
----------------------------------------

    Priority: Critical  (was: Major)

Bumping up the priority to be on the LTS backporting radar.
               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>            Assignee: Alex Lehmann
>            Priority: Critical
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161804#comment-161804 ]

SCM/JIRA link daemon commented on JENKINS-13129:
------------------------------------------------

Code changed in jenkins
User: Alex Lehmann
Path:
 core/src/main/java/hudson/PluginManager.java
 test/src/test/java/hudson/PluginManagerTest2.java
http://jenkins-ci.org/commit/jenkins/2453985ca5f4cb2c824466d132fe3658020b72fe
Log:
  [Fixed JENKINS-13129] Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

changed bundled plugin detection, added unit test



               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>            Assignee: Alex Lehmann
>            Priority: Critical
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161853#comment-161853 ]

dogfood commented on JENKINS-13129:
-----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_ui-changes_branch #21|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/21/]
     [Fixed JENKINS-13129] Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup (Revision 2453985ca5f4cb2c824466d132fe3658020b72fe)

     Result = SUCCESS
alexlehm : [2453985ca5f4cb2c824466d132fe3658020b72fe|https://github.com/jenkinsci/jenkins/commit/2453985ca5f4cb2c824466d132fe3658020b72fe]
Files :
* test/src/test/java/hudson/PluginManagerTest2.java
* core/src/main/java/hudson/PluginManager.java

               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>            Assignee: Alex Lehmann
>            Priority: Critical
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] (JENKINS-13129) Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163122#comment-163122 ]

SCM/JIRA link daemon commented on JENKINS-13129:
------------------------------------------------

Code changed in jenkins
User: Alex Lehmann
Path:
 core/src/main/java/hudson/PluginManager.java
 test/src/test/java/hudson/PluginManagerTest2.java
http://jenkins-ci.org/commit/jenkins/e986dcd929886182db6c5c1926ba01a927ba55d2
Log:
  [Fixed JENKINS-13129] Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup

changed bundled plugin detection, added unit test
(cherry picked from commit 2453985ca5f4cb2c824466d132fe3658020b72fe)



               

> Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13129
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13129
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on windows vista
>            Reporter: Alex Lehmann
>            Assignee: Alex Lehmann
>            Priority: Critical
>
> I still cannot update cvs or subversion plugins without manually creating a .pinned file.
> When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file is installed into the plugin dir, but no cvs.jpi.pinned file is created. When restarting the tomcat server, the file is replaced by the 1.6 version from the war directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira