JIRA / Hudson integration question

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

JIRA / Hudson integration question

Ilko Iliev-3
Hi,

I'm trying to integrate our hudson and JIRA instances follwong the instructions on the wiki and the post http://www.nabble.com/How-can-does-Hudson-Jira-integration-works--td20221008.html here. As far as I can understand the match to the Jira issues is done based on the Project ID - if I have UIR-123 in Jira the Hudson job should / must be named UIR? If this is the case what if I have several jobs to build the same project as it is in my case - for example I have release job in which I'd like to have the changeset connected to the Jira issues, too? Or would the issues be copied in this case from the CI build job? Some "best practices" on the topic will be appreciated.

Thanks,
Ilko
Reply | Threaded
Open this post in threaded view
|

RE: JIRA / Hudson integration question

Ulli Hafner-2
There is no naming convention for a job. The repository commit message needs to reference the Jira project, e.g. "Fixed issue UIR-123.". Then Hudson automatically maps everything...
 
Ulli
 


From: Ilko Iliev [mailto:[hidden email]]
Sent: Tuesday, June 30, 2009 12:52 PM
To: [hidden email]
Subject: JIRA / Hudson integration question

Hi,

I'm trying to integrate our hudson and JIRA instances follwong the instructions on the wiki and the post http://www.nabble.com/How-can-does-Hudson-Jira-integration-works--td20221008.html here. As far as I can understand the match to the Jira issues is done based on the Project ID - if I have UIR-123 in Jira the Hudson job should / must be named UIR? If this is the case what if I have several jobs to build the same project as it is in my case - for example I have release job in which I'd like to have the changeset connected to the Jira issues, too? Or would the issues be copied in this case from the CI build job? Some "best practices" on the topic will be appreciated.

Thanks,
Ilko
Reply | Threaded
Open this post in threaded view
|

Re: JIRA / Hudson integration question

Ilko Iliev-3
ok - the documentation is then not up to date...

on the other side this means that there is something wrong with the communication between Jira and Hudson even if I don't see any errors at least on the hudson's side - I have my comment as:

2009-06-25 impl UIR-12

and nothing is linked to this comment.

Do I need to set the authentication and enable Jira remote communication even if I don't need any update from hudson on the Jira issues? This was not clear to me and I leave the authentication fields empty resp. didn't change anything in Jira for now - I don't have control over Jira to check the settings there.

Thanks,
Ilko

On Tue, Jun 30, 2009 at 2:31 PM, Hafner Ullrich <[hidden email]> wrote:
There is no naming convention for a job. The repository commit message needs to reference the Jira project, e.g. "Fixed issue UIR-123.". Then Hudson automatically maps everything...
 
Ulli
 


From: Ilko Iliev [mailto:[hidden email]]
Sent: Tuesday, June 30, 2009 12:52 PM
To: [hidden email]
Subject: JIRA / Hudson integration question

Hi,

I'm trying to integrate our hudson and JIRA instances follwong the instructions on the wiki and the post http://www.nabble.com/How-can-does-Hudson-Jira-integration-works--td20221008.html here. As far as I can understand the match to the Jira issues is done based on the Project ID - if I have UIR-123 in Jira the Hudson job should / must be named UIR? If this is the case what if I have several jobs to build the same project as it is in my case - for example I have release job in which I'd like to have the changeset connected to the Jira issues, too? Or would the issues be copied in this case from the CI build job? Some "best practices" on the topic will be appreciated.

Thanks,
Ilko

Reply | Threaded
Open this post in threaded view
|

RE: Re: JIRA / Hudson integration question

Ulli Hafner-2
Yes, you need to enable remote communication and set the user/password if you would like to get updates in the issue comments.
 
Ull 


From: Ilko Iliev [mailto:[hidden email]]
Sent: Tuesday, June 30, 2009 3:22 PM
To: [hidden email]
Subject: Re: JIRA / Hudson integration question

ok - the documentation is then not up to date...

on the other side this means that there is something wrong with the communication between Jira and Hudson even if I don't see any errors at least on the hudson's side - I have my comment as:

2009-06-25 impl UIR-12

and nothing is linked to this comment.

Do I need to set the authentication and enable Jira remote communication even if I don't need any update from hudson on the Jira issues? This was not clear to me and I leave the authentication fields empty resp. didn't change anything in Jira for now - I don't have control over Jira to check the settings there.

Thanks,
Ilko

On Tue, Jun 30, 2009 at 2:31 PM, Hafner Ullrich <[hidden email]> wrote:
There is no naming convention for a job. The repository commit message needs to reference the Jira project, e.g. "Fixed issue UIR-123.". Then Hudson automatically maps everything...
 
Ulli
 


From: Ilko Iliev [mailto:[hidden email]]
Sent: Tuesday, June 30, 2009 12:52 PM
To: [hidden email]
Subject: JIRA / Hudson integration question

Hi,

I'm trying to integrate our hudson and JIRA instances follwong the instructions on the wiki and the post http://www.nabble.com/How-can-does-Hudson-Jira-integration-works--td20221008.html here. As far as I can understand the match to the Jira issues is done based on the Project ID - if I have UIR-123 in Jira the Hudson job should / must be named UIR? If this is the case what if I have several jobs to build the same project as it is in my case - for example I have release job in which I'd like to have the changeset connected to the Jira issues, too? Or would the issues be copied in this case from the CI build job? Some "best practices" on the topic will be appreciated.

Thanks,
Ilko

Reply | Threaded
Open this post in threaded view
|

Re: Re: JIRA / Hudson integration question

Ilko Iliev-3
thanks for the quick reply - last question - what permissions does the user require?

thanks,
Ilko

On Tue, Jun 30, 2009 at 3:27 PM, Hafner Ullrich <[hidden email]> wrote:
Yes, you need to enable remote communication and set the user/password if you would like to get updates in the issue comments.
 
Ull 


From: Ilko Iliev [mailto:[hidden email]]
Sent: Tuesday, June 30, 2009 3:22 PMSubject: Re: JIRA / Hudson integration question

ok - the documentation is then not up to date...

on the other side this means that there is something wrong with the communication between Jira and Hudson even if I don't see any errors at least on the hudson's side - I have my comment as:

2009-06-25 impl UIR-12

and nothing is linked to this comment.

Do I need to set the authentication and enable Jira remote communication even if I don't need any update from hudson on the Jira issues? This was not clear to me and I leave the authentication fields empty resp. didn't change anything in Jira for now - I don't have control over Jira to check the settings there.

Thanks,
Ilko

On Tue, Jun 30, 2009 at 2:31 PM, Hafner Ullrich <[hidden email]> wrote:
There is no naming convention for a job. The repository commit message needs to reference the Jira project, e.g. "Fixed issue UIR-123.". Then Hudson automatically maps everything...
 
Ulli
 


From: Ilko Iliev [mailto:[hidden email]]
Sent: Tuesday, June 30, 2009 12:52 PM
To: [hidden email]
Subject: JIRA / Hudson integration question

Hi,

I'm trying to integrate our hudson and JIRA instances follwong the instructions on the wiki and the post http://www.nabble.com/How-can-does-Hudson-Jira-integration-works--td20221008.html here. As far as I can understand the match to the Jira issues is done based on the Project ID - if I have UIR-123 in Jira the Hudson job should / must be named UIR? If this is the case what if I have several jobs to build the same project as it is in my case - for example I have release job in which I'd like to have the changeset connected to the Jira issues, too? Or would the issues be copied in this case from the CI build job? Some "best practices" on the topic will be appreciated.

Thanks,
Ilko