On 2/11/14 3:54 PM, "Nate Gordon" wrote:
>My goal is to eventually do a full build, deploy, configure, and
>automated tests against a scratch built local cloud with every commit from
>selected branches or daily from master (Hooray for nested virtualization
>and excess hardware)
Had done someth
Sorry for being a few days late on this.
I totally agree with the direction this conversation is going, but as
someone who has done build engineering in various incarnations over the
last couple of years, I would suggest two additional things. Build per
branch and gitflow. We have had good succe
On Fri, Feb 7, 2014 at 2:16 PM, Hugo Trippaers wrote:
> Hey David,
>
> I would make a distinction between code issues and functional issues.
> Occasionally somebody just plainly breaks the build, i'm guilty of that
> myself actually, and thats just plain stupid. Luckily we have Jenkins to
> cat
now. This would be a great if RM can enforce this
> >> during check ins - review unit tests and results before approving a
> >> check in.
> >>
> >> -----Original Message-
> >> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Tripp
Hi,
I used to work with gerrit in OS projects and I think the tool is great,
the integration with jenkins is cool.
One problem could be when jenkins infrastructure problems are frequent and
developers start to ignore warnings from jenkins.
With my particular project we were also frequently hit by
this practice now. This would be a great if RM can enforce this
>> during check ins - review unit tests and results before approving a
>> check in.
>>
>> -Original Message-
>> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
>> Sent:
ilto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Friday, February 07, 2014 12:46 AM
> To: dev
> Cc: jfarr...@apache.org
> Subject: Re: Code quality, QA, etc
>
> Hey David,
>
> I would make a distinction between code issues and functional issues.
> Occasionally
this during check
ins - review unit tests and results before approving a check in.
-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Friday, February 07, 2014 12:46 AM
To: dev
Cc: jfarr...@apache.org
Subject: Re: Code quality, QA, etc
Hey
Hey David,
I would make a distinction between code issues and functional issues.
Occasionally somebody just plainly breaks the build, i’m guilty of that myself
actually, and thats just plain stupid. Luckily we have Jenkins to catch these
errors quickly. I’m in a continuous struggle with Jenkins
