RE: Ability to remember last known good build

On March 11, 2016 1:08 PM Junio C Hamano wrote:

"Pedroso, Osiris" [off-list ref] writes:

quoted

I participate in an open source project that any pull merge is accepted,

no

matter what.

quoted

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.

quoted

Therefore, I would like to remember the id of the commit of the last

successful build. This would be updated by the Travis-CI script itself

upon a

successful build.

quoted

I imagine best option would be to merge master to a certain branch named

"Last_known_Linux_build" or "Last_known_Windows_build" or even
"Last_known_build_all_tests_passing".

quoted

I am new to git, but some other experienced co-volunteers tell me that

it

may not be possible due to authentication issues.

quoted

Any better way of accomplishing this?

"test && git branch -f last-good"?

I think semantically a last-good tag might be another option, unless you are
applying build fixes to a last-good topic branch. You also have the option
of adding content to the tag describing the build reason, engine used, etc.
See git tag --help. I have used that in a Jenkins environment putting the
tag move in the step following a build (failure does not execute the step so
the last-good build tag stays where it is).

Cheers,
Randall

-- Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)/NonStop(211288444200000000)
-- In my real life, I talk too much.