That worked like a charm, thanks! Came across the documentation for it as 
well - https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins

Yes, Jenkins 2.0 update is long due :)

On Saturday, 19 November 2016 07:12:47 UTC-8, Stephen Connolly wrote:
>
> As you are on 1.x create an empty ldap.jpi.pinned file as a sibling and 
> that marker will instruct Jenkins not to replace with the bundled plugin.
>
> On 2.x (why are you waiting?) the whole pinned & bundled concepts were 
> removed so this would not be an issue for you
>
> On Sat 19 Nov 2016 at 01:05, alok joshi <[email protected] <javascript:>> 
> wrote:
>
>> I have a large fleet of Jenkins instances running in a cluster, all 
>> having the LDAP plugin version 1.6 (Jenkins version 1.611). I want to 
>> fleet-upgrade the LDAP plugin version to 1.7 (to incorporate environment 
>> variables in my plugin configuration). How do I achieve this without 
>> manually uploading 1.7 version through UI for each Jenkins instance?
>>
>> I tried writing a script which basically performs these operations for 
>> each Jenkins instance:
>>
>>    1. 1. Replace the existing .jpi/.hpi file in $JENKINS_HOME/plugins 
>>    for ldap plugin with the correct .hpi file (of the 1.7 version)
>>    2. 2. Edit config.xml under $JENKINS_HOME which has the version number
>>    3. 3. Safe restart Jenkins
>>
>> It works fine till step 2 but as soon as I perform safe restart, Jenkins 
>> magically puts in the original .jpi/.hpi file (the 1.6 version file) back 
>> inside $JENKINS_HOME/plugins. Jenkins instance has the 1.6 plugin version 
>> again in the UI. Is there a better way to perform fleet plugin upgrades in 
>> general? I want to mention that I want the 1.7 plugin version, not the 
>> latest
>>
>> How do I fix this? I even tried using curl (mentioned at 
>> http://stackoverflow.com/a/20848745/1746529) but didn't help.
>>
>> -- 
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/37002132-3170-41df-a713-55caebdca064%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/37002132-3170-41df-a713-55caebdca064%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Sent from my phone
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/00eae494-2888-45c1-af01-8f6f226147a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to