On Tue, Nov 29, 2011 at 10:25 AM, Stephen Connolly
wrote:
> Will need the jenkins jobs to clean their local repo periodically in case
> of re-votes
>
> On 29 November 2011 15:24, Benson Margulies wrote:
>
>> Indeed nexus has a feature that allows a single, persistent, group, to
>> map to whatever
Will need the jenkins jobs to clean their local repo periodically in case
of re-votes
On 29 November 2011 15:24, Benson Margulies wrote:
> Indeed nexus has a feature that allows a single, persistent, group, to
> map to whatever staging repos we have pending. I've opened an INFRA
> ticket to make
Indeed nexus has a feature that allows a single, persistent, group, to
map to whatever staging repos we have pending. I've opened an INFRA
ticket to make use of this, and I will proceed to improve the Jenkins
jobs to use it unless someone objects.
--
2011/11/29 Arnaud Héritier :
> What I'm doing at eXo to manage such cascading releases without having a
> huge manual process to keep everything up-to-date is that I have a profile
> that allow to activate a group with all staging repositories. Jenkins is
> allowed to take artifacts from this stagi
What I'm doing at eXo to manage such cascading releases without having a
huge manual process to keep everything up-to-date is that I have a profile
that allow to activate a group with all staging repositories. Jenkins is
allowed to take artifacts from this staging group BUT it has to delete all
loc
I'd just vote on both at the same time... jenkins can fail if it wants...
or I can see about getting Apache a license for skippy (a.k.a. CloudBee's
Skip Builds plugin)
On 29 November 2011 13:22, Benson Margulies wrote:
> This morning, I considered the following:
>
> 1) Stage maven-common-filters
This morning, I considered the following:
1) Stage maven-common-filters 1.4 and call a vote
2) Make a settings.xml for myself that included the staging repo.
3) Update maven-assembly-plugin to use maven-common-filters 1.4,
building using the settings.xml.
4) stage maven-assembly-plugin and call
