Re: Ability to remember last known good build

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 11, 2016, 22:08 UTC
Message-ID: <xmqqio0sacrd.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <CAGZ79kZS7vnw5EskQHty9Cathv6FdE3L8wLstFwaWpMFHamSEw@mail.gmail.com>

Stefan Beller <sbeller@google.com> writes:

Show 10 quoted lines

>>> 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 all commits locally.
>
> So maybe the question is better rephrased as: "How do we keep track of
> the last good state using the distributed nature of Git?"

I think Travis integration with GitHub lets the commits tested to be annotated in the test status, so scanning the history from the tip to find the latest one with the "good" test result would be how you would find "the last passing one" if your workflow relies on the Travis-GitHub combination.

I am not sure about "using the distributed nature" part. That depends on the way how the result of the Travis testing is reflected on the GitHub side. If it is done by adding a note or something that can natively exported over "git fetch", that would be one way to do so.