I am trying to setup a link between Jira 6.3.3 an Jenkins 1.554LTS to communicate the results of the Jenkins builds to the Jira tickets.
However, I am not getting the application links defined in either Jenkins and Jira.
When defining an application link in Jenkins (via "Manage Jenkins > Configure System") the entry does not show in the Application Links link in the Manage Jenkins menu.
When defining the application link in Jira I get the message that the Jenkins link can not be found.
"Application 'Jenkins' seems to be offline. Click here to Relocate."
I've installed the latest version of this plugin, 1.4.7, in Jira and Jenkins.
You should be able to configure links between JIRA and Jenkins from JIRA using the new Application Link wiard. When in JIRA, go to Addons > Application Links. Provide the URL to jenkins and clink the "Create a new link" button. Then follow the wiard.
After this is done, go to Addons > Jenkins Configuration (Under source control). There you should be able to see a list of all the Jobs known on Jenkins. Where you can check the jobs you want to sync the builds of and that will participate in the builds panels.
Not sure how to get the logs at moment, but the addon is definitely installed, modules show it's registered as Application Link event listener.
Looking at the screenshots, all seems oke except for the missing two application type options Jenkins and Hudson.
Do your JIRA log file(s) print any exceptions?
If you don't want to add log files here you can create a new ticket at https://marvelution.atlassian.net/browse/JJIand select "Private Information" as security level.
The atlassian-jira.log Also contains the following errors:
2014-09-01 09:25:10,386 http-bio-8080-exec-6 WARN <USERNAME> 564x144273x1 c9rjyb 10.120.24.37 /plugins/servlet/applinks/listEntityLinks/com.atlassian.applinks.api.application.jira.JiraProjectEntityType/ATA [plugins.jenkins.applinks.JenkinsManifestProducer] Unable to get the manifest for http://XXXXXX:8080
2014-08-29 14:28:17,869 http-bio-8080-exec-9 WARN <USERNAME> 868x125950x1 1oib9gq 10.120.24.27 /plugins/servlet/streams [atlassian.streams.internal.StreamsCompletionService] Registering failure for stream provider <JENKINS> due to error other
which are repeated throughout the logs
This error explains way you would need to provide the details for Jenkins link by hand, like application type, name.
Are there any other errors in the log? There should be an error related to the Jenkins Application Type itself. I think that the missing Jenkins Application Type is the cause of the issue.
I think I did that. See my settings below
Application Name Jenkins_1694
Application Type Jenkins
Application URL http://einz1694:8080<br< a="">>This is the URL used to connect to the remote application from this server.
Display URL http://einz1694:8080<br< a="">>The display URL is used when rendering links to the application in the user's browser.
I also found the following error in the log file
2014-08-29 16:10:51,865 http-bio-8080-exec-24 WARN anonymous 970x130409x1 1y5ie56 10.120.24.172 /activity [atlassian.streams.internal.StreamsCompletionService] Registering failure for stream provider Jenkins_1694 due to error other
Yes, I've installed the latest version of this plugin, 1.4.7, in Jira 6.3.3 and Jenkins 1.554LTS.
Just to be sure: In the application link in Jenkins I am defining the application URL ( http:<ip of JIRA server>:8080 ) ? I did that, but when in Jenkins under 'Manage Jenkins' the 'Application Links' report:
No application links are configured
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs