Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

> On 29 Dec 2017, at 21:16, SZEDER Gábor wrote: > > On Fri, Dec 29, 2017 at 9:03 PM, SZEDER Gábor wrote: > > Or print it in a different color? Maybe red? > > See: https://travis-ci.org/szeder/git/jobs/322247836#L622-L625 I

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

On Fri, Dec 29, 2017 at 9:03 PM, SZEDER Gábor wrote: Or print it in a different color? Maybe red? See: https://travis-ci.org/szeder/git/jobs/322247836#L622-L625 >>> >>> I considered using color for the first line, but then didn't do it, >>> because I didn't

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

On Thu, Dec 28, 2017 at 12:16 PM, Lars Schneider wrote: > >> On 28 Dec 2017, at 00:00, SZEDER Gábor wrote: >> >> On Wed, Dec 27, 2017 at 8:15 PM, Lars Schneider >> wrote: >>> On 27 Dec 2017, at 17:49, SZEDER Gábor

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

SZEDER Gábor writes: > I was aware that things like 'cmd file >file' don't work, because the > shell opens and truncates 'file' before executing the command, so 'cmd' > will open the already empty file, but I didn't know that 'echo "$(cmd > file)" >file' works. Thanks for

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

> On 28 Dec 2017, at 00:00, SZEDER Gábor wrote: > > On Wed, Dec 27, 2017 at 8:15 PM, Lars Schneider > wrote: >> >>> On 27 Dec 2017, at 17:49, SZEDER Gábor wrote: >>> +# Skip the build job if the same tree has already been

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

> On 28 Dec 2017, at 11:31, SZEDER Gábor wrote: > > On Wed, Dec 27, 2017 at 8:35 PM, Lars Schneider > wrote: >> >>> On 27 Dec 2017, at 17:49, SZEDER Gábor wrote: > >>> Using an ever-growing flat text file might seem like

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

On Wed, Dec 27, 2017 at 8:35 PM, Lars Schneider wrote: > >> On 27 Dec 2017, at 17:49, SZEDER Gábor wrote: >> Using an ever-growing flat text file might seem like asking for >> trouble on the long run, but it's perfectly adequate for this purpose.

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

On Thu, Dec 28, 2017 at 12:00 AM, SZEDER Gábor wrote: > On Wed, Dec 27, 2017 at 8:15 PM, Lars Schneider > wrote: >>> + then >>> + cat <<-EOF >>> + Skipping build job for commit $TRAVIS_COMMIT.

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

On Wed, Dec 27, 2017 at 8:15 PM, Lars Schneider wrote: > >> On 27 Dec 2017, at 17:49, SZEDER Gábor wrote: >> +# Skip the build job if the same tree has already been built and tested >> +# successfully before (e.g. because the branch got rebased,

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

> On 27 Dec 2017, at 17:49, SZEDER Gábor wrote: > > Travis CI dutifully builds and tests each new branch tip, even if its > tree has previously been successfully built and tested. This happens > often enough in contributors' workflows, when a work-in-progress > branch is

Re: [PATCH 2/2] travis-ci: record and skip successfully built trees

> On 27 Dec 2017, at 17:49, SZEDER Gábor wrote: > > Travis CI dutifully builds and tests each new branch tip, even if its > tree has previously been successfully built and tested. This happens > often enough in contributors' workflows, when a work-in-progress > branch is

[PATCH 2/2] travis-ci: record and skip successfully built trees

Travis CI dutifully builds and tests each new branch tip, even if its tree has previously been successfully built and tested. This happens often enough in contributors' workflows, when a work-in-progress branch is rebased changing e.g. only commit messages or the order or number of commits while