Re: Ability to remember last known good build

2016-03-11 Thread Junio C Hamano
Stefan Beller writes: >>> Any better way of accomplishing this? >> >> "test && git branch -f last-good"? > > Travis-CI enabled, tells me they're using Github and are distributed, > so one contributor would want to know the last known good state of > a remote, that others push to, without testing

RE: Ability to remember last known good build

2016-03-11 Thread Randall S. Becker
On March 11, 2016 1:08 PM Junio C Hamano wrote: > "Pedroso, Osiris" writes: > > > I participate in an open source project that any pull merge is accepted, no > matter what. > > > > This makes for lots of broken builds, even though we do have Travis-CI > enabled on the project, because people will

Re: Ability to remember last known good build

2016-03-11 Thread Stefan Beller
On Fri, Mar 11, 2016 at 10:08 AM, Junio C Hamano wrote: > "Pedroso, Osiris" writes: > >> I participate in an open source project that any pull merge is accepted, no >> matter what. >> >> This makes for lots of broken builds, even though we do have Travis-CI >> enabled on the project, because pe

Re: Ability to remember last known good build

2016-03-11 Thread Junio C Hamano
"Pedroso, Osiris" writes: > I participate in an open source project that any pull merge is accepted, no > matter what. > > This makes for lots of broken builds, even though we do have Travis-CI > enabled on the project, because people will merge a request before even the > build is complete. >

Ability to remember last known good build

2016-03-11 Thread Pedroso, Osiris
I participate in an open source project that any pull merge is accepted, no matter what. This makes for lots of broken builds, even though we do have Travis-CI enabled on the project, because people will merge a request before even the build is complete. Therefore, I would like to remember the