On Mon, Jul 15, 2013 at 03:06:41PM +0530, Girish Shilamkar wrote:
> Alex,
>
> On 10-Jul-2013, at 9:32 AM, Alex Huang
> wrote:
>
> > Sorry this took a little longer than expected with the holiday in
> > US. Here's the first proposal [1] on the automated test system.
> > Comments welcome.
> >
y, June 28, 2013 8:44 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [DISCUSS] If BVT breaks, revert the commits...
>>
>> On Fri, Jun 28, 2013 at 8:18 PM, Alex Huang wrote:
>>> After Dave's complain in the vmsync [MERGE] thread about BVT in horrible
>
STACK/Automated+Tests+Rules+and+Guidelines
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Friday, June 28, 2013 8:44 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] If BVT breaks, revert the commits...
>
> On Fri, Jun 28, 2013 at
On Sat, Jun 29, 2013 at 12:31:31PM -0400, David Nalley wrote:
> On Sat, Jun 29, 2013 at 12:45 AM, Prasanna Santhanam wrote:
> > On Sat, Jun 29, 2013 at 12:18:17AM +, Alex Huang wrote:
> >>
> >> To avoid having a bunch of reverts and resubmits, the developers
> >> should be able to request that
On Sat, Jun 29, 2013 at 12:45 AM, Prasanna Santhanam wrote:
> On Sat, Jun 29, 2013 at 12:18:17AM +, Alex Huang wrote:
>> After Dave's complain in the vmsync [MERGE] thread about BVT in
>> horrible shape on master, I went around to figure out what exactly
>> happened. The best I can figure is
On Sat, Jun 29, 2013 at 12:18:17AM +, Alex Huang wrote:
> After Dave's complain in the vmsync [MERGE] thread about BVT in
> horrible shape on master, I went around to figure out what exactly
> happened. The best I can figure is that after a certain merge (I
> will leave out which merge as that
On Fri, Jun 28, 2013 at 8:18 PM, Alex Huang wrote:
> After Dave's complain in the vmsync [MERGE] thread about BVT in horrible
> shape on master, I went around to figure out what exactly happened. The best
> I can figure is that after a certain merge (I will leave out which merge as
> that's no
> This only thing i'm a bit afraid of is the technical side of reverting a
> merge. It's
> one of those this that you need to be careful with in git.
I think this means all merges must come in as one big squashed patch. If they
come in as multiple commits or rebase, then it gets reverted automa
Alex,
+1
From the jenkins side we could make more jobs with parameters so anyone can
kick-off a test run on his/her branch. I don't know if that would work for the
BVT tests though.
This only thing i'm a bit afraid of is the technical side of reverting a merge.
It's one of those this that you
