Use Application Link Data in Build Notifier
Activity
Jon Starbird November 17, 2015 at 6:32 PM
Mark,
thanks for that info. I look forward to that fix, been a long time coming but I understand the situation and I am patiently awaiting the fix.
Mark Rekveld November 17, 2015 at 10:04 AM
Hi Jon,
This is the first step in two to allow you to change the RPC URLs of linked JIRA instances.
Implemented in this improvement is that no direct link is stored in the Build configuration but instead a reference link is stored. Tis reference link is then using to lookup the RPC URL of JIRA at build time.
I have created https://marvelution.atlassian.net/browse/JJI-207#icft=JJI-207 to support the second part, editing of field of a link.
Jon Starbird November 17, 2015 at 1:55 AM
Mark,
this is not fixed as far as I can tell. I've updated both Jira and Jenkins and still get the same errors as before.
I even removed and readded the app link to no avail.
I'm not exactly sure how it is fixed since I still have no way of changing the URL that Jenkins uses to talk to Jira.
Still not sure I understand why you just don't allow the Jenkins side to be edited in the application links, that would solve the problem. Having it be auto configured is great but why not allow that to be edited if needed?
Mark Rekveld March 5, 2015 at 9:01 PM
I've been struggling to get some more time for resolve this, sorry for the long wait.
I'l do my very best to get the fix out as soon as I can.
Jon Starbird February 27, 2015 at 1:27 AMEdited
I tried what Rade tried above but builds will still not show up and I still get the same error I posted elsewhere, ERROR: Unable to trigger JIRA to update builds of this job, JIRA responded with [411] Length Required, by the build job when it attempts to update Jira. I did check and the RPCURL is still set to the non-proxy URL but the plugin doesn't seem to be using it.
Then this error in the Jenkins system log: Failed to handle OAuth message: Failed to write editType
Just wanted to add that here since this is the issue that is supposed to address this.
Can we expect a fix for this anytime soon? Been waiting a long time now.
Currently the JIRA server will update the notifier post url in Jenkins with a fixed url pointing back to JIRA.
This improvement should result in:
The JIRA synchronisation process should configure the notifier with the application link id of the source JIRA server
The Jenkins build notifier should lookup the RPC url for JIRA using the application link id