Merge pull request #17536 from cevich/fix_version_check_cron

[CI:DOCS] Cirrus: Fix version-check to only run on `main` job
This commit is contained in:
OpenShift Merge Robot 2023-02-20 14:45:29 +01:00 committed by GitHub
commit a9ec6492e8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 14 additions and 12 deletions

View file

@ -17,7 +17,7 @@ The remote client uses a client-server model. You need Podman installed on a Lin
### Windows
Installing the Windows Podman client begins by downloading the Podman Windows installer. The Windows installer is built with each Podman release and is downloadable from its [release description page](https://github.com/containers/podman/releases/latest). The Windows installer file is named `podman-#.#.#-setup.exe`, where the `#` symbols represent the version number of Podman.
As of 2023-01-16 the latest version is [v4.3.1](https://github.com/containers/podman/releases/download/v4.3.1/podman-4.3.1-setup.exe).
As of 2023-02-16 the latest version is [v4.4.1](https://github.com/containers/podman/releases/download/v4.4.1/podman-4.4.1-setup.exe).
Once you have downloaded the installer to your Windows host, simply double click the installer and Podman will be installed. The path is also set to put `podman` in the default user path.

View file

@ -44,7 +44,7 @@ downloaded from the official
Windows installer file is named podman-#.#.#-setup.exe, where the # symbols
represent the version number of Podman. Be sure to download a 4.1 or later
release for the capabilities discussed in this guide.
As of 2023-01-16 the latest version is [v4.3.1](https://github.com/containers/podman/releases/download/v4.3.1/podman-4.3.1-setup.exe).
As of 2023-02-16 the latest version is [v4.4.1](https://github.com/containers/podman/releases/download/v4.4.1/podman-4.4.1-setup.exe).
![Installing Podman 4.1.0](podman-win-install.jpg)

View file

@ -21,17 +21,19 @@ function warn() {
echo "$ME: $*" >&2
}
# Setup check: exit gracefully unless we're in the desired environment
if [[ -n "$CIRRUS_PR" ]]; then
warn "we don't run on PRs"
exit 0
fi
if [[ -n "$CIRRUS_CI" ]]; then
# Setup check: exit gracefully unless we're in the desired environment
if [[ -n "$CIRRUS_PR" ]]; then
warn "we don't run on PRs"
exit 0
fi
if [[ "$CIRRUS_CRON" != "main" ]]; then
warn "Only meaningful in CI when CIRRUS_CRON=main (it is '$CIRRUS_CRON')"
exit 0
fi
if [[ -n "$CIRRUS_CRON" ]]; then
if [[ "$CIRRUS_CRON" != "nightly" ]]; then
warn "Only meaningful when CIRRUS_CRON=nightly (it is '$CIRRUS_CRON')"
exit 0
fi
fi
# No sense running on release branches