establish PreCommit build(s) on EC2 Jenkins

[Ted Yu <yu...@gmail.com>]

Hi,
I mentioned this initiative in the thread Andrew started.
As of my latest check, Apache Jenkins is still down. It has been off most
of time this week.
So we need to find an alternative.

Besides, we need EC2 where hostnames regularly contain hyphens. On the
Apache Jenkins, it wouldn't be easy to test the fix for the following JIRA:
HBASE-8207 Replication could have data loss when machine name contains
hyphen "-"

Please comment.

Thanks

Re: establish PreCommit build(s) on EC2 Jenkins

[Andrew Purtell <ap...@apache.org>]

This discussion may be premature. We hope the issues with the Apache
Jenkins VM farm can be successfully resolved soon. My management is happy
to support this for as long as the Apache Jenkins farm is having issues.
Beyond that, let's have a discussion then. Whatever is the long term
disposition of these systems is up to HBase, really. They are eminently
portable. We could easily make a new AMI of Jenkins at whatever is its
current state (it's an EBS based instance) and hand it off. Likewise, the
PV slave AMI bits and manifest can be transferred to another S3 bucket and
registered to any other account.

> > A vote to formally adopt Andrew's new deployment?
>  A vote may be needed in the future.

I don't understand, but no matter because it doesn't sound like you want to
do this now.

> We can create a PreCommit build which accepts JIRA number as input.
Before QA run is tied up to JIRA system, one of the admins has to trigger
QA build for that JIRA number.

Jenkins has a RESTful API and I've also installed the JIRA plugin on this
instance. Some sort of two way integration would not be much of a challenge
set up. The big detail would be what IP address(es) to whitelist for
Jenkins API access.


On Thu, Mar 28, 2013 at 3:29 PM, Ted Yu <yu...@gmail.com> wrote:

> bq. A vote to formally adopt Andrew's new deployment?
>
> A vote may be needed in the future. My intention was to prepare for full
> integration with JIRA system. See third answer below.
>
> bq. A resolution to fund the environment via Apache?
>
> Outside scope of my initial email.
>
> bq. Someone to get INFRA to provide this for us?
>
> I doubt INFRA has bandwidth to cover this request.
> We can create a PreCommit build which accepts JIRA number as input. Before
> QA run is tied up to JIRA system, one of the admins has to trigger QA build
> for that JIRA number.
> Once proof of concept passes, we can request INFRA to point Hadoop QA at
> EC2 Jenkins.
>
> Thanks
>
> On Thu, Mar 28, 2013 at 3:19 PM, Nick Dimiduk <nd...@gmail.com> wrote:
>
> > Ted,
> >
> > What are you asking for specifically? A vote to formally adopt Andrew's
> new
> > deployment? A resolution to fund the environment via Apache? Someone to
> get
> > INFRA to provide this for us?
> >
> > Thanks,
> > Nick
> >
> > On Thu, Mar 28, 2013 at 11:27 AM, Ted Yu <yu...@gmail.com> wrote:
> >
> > > Hi,
> > > I mentioned this initiative in the thread Andrew started.
> > > As of my latest check, Apache Jenkins is still down. It has been off
> most
> > > of time this week.
> > > So we need to find an alternative.
> > >
> > > Besides, we need EC2 where hostnames regularly contain hyphens. On the
> > > Apache Jenkins, it wouldn't be easy to test the fix for the following
> > JIRA:
> > > HBASE-8207 Replication could have data loss when machine name contains
> > > hyphen "-"
> > >
> > > Please comment.
> > >
> > > Thanks
> > >
> >
>


-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

Re: establish PreCommit build(s) on EC2 Jenkins

[Ted Yu <yu...@gmail.com>]

bq. A vote to formally adopt Andrew's new deployment?

A vote may be needed in the future. My intention was to prepare for full
integration with JIRA system. See third answer below.

bq. A resolution to fund the environment via Apache?

Outside scope of my initial email.

bq. Someone to get INFRA to provide this for us?

I doubt INFRA has bandwidth to cover this request.
We can create a PreCommit build which accepts JIRA number as input. Before
QA run is tied up to JIRA system, one of the admins has to trigger QA build
for that JIRA number.
Once proof of concept passes, we can request INFRA to point Hadoop QA at
EC2 Jenkins.

Thanks

On Thu, Mar 28, 2013 at 3:19 PM, Nick Dimiduk <nd...@gmail.com> wrote:

> Ted,
>
> What are you asking for specifically? A vote to formally adopt Andrew's new
> deployment? A resolution to fund the environment via Apache? Someone to get
> INFRA to provide this for us?
>
> Thanks,
> Nick
>
> On Thu, Mar 28, 2013 at 11:27 AM, Ted Yu <yu...@gmail.com> wrote:
>
> > Hi,
> > I mentioned this initiative in the thread Andrew started.
> > As of my latest check, Apache Jenkins is still down. It has been off most
> > of time this week.
> > So we need to find an alternative.
> >
> > Besides, we need EC2 where hostnames regularly contain hyphens. On the
> > Apache Jenkins, it wouldn't be easy to test the fix for the following
> JIRA:
> > HBASE-8207 Replication could have data loss when machine name contains
> > hyphen "-"
> >
> > Please comment.
> >
> > Thanks
> >
>

Re: establish PreCommit build(s) on EC2 Jenkins

[Nick Dimiduk <nd...@gmail.com>]

Ted,

What are you asking for specifically? A vote to formally adopt Andrew's new
deployment? A resolution to fund the environment via Apache? Someone to get
INFRA to provide this for us?

Thanks,
Nick

On Thu, Mar 28, 2013 at 11:27 AM, Ted Yu <yu...@gmail.com> wrote:

> Hi,
> I mentioned this initiative in the thread Andrew started.
> As of my latest check, Apache Jenkins is still down. It has been off most
> of time this week.
> So we need to find an alternative.
>
> Besides, we need EC2 where hostnames regularly contain hyphens. On the
> Apache Jenkins, it wouldn't be easy to test the fix for the following JIRA:
> HBASE-8207 Replication could have data loss when machine name contains
> hyphen "-"
>
> Please comment.
>
> Thanks
>