| Note |
|---|
| Warning |
Looking for the documentation on the newest versions of Power Scripts for Jira 8 for Server/Data Center? Click here ! |
| Info |
|---|
Content in development. |
| Note |
|---|
Once you upgrade to version 4.0.0, all persistence uses Active Objects and does not require having the plugins installed when importing a backup to a new syst |
...
Mundane operations as backup and restore may pose some problems to the unsuspecting JIRA administrator. Since all the Kepler plugins create some tables in the JIRA schema - we created this mechanism long before Active Objects was introduced into Atlassian's framework - you need to take some precautions at restore.
Specifically, at restore you need to create the tables used by our plugins. You do not need to copy schema from the previous JIRA or fill it with data, you just need to simply install the plugins into JIRA before restoring (enabling the plugins would create the needed tables).
JJUPIN has two dependencies:
- katl-commons (core support)
- warden (used for licensing)
For reference, these are the tables created by each add-on
...
krunnablesils
krssecurity
klistenersils
jjlf_config
jjlf_project
jjlf_category
...
kplugins
kpluginscfg
kissuestate
kstatevalues
...
and data is migrated to this version, you will not be able to downgrade. That's why we recommend upgrading on a test instance first to check if everything works fine. |
Possible "errors"
We're working to make the upgrade experience as smooth as possible. However, there are a few "errors" you may see in the logs that are actually normal.
Unable to create a service config for service with the name <service_name>
| Code Block |
|---|
Unable to create a service config for service with the name : asdf
com.atlassian.jira.service.OfBizServiceConfigStore$ClassNotFoundServiceException: Could not find class: com.keplerrominfo.jira.plugins.jjupin.services.SILService
at com.atlassian.jira.service.OfBizServiceConfigStore.instantiateServiceContainer(OfBizServiceConfigStore.java:249)
at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceContainer(OfBizServiceConfigStore.java:209)
at com.atlassian.jira.service.OfBizServiceConfigStore.getServiceConfigForId(OfBizServiceConfigStore.java:180)
at com.atlassian.jira.service.DefaultServiceManager.removeService(DefaultServiceManager.java:480)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
....
Caused by: java.lang.ClassNotFoundException: Class 'com.keplerrominfo.jira.plugins.jjupin.services.SILService' not found.
at com.atlassian.jira.plugin.DefaultComponentClassManager.constructEvenIfNotEnabled(DefaultComponentClassManager.java:160)
at com.atlassian.jira.plugin.DefaultComponentClassManager.newInstance(DefaultComponentClassManager.java:72)
at com.atlassian.jira.service.OfBizServiceConfigStore.loadServiceClass(OfBizServiceConfigStore.java:385)
at com.atlassian.jira.service.OfBizServiceConfigStore.instantiateServiceContainer(OfBizServiceConfigStore.java:244)
... 170 more |
Explanation
In version 4.0.0 we've moved our services to run with the Atlassian Scheduler library instead of the old services API. This error appears because at the end of the data migration, we attempt to delete the old services that are no longer needed. When removing a service, the services API attempts to instantiate it if it's not already available and since since the old implementation is no longer available, the instantiation will fail with the above error, but the service will be deleted as intended.
Actions needed
None