Re: [DISCUSS] Deprecating jenkins.cs.o

Jake Farrell Sat, 10 Nov 2012 09:26:06 -0800

Let me know what I can do to help with this transition and getting Cloudstack accounts setup on builds.a.o

-Jake

prasanna

November 10, 2012 11:30 AM

+1, Let's go for it!

Chip Childers

November 9, 2012 2:48 PM
On Sun, Nov 4, 2012 at 4:57 PM, David Nalley <da...@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?
+1 to moving this, but I'm not necessarily volunteering to make the changes ;-)

Anyone else have an opinion?
--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/
David Nalley

November 4, 2012 4:57 PM

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/

Re: [DISCUSS] Deprecating jenkins.cs.o

Reply via email to