Re: [DISCUSS] Remove Jenkins integration with JIRA

2013-11-14 Thread Francesco Chicchiriccò

FYI: https://issues.apache.org/jira/browse/INFRA-7006

On 14/11/2013 11:10, Colm O hEigeartaigh wrote:

Sure, makes sense to me.

Colm.


On Thu, Nov 14, 2013 at 9:08 AM, Francesco Chicchiriccò 
wrote:
Hi all,
recently we've got back the feature of generating JIRA comments from SVN
commits, disabled a while ago as you might remember because of some
malfunctioning of that plugin.

At that time we requested to enable the Jenkins integration with JIRA in
order to have some automatic mechanism to bind commits (mentioned by
Jenkins builds) to JIRA issues.
Nowadays this is no more necessary; moreover, Jenkins often fails for
various reasons - most times it is just some network issue while deploying
artifacts to Nexus - but we end up with some ugly FAILURE comments on our
JIRA issues.

Hence my proposal: request INFRA to disable the Jenkins2JIRA integration
and manually handle Jenkins failures - as we are doing currently. I
remember that, driven by our github mirror, we also have Travis [1] taking
care of CI.

WDYT?

[1] https://travis-ci.org/apache/syncope


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/



Re: [DISCUSS] Remove Jenkins integration with JIRA

2013-11-14 Thread Colm O hEigeartaigh
Sure, makes sense to me.

Colm.


On Thu, Nov 14, 2013 at 9:08 AM, Francesco Chicchiriccò  wrote:

> Hi all,
> recently we've got back the feature of generating JIRA comments from SVN
> commits, disabled a while ago as you might remember because of some
> malfunctioning of that plugin.
>
> At that time we requested to enable the Jenkins integration with JIRA in
> order to have some automatic mechanism to bind commits (mentioned by
> Jenkins builds) to JIRA issues.
> Nowadays this is no more necessary; moreover, Jenkins often fails for
> various reasons - most times it is just some network issue while deploying
> artifacts to Nexus - but we end up with some ugly FAILURE comments on our
> JIRA issues.
>
> Hence my proposal: request INFRA to disable the Jenkins2JIRA integration
> and manually handle Jenkins failures - as we are doing currently. I
> remember that, driven by our github mirror, we also have Travis [1] taking
> care of CI.
>
> WDYT?
>
> [1] https://travis-ci.org/apache/syncope
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~ilgrosso/
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com


[DISCUSS] Remove Jenkins integration with JIRA

2013-11-14 Thread Francesco Chicchiriccò

Hi all,
recently we've got back the feature of generating JIRA comments from SVN 
commits, disabled a while ago as you might remember because of some 
malfunctioning of that plugin.


At that time we requested to enable the Jenkins integration with JIRA in 
order to have some automatic mechanism to bind commits (mentioned by 
Jenkins builds) to JIRA issues.
Nowadays this is no more necessary; moreover, Jenkins often fails for 
various reasons - most times it is just some network issue while 
deploying artifacts to Nexus - but we end up with some ugly FAILURE 
comments on our JIRA issues.


Hence my proposal: request INFRA to disable the Jenkins2JIRA integration 
and manually handle Jenkins failures - as we are doing currently. I 
remember that, driven by our github mirror, we also have Travis [1] 
taking care of CI.


WDYT?

[1] https://travis-ci.org/apache/syncope

--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/