On Dec 11, 2012, at 10:53 PM, "Roy Stogner" wrote:
> A) given another patch designed specifically to fix the failed tests,
> B) reverted to any other newer-than-Master revision that hasn't been
> tested (in cases where multiple patches were added too fast for
> buildbot to test)
> C) reverted com
On Tue, Dec 11, 2012 at 9:53 PM, Roy Stogner wrote:
>
> On Tue, 11 Dec 2012, Kirk, Benjamin (JSC-EG311) wrote:
>
>>
>> http://git-scm.com/book/en/Distributed-Git-Distributed-Workflows#Integration-Manager-Workflow
>
>
> Who volunteers to be integration manager? If it's not the most
> prolific deve
On Dec 12, 2012, at 9:28 AM, John Peterson
wrote:
> The development branch can be periodically merged into stable, perhaps
> automatically by buildbot whenever tests pass.
>
> So core developers would primarily work with the development branch,
> and users who lie somewhere between "core develo
On Wed, 12 Dec 2012, Kirk, Benjamin (JSC-EG311) wrote:
> (1) treating 'master' as the place for stable code, along the lines of Roy's
> suggestion,
> (2) creating 'devel' where the core developers live.
My concern here is that then the core developers don't get the main
benefit of the "devel"->
I am not against this model... (it is VERY close to how we do things with
MOOSE... and our "stable merge" is automated by Bitten) however, can we
have a small "cooling off" period for a moment while everyone gets up to
date with using the new build system and pulling from Git? MOOSE still
doesn't
On Wed, 12 Dec 2012, Derek Gaston wrote:
> I am not against this model... (it is VERY close to how we do things
> with MOOSE... and our "stable merge" is automated by Bitten)
> however, can we have a small "cooling off" period for a moment while
> everyone gets up to date with using the new buil
On Dec 12, 2012, at 11:17 AM, Roy Stogner wrote:
> On Wed, 12 Dec 2012, Derek Gaston wrote:
>
>> I am not against this model... (it is VERY close to how we do things
>> with MOOSE... and our "stable merge" is automated by Bitten)
>> however, can we have a small "cooling off" period for a moment
On Wed, Dec 12, 2012 at 10:17 AM, Roy Stogner wrote:
> The PECOS CI server actually is publicly accessible. It's so hammered
> right now that I'd rather not subject its interface to even more usage
> until we get some new hardware going, but email me privately if you
> want the URL to peek at occ
On Wed, Dec 12, 2012 at 9:32 AM, Kirk, Benjamin (JSC-EG311)
wrote:
> On Dec 12, 2012, at 9:28 AM, John Peterson
> wrote:
>
>> The development branch can be periodically merged into stable, perhaps
>> automatically by buildbot whenever tests pass.
>>
>> So core developers would primarily work wit
On Wed, 12 Dec 2012, Derek Gaston wrote:
Sounds good. Is there any way we could run a build bot "slave" (I
don't know the BuildBot parlance) here at INL that would report our
test status back to your Build Bot server? If so, we could
definitely set that up.
Nick Malaya set up something simi
On Wed, 12 Dec 2012, Roy Stogner wrote:
> Ben and I (at least) haven't been getting the automatic emails that
> libMesh pull requests are supposed to generate; you might want to ping
> -devel at the same time until we get that sorted out.
Never mind; looks like John figured out the problem.
---
On Dec 12, 2012, at 12:04 PM, Roy Stogner wrote:
>>
>> Also, I have some libMesh changes that I'm going to be making today,
>> so I was thinking about my Git workflow a little bit. I think even
>> _I_ am going to clone the libMesh Git repo on GitHub over into my
>> own workspace and work on my
Sorry I'm late to the party, been in bed with the flu all day.
On Dec 12, 2012, at 11:27 AM, Derek Gaston wrote:
> Also, I have some libMesh changes that I'm going to be making today, so I was
> thinking about my Git workflow a little bit. I think even _I_ am going to
> clone the libMesh Git r
On Wed, Dec 12, 2012 at 11:04 AM, Roy Stogner wrote:
> Nick Malaya set up something similar over here with the TACC systems -
> longhorn.tacc builds and tests our manufactured solution library MASA
> with the Portland Group compilers, and reports the results back to our
> "master" server where it
14 matches
Mail list logo
