I read the Hudson/Jira integration in wiki, http://weblogs.java.net/blog/kohsuke/archive/2007/03/hudsonjira_inte.html
I saw the configuration instruction in the wiki, but in practice, how does it work?My question is, how does Jira knows about Hudson's build information and how does Hudson's build link to Jira? How does a Jira issue link to fixes and revision in a build?
Anyone can list the step by step workflow?
The work is all done on hudson’s end. We use JIRA’s webservices.
Basically you configure on a global basis the jira credentials necessary for us to connect via soap.
Then in the individual Hudson projects, when you enable update relevant JIRA issues it queries jira for projects that match the Hudson project name. If it finds one it will publish information from the build into that issue. It does that based on your scm checkin comments. So if the changelog for a build contains a comment like “VND-115 blahhh blahhh” it will look for a ticket in the vnd project identified as VND-115 in jira. It will create a comment in that ticket that contains the contents of the changelog item and will include in that comment the url back to the Hudson build. Also in the Hudson build in the “Changes” section for that build where it lists the changelog it will highlight the VND-115 portion of the checkin comment and make it a url link back to the jira ticket so that if you’re in Hudson you can easily jump to the ticket and if you are in jira you can click from the comment straight to the relevant build that changed something about the ticket.
It’s been a little while since I went through the code (last time I fixed a bug) but that should basically be the gist of how it works – we’re using it successfully here and its been quite useful. Future enhancements are more keyword recognition in the scm comment parsing so that we can change status on a ticket to say resolved instead of just adding a comment. Also requested was some sort of user mapping from Hudson to jira so that we could make it look like the comments came from individual users instead of just one generic “build” user.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Yay! It works. Andrew, thank you for your information :)
On Wed, Oct 29, 2008 at 8:31 AM, Andrew Chandler <[hidden email]> wrote:
This post has NOT been accepted by the mailing list yet.
In reply to this post by Andrew Chandler
Hi Andrew ,
We had working setup for Jira and Hudson ( setup was done by someone in past , not with organization anymore ) . It was working fine.
On Hudson configuration page , we could see the Jira user used as "hudson" , but we dint know it's password so we logged in to Jira and reset it .
But that broke Hudson configuration and we are getting the error message , on Hudson configuration page as :
"com.atlassian.jira.rpc.exception.RemoteAuthenticationException: An elevated security check is required for 'hudson'. They have not been allowed an attempt to authenticate."
Can someone please advise urgently..
|Powered by Nabble||Edit this page|