Publish to snapcraft.io automatically using Github workflows. The master branch will publish to latest/edge and as we create new branches for releases, we should have those publish to <vault version>/edge.
As of Vault 1.15, Github runners will be used for building and publishing the Vault snap. Launchpad will continue to be used for older version of this snap.
Rationale
Failing Builds
Builds are failing on Launchpad, but passing using Github runners or locally. In order to get around this issue, we'd have to complexify the snapcraft.yaml content to satisfy Launchpad.
Complexity
Having Launchpad as a separate build system complexifies the development process, we have 2 systems instead of 1 for CI.
Architecture supports
The only advantage of using Launchpad is building for more architectures. Currently, less than 1% of the install base is using a non amd64 architecture and most of those are on ARM. As IS adds arm Github runners, we will also build this snap for ARM using Github runners.
Description
Publish to snapcraft.io automatically using Github workflows. The
masterbranch will publish tolatest/edgeand as we create new branches for releases, we should have those publish to<vault version>/edge.As of Vault
1.15, Github runners will be used for building and publishing the Vault snap. Launchpad will continue to be used for older version of this snap.Rationale
Failing Builds
Builds are failing on Launchpad, but passing using Github runners or locally. In order to get around this issue, we'd have to complexify the snapcraft.yaml content to satisfy Launchpad.
Complexity
Having Launchpad as a separate build system complexifies the development process, we have 2 systems instead of 1 for CI.
Architecture supports
The only advantage of using Launchpad is building for more architectures. Currently, less than 1% of the install base is using a non amd64 architecture and most of those are on ARM. As IS adds arm Github runners, we will also build this snap for ARM using Github runners.