You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mrunit.apache.org by Jim Donofrio <do...@gmail.com> on 2012/09/09 19:23:43 UTC
Jenkins will now automatically add commit information in JIRA
I checked the box in JIRA to update relevant JIRA issues so that Jenkins
will update JIRA's below with a link to the commit.
Jarek,
I also removed the ;a=summary from the Jenkins link because that was not
a correct link when adding the a=commit part of the link.
-------- Original Message --------
Subject: [jira] [Commented] (MRUNIT-147) upgrade parent pom to version 11
Date: Mon, 10 Sep 2012 04:19:07 +1100 (NCT)
From: Hudson (JIRA) <ji...@apache.org>
Reply-To: dev@mrunit.apache.org
To: dev@mrunit.apache.org
[ https://issues.apache.org/jira/browse/MRUNIT-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451631#comment-13451631 ]
Hudson commented on MRUNIT-147:
-------------------------------
Integrated in mrunit-trunk #134 (See [https://builds.apache.org/job/mrunit-trunk/134/])
MRUNIT-147: upgrade parent pom to version 11 (Revision 57b5850b9f452d534025f467ae9d3346554a1b5f)
Result = SUCCESS
jdonofrio : https://git-wip-us.apache.org/repos/asf?p=mrunit.git&a=commit&h=57b5850b9f452d534025f467ae9d3346554a1b5f
Files :
* pom.xml
> upgrade parent pom to version 11
> --------------------------------
>
> Key: MRUNIT-147
> URL: https://issues.apache.org/jira/browse/MRUNIT-147
> Project: MRUnit
> Issue Type: Task
> Reporter: Jim Donofrio
> Assignee: Jim Donofrio
> Priority: Trivial
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Jenkins will now automatically add commit information in JIRA
Posted by Brock Noland <br...@cloudera.com>.
Cool!
On Sun, Sep 9, 2012 at 12:23 PM, Jim Donofrio <do...@gmail.com> wrote:
> I checked the box in JIRA to update relevant JIRA issues so that Jenkins
> will update JIRA's below with a link to the commit.
>
> Jarek,
>
> I also removed the ;a=summary from the Jenkins link because that was not a
> correct link when adding the a=commit part of the link.
>
> -------- Original Message --------
> Subject: [jira] [Commented] (MRUNIT-147) upgrade parent pom to
> version 11
> Date: Mon, 10 Sep 2012 04:19:07 +1100 (NCT)
> From: Hudson (JIRA) <ji...@apache.org>
> Reply-To: dev@mrunit.apache.org
> To: dev@mrunit.apache.org
>
>
>
> [
> https://issues.apache.org/jira/browse/MRUNIT-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451631#comment-13451631
> ]
>
> Hudson commented on MRUNIT-147:
> -------------------------------
>
> Integrated in mrunit-trunk #134 (See
> [https://builds.apache.org/job/mrunit-trunk/134/])
> MRUNIT-147: upgrade parent pom to version 11 (Revision
> 57b5850b9f452d534025f467ae9d3346554a1b5f)
>
> Result = SUCCESS
> jdonofrio :
> https://git-wip-us.apache.org/repos/asf?p=mrunit.git&a=commit&h=57b5850b9f452d534025f467ae9d3346554a1b5f
> Files :
> * pom.xml
>
>
>>
>> upgrade parent pom to version 11
>> --------------------------------
>>
>> Key: MRUNIT-147
>> URL: https://issues.apache.org/jira/browse/MRUNIT-147
>> Project: MRUnit
>> Issue Type: Task
>> Reporter: Jim Donofrio
>> Assignee: Jim Donofrio
>> Priority: Trivial
>>
>
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
>
--
Apache MRUnit - Unit testing MapReduce - http://incubator.apache.org/mrunit/
Re: Jenkins will now automatically add commit information in JIRA
Posted by Jim Donofrio <do...@gmail.com>.
No there is no policy, I just happened to notice there was a newer
version of the parent pom. The only changes were new plugin versions so
I decided it would be safe to switch to it.
On 09/10/2012 01:32 AM, Jarek Jarcec Cecho wrote:
> Thank you Jim for fixing the broken link.
>
> I'm expecting that I should have increase the version number myself when I was doing the changes in MRUNIT-146. Do we have policy somewhere when the version should be increased?
>
> Jarcec
>
> On Sun, Sep 09, 2012 at 01:23:43PM -0400, Jim Donofrio wrote:
>> I checked the box in JIRA to update relevant JIRA issues so that
>> Jenkins will update JIRA's below with a link to the commit.
>>
>> Jarek,
>>
>> I also removed the ;a=summary from the Jenkins link because that was
>> not a correct link when adding the a=commit part of the link.
>>
>> -------- Original Message --------
>> Subject: [jira] [Commented] (MRUNIT-147) upgrade parent pom to version 11
>> Date: Mon, 10 Sep 2012 04:19:07 +1100 (NCT)
>> From: Hudson (JIRA) <ji...@apache.org>
>> Reply-To: dev@mrunit.apache.org
>> To: dev@mrunit.apache.org
>>
>>
>>
>> [ https://issues.apache.org/jira/browse/MRUNIT-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451631#comment-13451631 ]
>>
>> Hudson commented on MRUNIT-147:
>> -------------------------------
>>
>> Integrated in mrunit-trunk #134 (See [https://builds.apache.org/job/mrunit-trunk/134/])
>> MRUNIT-147: upgrade parent pom to version 11 (Revision 57b5850b9f452d534025f467ae9d3346554a1b5f)
>>
>> Result = SUCCESS
>> jdonofrio : https://git-wip-us.apache.org/repos/asf?p=mrunit.git&a=commit&h=57b5850b9f452d534025f467ae9d3346554a1b5f
>> Files :
>> * pom.xml
>>
>>> upgrade parent pom to version 11
>>> --------------------------------
>>>
>>> Key: MRUNIT-147
>>> URL: https://issues.apache.org/jira/browse/MRUNIT-147
>>> Project: MRUnit
>>> Issue Type: Task
>>> Reporter: Jim Donofrio
>>> Assignee: Jim Donofrio
>>> Priority: Trivial
>>>
>>
>> --
>> This message is automatically generated by JIRA.
>> If you think it was sent incorrectly, please contact your JIRA administrators
>> For more information on JIRA, see: http://www.atlassian.com/software/jira
>>
>>
>>
>>
Re: Jenkins will now automatically add commit information in JIRA
Posted by Jarek Jarcec Cecho <ja...@apache.org>.
Thank you Jim for fixing the broken link.
I'm expecting that I should have increase the version number myself when I was doing the changes in MRUNIT-146. Do we have policy somewhere when the version should be increased?
Jarcec
On Sun, Sep 09, 2012 at 01:23:43PM -0400, Jim Donofrio wrote:
> I checked the box in JIRA to update relevant JIRA issues so that
> Jenkins will update JIRA's below with a link to the commit.
>
> Jarek,
>
> I also removed the ;a=summary from the Jenkins link because that was
> not a correct link when adding the a=commit part of the link.
>
> -------- Original Message --------
> Subject: [jira] [Commented] (MRUNIT-147) upgrade parent pom to version 11
> Date: Mon, 10 Sep 2012 04:19:07 +1100 (NCT)
> From: Hudson (JIRA) <ji...@apache.org>
> Reply-To: dev@mrunit.apache.org
> To: dev@mrunit.apache.org
>
>
>
> [ https://issues.apache.org/jira/browse/MRUNIT-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451631#comment-13451631 ]
>
> Hudson commented on MRUNIT-147:
> -------------------------------
>
> Integrated in mrunit-trunk #134 (See [https://builds.apache.org/job/mrunit-trunk/134/])
> MRUNIT-147: upgrade parent pom to version 11 (Revision 57b5850b9f452d534025f467ae9d3346554a1b5f)
>
> Result = SUCCESS
> jdonofrio : https://git-wip-us.apache.org/repos/asf?p=mrunit.git&a=commit&h=57b5850b9f452d534025f467ae9d3346554a1b5f
> Files :
> * pom.xml
>
> >upgrade parent pom to version 11
> >--------------------------------
> >
> > Key: MRUNIT-147
> > URL: https://issues.apache.org/jira/browse/MRUNIT-147
> > Project: MRUnit
> > Issue Type: Task
> > Reporter: Jim Donofrio
> > Assignee: Jim Donofrio
> > Priority: Trivial
> >
>
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
>