incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Kinsella <...@stratosec.co>
Subject Re: [DISCUSS] Deprecating jenkins.cs.o
Date Wed, 26 Dec 2012 19:18:56 GMT
Just checking in on this one as well…

On Nov 4, 2012, at 1:57 PM, David Nalley <david@gnsa.us> wrote:

> Hi folks:
> 
> Our existing jenkins instance is housed on my AWS account [1].
> However, since its inception, the project has moved to the Apache
> Software Foundation; and the ASF has its own Jenkins instance [2].
> We've also moved past a large hurdle in working through our first
> release - and as we start to ramp up towards 4.next I'd like to
> propose that we begin transitioning to the ASF jenkins instance
> (though we likely will use slaves that are not part of the ASF's
> infrastructure much like Hadoop does due to our unique constraints,
> that aren't easily solved by things like VMs.
> 
> So - first any opposition to this move? Is there any reason the ASF
> jenkins instance will not work for the project? (There could well be
> valid reasons - I do note that Apache Bigtop runs a separate jenkins
> instance and there may well be others)
> 
> If we don't end up with any opposition, I'd like to propose that we
> consider jenkins.cs.o frozen and no new tests be added there; and
> begin working on getting things moved to the ASF jenkins instance.
> 
> Thoughts, comments, flames?
> 
> --David
> 
> [1] Yes I know, I should have used a CloudStack instance instead of
> AWS, however my CloudStack instance was in disrepair at the time, and
> it seemed relatively fast to do so on AWS and it was intended to be
> 'temporary'
> [2] https://builds.apache.org/
> 

Stratosec - Secure Infrastructure as a Service
o: 415.315.9385
@johnlkinsella


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message