Issues
- Plugin message although successful login / Job sync fails when job deleted in JenkinsJJI-334Resolved issue: JJI-334Mark Rekveld
- JIRA URL missing slash after portJJI-330Resolved issue: JJI-330
- Same Jenkins build notification show in JIRA CI Builds consoleJJI-308Resolved issue: JJI-308Mark Rekveld
- Jenkins Jira Integration issue on notification buildJJI-303Resolved issue: JJI-303Mark Rekveld
- Glitches after Jira 7 upgrade and Jira add-on upgradeJJI-302Resolved issue: JJI-302Mark Rekveld
- Error annotating messageJJI-299Resolved issue: JJI-299Mark Rekveld
- Wrong link in UI dialogJJI-298Resolved issue: JJI-298Mark Rekveld
- Deleting/Editing sites not possible after creationJJI-297Resolved issue: JJI-297Mark Rekveld
- Cleanup fo Jenkins jobs list not workingJJI-294Resolved issue: JJI-294Mark Rekveld
- Not able to configure the "Jenkins Integration for JIRA" plugin on JIRA 7.x serverJJI-292Resolved issue: JJI-292Mark Rekveld
- JIRA Jenkins integration - Not workingJJI-290Resolved issue: JJI-290Mark Rekveld
- Refactor JIRABuildNotifier to a more common RunListener implementationsJJI-287Resolved issue: JJI-287Mark Rekveld
- Unsatisfied requirement: (&(package=com.atlassian.jira.software.api.conditions))JJI-284Resolved issue: JJI-284Mark Rekveld
Plugin message although successful login / Job sync fails when job deleted in Jenkins
Description
Environment
Attachments
Activity
Mark Rekveld February 2, 2017 at 9:24 AM
Hi Tom,
Good to hear and you are welcome.
I'll go ahead and close this issue, but if needed please feel free to open a new issue or comment on this one.
Cheers,
Mark
Tom Pfueller February 2, 2017 at 7:06 AM
Dear Mark,
I was able to install the correct JIRA plugin in Jenkins and the error message on JIRA side disappeared.
Thank you very much and this is solved.
Kind regards
Tom
Mark Rekveld February 1, 2017 at 9:36 AM
Hi Tom,
The plugin that you installed on Jenkins is the one maintained by the Jenkins team and it not the one maintained and supported by Marvelution.
It is also not used by this project. If you want to use our plugin, then please refer to the release notes mentioned before and install the plugin supported by this project.
Cheers,
Mark
Tom Pfueller February 1, 2017 at 4:35 AM
Mark,
thank you for kind answer.
I tried the URL in my browser, but get an error.
Instead if I modify the URL like below I succeed.
https://xxx.xxglobal.com/jenkins/plugin/jira/help.html
Do you know why this happens. I believe that I have installed the correct JIRA plugin in Jenkins.
Tom
Mark Rekveld January 31, 2017 at 12:12 PM
Hi,
Just some background, the plugin on the Jenkins side is not required, the plugin on the JIRA side uses the default JSON API that Jenkins provides. The Jenkins side plugin is a simple notifier and changelog annotator to also provide features in Jenkins. The notifier is the method in which the Jenkins plugin can notify the JIRA plugin that a new build is ready for synchronization. This will speed up time in which the build data becomes available in JIRA.
That said, the JIRA plugin uses a simple HTTP GET request to check if the Jenkins side plugin is installed. For this it uses the URL
[jenkins-site-rpcurl]/plugin/jenkins-jira-plugin/static/help.htmlIf the plugin is able to synchronize data from Jenkins then it should able to able to request this URL to check if the Jenkins side plugin is installed. So I don't think your Apache proxy is blocking this since the authentication information is also added to this GET request.
A simple check you could do is open a browser and browse to the URL above replacing [jenkins-site-rpcurl] with the actual URL you configured in JIRA. This should give a response with the help text for the JIRA Build Notifier.
Cheers,
Mark
Hi,
I am trying out this plugin for the first time, but encounter two problems.
1) Although user authentication is successful, the plugin says that I should install the JIRA plugin on Jenkins side. But the plugin is installed and access from Jenkins to JIRA is successful. So the question is why does the check of JIRA plugin in Jenkins fail?
Additional information
Jenkins runs behind Apache and Apache checks user ID and Password (AuthBasicProvider file).
I have used the apiToken which is also the password for passing the Apache authentication.
2) Although I have deleted a job in Jenkins, JIRA does not delete the job when synchronizing. What can be the reason for this behavior and is there a way to fix this?
Kind regards
Tom