diff options
| author | Chris Evich <cevich@redhat.com> | 2022-03-18 15:30:48 -0400 |
|---|---|---|
| committer | Chris Evich <cevich@redhat.com> | 2022-03-22 11:01:45 -0400 |
| commit | 1a7f5b3d51d60c71068cfbcf03a3f82ce4ed5e1f (patch) | |
| tree | 99c3dafe0d577811ea6337bcfbefb98c77c55fe2 /transfer.md | |
| parent | e034db16bf68c06c1ecf63addd033fcbd83090e3 (diff) | |
| download | podman-1a7f5b3d51d60c71068cfbcf03a3f82ce4ed5e1f.tar.gz podman-1a7f5b3d51d60c71068cfbcf03a3f82ce4ed5e1f.tar.bz2 podman-1a7f5b3d51d60c71068cfbcf03a3f82ce4ed5e1f.zip | |
Cirrus: Publish binary artifacts on success
In general continuous-delivery (CD) tends to pair well with CI. More
specifically, there is a need for some reverse-dependency CI testing in
netavark/aardvark-dns. In all cases, the download URL needs to remain
consistent, without elements like `Build%20for%20fedora-35`.
The 'Total Success' task only ever executes when all dependencies are
successful. When a non `[CI:DOCS]` build is successful, gather all
binary/release artifacts in a new task which depends on 'Total Success'.
This will provide a uniform name (`artifacts`) and URL for downstream
users to use. For example:
https://api.cirrus-ci.com/v1/artifact/github/containers/podman/artifacts/binary.zip
or
https://api.cirrus-ci.com/v1/artifact/github/containers/podman/artifacts/binary/FILENAME
Where ***FILENAME*** is one of:
* `podman`
* `podman-remote`
* `rootlessport`
* `podman-release-386.tar.gz`
* `podman-release-amd64.tar.gz`
* `podman-release-arm64.tar.gz`
* `podman-release-arm.tar.gz`
* `podman-release-mips64le.tar.gz`
* `podman-release-mips64.tar.gz`
* `podman-release-mipsle.tar.gz`
* `podman-release-mips.tar.gz`
* `podman-release-ppc64le.tar.gz`
* `podman-release-s390x.tar.gz`
* `podman-remote-release-darwin_amd64.zip`
* `podman-remote-release-darwin_arm64.zip`
* `podman-remote-release-windows_amd64.zip`
* `podman-v4.0.0-dev.msi`
Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'transfer.md')
0 files changed, 0 insertions, 0 deletions