git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Ability to remember last known good build

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 11, 2016, 18:08 UTC
Message-ID
<xmqq60wsc2gh.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<CEDF59214E9E6A4CB418120F4FD7A0056E86A214@US-MBX2.ingrnet.com>
"Pedroso, Osiris" <osiris.pedroso@intergraph.com> writes:
Show 11 quoted lines
> 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 id of the commit of the last successful build. This would be updated by the Travis-CI script itself upon a successful build.
>
> 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".
>
> I am new to git, but some other experienced co-volunteers tell me that it may not be possible due to authentication issues.
>
> Any better way of accomplishing this?
"test && git branch -f last-good"?
Previous: Pedroso, OsirisNext: Stefan Beller
Message 2 of 5 in “Ability to remember last known good build”
  1. Pedroso, OsirisMar 11, 2016
  2. Junio C HamanoMar 11, 2016
  3. Stefan BellerMar 11, 2016
  4. Junio C HamanoMar 11, 2016
  5. Randall S. BeckerMar 11, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.