@@ -79,6 +79,8 @@ jobs:
windows-build:
name: win build
+ env:
+ jobname: windows-build
needs: ci-config
if: needs.ci-config.outputs.enabled == 'yes'
runs-on: windows-latest
@@ -100,6 +102,8 @@ jobs:
path: artifacts
windows-test:
name: win test
+ env:
+ jobname: windows-test
runs-on: windows-latest
needs: [windows-build]
strategy:
@@ -134,6 +138,7 @@ jobs:
needs: ci-config
if: needs.ci-config.outputs.enabled == 'yes'
env:
+ jobname: vs-build
NO_PERL: 1
GIT_CONFIG_PARAMETERS: "'user.name=CI' 'user.email=ci@git'"
runs-on: windows-latest
@@ -183,6 +188,8 @@ jobs:
path: artifacts
vs-test:
name: win+VS test
+ env:
+ jobname: vs-test
runs-on: windows-latest
needs: vs-build
strategy:
@@ -8,6 +8,13 @@
# are installed.
set -e
+# Starting assertions
+if test -z "$jobname"
+then
+ echo "error: must set a CI jobname in the environment" >&2
+ exit 1
+fi
+
if test true != "$GITHUB_ACTIONS"
then
begin_group () { :; }
@@ -119,11 +126,6 @@ else
exit 1
fi
-if test -z "$jobname"
-then
- jobname="$CI_OS_NAME-$CC"
-fi
-
export DEVELOPER=1
export DEFAULT_TEST_TARGET=prove
export GIT_TEST_CLONE_2GB=true
Remove the $jobname fallback last adjusted in b011fabd6e0 (ci/lib.sh: encapsulate Travis-specific things, 2019-01-27). This makes all of our CI jobs have an explicit $jobname, and removes the special-case of the Windows jobs implicitly setting one (that they don't currently use). This is a follow-up to my 25715419bf4 (CI: don't run "make test" twice in one job, 2021-11-23), since then all the jobs except the Windows jobs have had an explicit $jobname. In the case of the Windows jobs we were using a jobname of windows-gcc for both, due to picking "gcc" as a default fallback for "$CC" in ci/lib.sh. Since we'll need this to run ci/lib.sh it makes sense to move the check to the top of the file. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> --- .github/workflows/main.yml | 7 +++++++ ci/lib.sh | 12 +++++++----- 2 files changed, 14 insertions(+), 5 deletions(-)