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

[PATCH 0/2] Travis CI: check unignored build artifacts

From
SZEDER Gábor <szeder.dev@gmail.com>
Date
Dec 31, 2017, 16:02 UTC
Message-ID
<20171231160206.19481-1-szeder.dev@gmail.com>

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: SZEDER Gábor
Message 1 of 7 in “Travis CI: check unignored build artifacts”
  1. 0/2 Travis CI: check unignored build artifactsSZEDER Gábor, Dec 31, 2017
  2. 1/2 travis-ci: don't store P4 and Git LFS in the working treeSZEDER Gábor, Dec 31, 2017
  3. Lars SchneiderJan 2, 2018
  4. 2/2 travis-ci: check that all build artifacts are .gitignore-dSZEDER Gábor, Dec 31, 2017
  5. Lars SchneiderJan 2, 2018
  6. SZEDER GáborJan 2, 2018
  7. Lars SchneiderJan 3, 2018

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.