# Jenkins plugin not working after upgrade to 2.30.1 **URL:** \ **Category:** SCM-Manager Bug Reports\ **Created:** [January 28, 2022, 8:47am UTC](https://community.cloudogu.com/t/jenkins-plugin-not-working-after-upgrade-to-2-30-1/491 "2022-01-28T08:47:31Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![yeradd12](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/yeradd12/32/291_2.png) [@yeradd12](https://community.cloudogu.com/u/yeradd12)\ **Post date:** [January 28, 2022, 8:47am UTC](https://community.cloudogu.com/t/jenkins-plugin-not-working-after-upgrade-to-2-30-1/491/1 "2022-01-28T08:47:31Z")
Hi, it’s me again 🙂 After migration from 1.60 to 2.30.1 we have an issue with Jenkins plugin. Before migration we were using it (of course old version, for 1.60) and configuration was stored in jenkins.xml file in conf directory. After upgrade there was no Jenkins plugin installed which for sure is normal behaviour. But when I then install it from available plugins and restart scm instance, application doesn’t work and in web browser and logs I see onlyerror message **An error occurred during SCM-Manager startup** and java stack trace: > sonia.scm.migration.UpdateException: could not execute update for type sonia.scm.jenkins.config.repository.xml to version 2.0.0 in class sonia.scm.update.UpdateEngine$GlobalUpdateStepWrapper > at sonia.scm.update.UpdateEngine.execute(UpdateEngine.java:100) > at java.base/java.util.ArrayList.forEach(ArrayList.java:1541) > at sonia.scm.update.UpdateEngine.update(UpdateEngine.java:88) > … > Caused by: java.lang.NullPointerException > at sonia.scm.jenkins.update.JenkinsV2ConfigMigrationUpdateStep.buildConfig(JenkinsV2ConfigMigrationUpdateStep.java:79) > at sonia.scm.jenkins.update.JenkinsV2ConfigMigrationUpdateStep.lambda$doUpdate$0(JenkinsV2ConfigMigrationUpdateStep.java:73) > at sonia.scm.update.MapBasedPropertyReaderInstance.call(MapBasedPropertyReaderInstance.java:58) > … Something related with update. To get application running again I need to erase scm-jenkins-plugin from plugins directory. With LDAP plugin removing ldap.xml helped so I tried here the same but it didn’t help. I would like to be able to use Jenkins plugin. Can I do something to fix it? ---
**Author:** ![pfeuffer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pfeuffer/32/72_2.png) [@pfeuffer](https://community.cloudogu.com/u/pfeuffer)\ **Post date:** [January 28, 2022, 9:44am UTC](https://community.cloudogu.com/t/jenkins-plugin-not-working-after-upgrade-to-2-30-1/491/2 "2022-01-28T09:44:12Z")
Hi, this one’s on us. It looks like we missed a case in the migration for the jenkins plugin. To make SCM-Manager run again, please delete the folder `/plugins/scm-jenkins-plugin` to remove the plugin again and restart SCM-Manager. We will release a fixed version of the plugin probably today. If you cannot wait, you can try to fix this manually: Somwhere in your config folder there should be a file `repositories.xml.v1.backup`. In this you will find many `repository` entries. For each such entry that has a `jenkins....` propery (for example `jenkins.url`), this has to have a `jenkins.branches` property, too: ```auto jenkins.branches ``` By the way: Yes, after the migration SCM-Manager does not install the old plugins automatically. ---
**Author:** ![yeradd12](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/yeradd12/32/291_2.png) [@yeradd12](https://community.cloudogu.com/u/yeradd12)\ **Post date:** [January 28, 2022, 11:00am UTC](https://community.cloudogu.com/t/jenkins-plugin-not-working-after-upgrade-to-2-30-1/491/3 "2022-01-28T11:00:15Z")
I have no problem waiting for a new version of plugin but just to let you know I tried your workaround and although I think I did everything right it doesnt work (the same outcome as before). In my `repositories.xml.v1.backup` was only one `repository` entry with jenkins.\* keys in it and I just added snippet you provided inside it. ---
**Author:** ![pfeuffer](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/pfeuffer/32/72_2.png) [@pfeuffer](https://community.cloudogu.com/u/pfeuffer)\ **Post date:** [January 28, 2022, 2:05pm UTC](https://community.cloudogu.com/t/jenkins-plugin-not-working-after-upgrade-to-2-30-1/491/4 "2022-01-28T14:05:19Z")
OK, thanks for the feedback. We released a new version of the Jenkins plugin with a fixed migration (2.2.2). Please check whether this works for you. ---
**Author:** ![yeradd12](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/yeradd12/32/291_2.png) [@yeradd12](https://community.cloudogu.com/u/yeradd12)\ **Post date:** [January 28, 2022, 2:22pm UTC](https://community.cloudogu.com/t/jenkins-plugin-not-working-after-upgrade-to-2-30-1/491/5 "2022-01-28T14:22:35Z")
Now it works. Thank you! ---
**Author:** ![felix.ebert](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/felix.ebert/32/1554_2.png) [@felix.ebert](https://community.cloudogu.com/u/felix.ebert)\ **Post date:** [July 22, 2022, 9:50am UTC](https://community.cloudogu.com/t/jenkins-plugin-not-working-after-upgrade-to-2-30-1/491/6 "2022-07-22T09:50:50Z")
I have closed this thread since there was no activity in the last 30 days.