Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> writes: > * The rather minor in code but rather big in UX terms is that I've > added 29/29, which explicitly documents and shows examples of using > the CI tooling in a way where you can locally run a CI target as if > though it were a given $jobname, e.g.: Yay. > Likewise the ci/print-test-failures.sh script can now be run > locally without any extra mock-ups, e.g.: Double yay. > @@ ci/lib.sh > +# Starting assertions > +if test -z "$jobname" > +then > -+ echo "must set a CI jobname" >&2 > ++ echo "must set a CI jobname in the environment" >&2 > + exit 1 > +fi OK. In the truely-automated-machine-initiated run, this should not matter, but once we start allowing end-user to interact with the guts of the CI machinery, being as helpful as possible matters.
