Glitches after Jira 7 upgrade and Jira add-on upgrade
Description
Environment
Attachments
- 23 Sep 2016, 02:03 PM
Activity
Mark Rekveld September 26, 2016 at 1:41 PM
Good to hear the workaround fixed your issue.
Shawn Bai September 26, 2016 at 1:40 PM
The sites are now showing in Jira. You may close this issue. Thanks.
Mark Rekveld September 23, 2016 at 9:33 PM
SITE_TYPE should either be JENKINS or HUDSON depending on the flavour you are connecting to.
As for RPC_URL this is the base URL of the site that JIRA will use to synchronize data.
There is also the option of having a DISPLAY_URL but this is optional, if you don't specify it, then the RPC_URL is used in the UIs as well.
Shawn Bai September 23, 2016 at 8:51 PM
Both SITE_TYPE and RPC_URL are empty after add-on upgrade in my case. What should be the value for RPC_URL?
Mark Rekveld September 23, 2016 at 2:18 PM
Hi @Shawn Bai,
The first "glitch" you mentioned, the application link name has "(DO NOT USE)" appended to it is by design. Since version 1.6.0 the plugin moved away from application links since it was getting harder and harder to make the add-on work with that specific framework.
No its just storing the configuration itself and so the application link framework is no longer used.
How ever, in some cases the upgrade doesn't do a complete job. And this is the second glitch you experience.
I'm not sure why this happens, but there is a workaround for it to resolve this.
Please refer to the attached document on how to resolve the error that you experience in the Jenkins Configuration page.
Cheers,
Mark
Upgrade to Jira 7.1.9 resulted in a couple of glitches as shown in the attached screenshots. First is that the Application field in the row "App Link for Jenkins" is automatically appended string "(DO NOT USE)". Second is that null pointer exception is thrown when accessing the page "Manage Jenkins Sites".