After failed upgrade, restarting Jenkins keeps upgrading GIT plugin

107 views
Skip to first unread message

Todd

unread,
Nov 20, 2013, 10:21:03 AM11/20/13
to jenkins...@googlegroups.com
Hi all,

We're running Jenkins version 1.502. After a failed upgrade of the "Jenkins GIT plugin" from version 1.2.0 to 2.0, we downgraded back to version 1.2.0 by hand by following these steps. The problem we're having is each time Jenkins is restarted, version 2.0 gets installed again, even though we've created a git.jpi.pinned file. Performing the downgrade to 1.2.0 and restarting again consistently fixes the problem – that is, until the following restart.

Any ideas on what might be causing the new version to keep getting installed over and over again? Happy to provide any additional information that would be useful. Thanks!

Todd

Todd

unread,
Nov 22, 2013, 10:22:37 AM11/22/13
to jenkins...@googlegroups.com
An update: it wasn't Jenkins, but a Chef script for Jenkins that was causing our issue. git was one of the plugins we had configured to automatically upgrade (the fix was to simply stop using this automatic upgrade feature). Hope this is of use to someone!

Vishal Mahindrakar

unread,
May 25, 2015, 5:08:10 AM5/25/15
to jenkins...@googlegroups.com
Hi,

  Can you let me know where in Jenkins can i stop this automatic upgrade ??

Regards
Vishal M
Reply all
Reply to author
Forward
0 new messages