Hello, 

I am updating Jenkins LTS from 2.346.1 to 2.361.1 and keep hitting an issue with plugin versions. Upon the first start of Jenkins, it overwrites some of existing plugins with older versions that comes from the war file (detached-plugins). This causes dependency conflict and prevents some modules to load, which in return fails the whole startup due to the inability to read config.xml correctly. 

A bit of background: 

We package all plugins separately. The latest plugins were downloaded with plugin-installation-manager-tool (2.12.9) and targeted for Jenkins 2.361.1.

My understanding is that this should involve all the dependencies needed. Command I use:

  java -jar jenkins-plugin-manager.jar \
  --jenkins-version "$JENKINS_VERSION" \
  --plugin-file plugins.yaml \
  --plugin-download-directory plugins/ \
  --verbose 

Later on, we upgrade jenkins RPM, clear plugins directory and extract our zip with all updated plugins. 

When Jenkins is started, it recognizes that the last version was 2.346.1 (probably from /var/lib/jenkins/jenkins.install.InstallUtil.lastExecVersion) and overwrites a few plugins we staged. 

One of them is instance-identity.jpi for example. The latest War comes with 3.1 but we need 116.vf8f487400980 for many dependencies to start.

The reason for our unusual upgrade procedure is the fact that many of our environments don't have internet access and we have to deliver updates via another means. 

Is there a way to prevent the automated plugin updates during first start?