diff options
| author | Chris Evich <cevich@redhat.com> | 2019-10-30 10:35:20 -0400 |
|---|---|---|
| committer | Chris Evich <cevich@redhat.com> | 2019-10-30 14:31:38 -0400 |
| commit | 326ef19d942c8922ebba68e96d870d5117f67472 (patch) | |
| tree | d95167354848a6366ee1553e3a5630a8e127cbd4 /.tool | |
| parent | 63b57f5147462bef19df842f9c92868f7bdaea8a (diff) | |
| download | podman-326ef19d942c8922ebba68e96d870d5117f67472.tar.gz podman-326ef19d942c8922ebba68e96d870d5117f67472.tar.bz2 podman-326ef19d942c8922ebba68e96d870d5117f67472.zip | |
Cirrus: Fix upload_release_archive on branch or tag
Cirrus-CI only sets `$CIRRUS_BASE_SHA` when testing PRs since the
destination and it's state is easy to discover. However, when
post-merge and/or tag-push testing, the previous state is not
easily discoverable (changes have already merged). The
`upload_release_archive` script incorrectly assumed this
variable was always set, causing a constant stream of post-merge
testing failures.
Tweak the `is_release()` function to properly handle an empty
`$CIRRUS_BASE_SHA` whether or not `$CIRRUS_TAG` is also set. Also
update the unit-tests to check for this. Also account for a
corner case where hack/get_ci_vm.sh is running on a VM w/o git.
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to '.tool')
0 files changed, 0 insertions, 0 deletions