For now, leave these jobs out during merge requests.

This makes room for future equivalents for other architectures.
The packaging jobs produce universal binaries, so leave them as-is.

The package pipeline for release versions should not upload packages
automatically to our archive of nightly development versions.

Test building our release for the `aarch64` architecture.
For now, leave this job out during merge requests.

This makes room for a future equivalent for other architectures.

Use `linux_release` in names associated with building or testing
release-style binaries.  Add a `.linux_package` helper to adjust
the release binary build behavior for package-specific jobs.

In order to support modern macOS features like Dark Mode, we need to use
Qt 5.15, which requires macOS 10.13.  However, we still want to support
macOS 10.10 as well, for which we need to use Qt 5.9.  Build separate
macOS packages for these use cases.

Fixes: #21606
Issue: #20825

The package pipeline for release versions should not upload packages
automatically to our archive of nightly development versions.

Ben Boeckel authored 4 years ago and Brad King committed 4 years ago

These reuse the doc artifacts as the macOS package does.

Move the macOS package build job into the `build` stage.  Since it
depends on the sphinx doc package job, add a preceding `prep` stage.

This can be added to any other platform's package by reusing the
artifact.

They're not actually the same anyways and the anchors can't be shared
between the files. We can figure out refactoring in the future.

YAML anchors are not supported across include files.

Also add comments for sections to make it easier to figure out what's
going on.

Also rename the `cmake_test_unix_package` to be Linux-specific since it
actually is.

macOS install trees have a different layout and package names.