In 2015 we introduced usage of EXECUTOR_NUMBER to namespace the temporary directory between builds (Gerrit 198197. As the workload got moved to container, that is no more needed.
We still have some occurrences in code search:
integration/config
# XXX note wikimedia/fundraising/tools test suite expects the Jenkins env # variable EXECUTOR_NUMBER to be set. docker run \ --rm --tty \ --env EXECUTOR_NUMBER=1 \
# Job to run MediaWiki update.php script on all the beta wikis. # # Set TMPDIR to point to the tmpfs if it exists. - job: name: beta-update-databases-eqiad defaults: beta node: BetaClusterBastion builders: - shell: | # Setup tmpfs directory export TMPDIR_FS="/srv/home/jenkins-deploy/tmpfs/jenkins-${EXECUTOR_NUMBER}" if [ -d "/srv/home/jenkins-deploy/tmpfs" ]; then mkdir -p "$TMPDIR_FS" chmod 777 "$TMPDIR_FS" export TMPDIR="$TMPDIR_FS" fi # Teardown tmpfs directory function global_teardown() { rm -rf "$TMPDIR_FS" } trap global_teardown EXIT /usr/local/bin/wmf-beta-update-databases.py
integration/quibble
""" Set and get needed environment variables. TODO: Can we deprecate any of these in favor of explicit parameters? """ if 'EXECUTOR_NUMBER' not in os.environ: os.environ['EXECUTOR_NUMBER'] = '1'
That one in Quibble came from the early days of Quibble and probably came from the 2015 script.