Junio C Hamano a8c51f77d1 ci: clear and mark MAKEFLAGS exported just once ... Clearing it once upfront, and turning all the assignment into appending, would future-proof the code even more, to prevent mistakes the previous one fixed from happening again. Also, mark the variable exported just once at the beginning. There is no point in marking it exported repeatedly. Signed-off-by: Junio C Hamano <gitster@pobox.com>		2019-02-07 11:36:28 -08:00
..
util	travis-ci: include the trash directories of failed tests in the trace log	2018-08-01 09:59:36 -07:00
install-dependencies.sh	Merge branch 'sg/travis-osx-brew-breakage-workaround'	2019-02-06 22:05:28 -08:00
lib.sh	ci: clear and mark MAKEFLAGS exported just once	2019-02-07 11:36:28 -08:00
make-test-artifacts.sh	ci: parallelize testing on Windows	2019-01-29 09:26:47 -08:00
mount-fileshare.sh	Add a build definition for Azure DevOps	2019-01-29 09:26:46 -08:00
print-test-failures.sh	ci/lib.sh: add support for Azure Pipelines	2019-01-29 09:26:46 -08:00
run-build-and-tests.sh	Merge branch 'js/vsts-ci'	2019-02-06 22:05:26 -08:00
run-linux32-build.sh	Merge branch 'js/vsts-ci'	2019-02-06 22:05:26 -08:00
run-linux32-docker.sh	ci: rename the library of common functions	2019-01-28 10:34:28 -08:00
run-static-analysis.sh	ci: inherit --jobs via MAKEFLAGS in run-build-and-tests	2019-01-28 10:34:28 -08:00
run-test-slice.sh	ci: parallelize testing on Windows	2019-01-29 09:26:47 -08:00
run-windows-build.sh	ci: rename the library of common functions	2019-01-28 10:34:28 -08:00
test-documentation.sh	ci: inherit --jobs via MAKEFLAGS in run-build-and-tests	2019-01-28 10:34:28 -08:00