aboutsummaryrefslogtreecommitdiff
path: root/transfer.md
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2021-01-21 14:56:34 -0500
committerChris Evich <cevich@redhat.com>2021-02-01 10:07:15 -0500
commit545eeca8ea3d8736ec8646a6cd27d94b9a61e2c7 (patch)
tree9795329ac9fbdd32b54e22babaa3484ebd934fee /transfer.md
parent745fa4ac94c3ec99becd85f59d1b59c2c9765527 (diff)
downloadpodman-545eeca8ea3d8736ec8646a6cd27d94b9a61e2c7.tar.gz
podman-545eeca8ea3d8736ec8646a6cd27d94b9a61e2c7.tar.bz2
podman-545eeca8ea3d8736ec8646a6cd27d94b9a61e2c7.zip
Cirrus: Fix running Validate task on branches
Followup to 4c60523 Despite skipping the `Smoke` check, it was observed on a *new* branch, the `validate` task (specifically `git-validation`) will fail. This is because: * `$CIRRUS_LAST_GREEN_CHANGE` will be empty on a new branch. * `$CIRRUS_BASE_SHA` is always empty for runs triggered by branch-push * `$EPOCH_TEST_COMMIT` will be set to `YOU_FOUND_A_BUG`. Fix this by eliminating the `Smoke` task entirely, simplifying all the `make validate` operations into the `validate` cirrus task. Ensure this task does not run when a new branch or tag is pushed. Also, eliminate the `$CIRRUS_BUILD_ID` value as it's confusing and not actually used anywhere. It was formerly used for building VM images, but this has moved to another repo entirely. Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'transfer.md')
0 files changed, 0 insertions, 0 deletions