From: "SZEDER Gábor" <szeder.dev@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Lars Schneider" <larsxschneider@gmail.com>,
"SZEDER Gábor" <szeder.dev@gmail.com>
Subject: [PATCH 0/2] Travis CI: check unignored build artifacts
Date: Sun, 31 Dec 2017 17:02:04 +0100 [thread overview]
Message-ID: <20171231160206.19481-1-szeder.dev@gmail.com> (raw)
Every once in a while our explicit .gitignore files get out of sync when
our build process learns to create new artifacts, but the .gitignore
files are not updated accordingly. It was recently that we got a report
about unignored test helper executables, see 44103f419 (t/helper: ignore
everything but sources, 2017-12-12).
This short patch series teaches our Travis CI build scripts to detect
unignored build artifacts at the end of builds, in the hope to catch
these issues earlier.
These patches should go on top 'sg/travis-skip-identical-test'. The two
patch series are conceptually independent, but would have a couple of
conflicts when applied separately and then merged together, and I don't
think it's worth carrying them in separate branches.
SZEDER Gábor (2):
travis-ci: don't store P4 and Git LFS in the working tree
travis-ci: check that all build artifacts are .gitignore-d
ci/lib-travisci.sh | 14 ++++++++++++--
ci/run-linux32-docker.sh | 2 ++
ci/run-tests.sh | 2 ++
ci/test-documentation.sh | 6 ++++++
4 files changed, 22 insertions(+), 2 deletions(-)
--
2.16.0.rc0.67.g3a46dbca7
next reply other threads:[~2017-12-31 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 16:02 SZEDER Gábor [this message]
2017-12-31 16:02 ` [PATCH 1/2] travis-ci: don't store P4 and Git LFS in the working tree SZEDER Gábor
2018-01-02 19:38 ` Lars Schneider
2017-12-31 16:02 ` [PATCH 2/2] travis-ci: check that all build artifacts are .gitignore-d SZEDER Gábor
2018-01-02 19:40 ` Lars Schneider
2018-01-02 23:12 ` SZEDER Gábor
2018-01-03 9:45 ` Lars Schneider
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171231160206.19481-1-szeder.dev@gmail.com \
--to=szeder.dev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsxschneider@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).