mirror of
https://github.com/subsurface/subsurface.git
synced 2025-01-21 07:15:27 +00:00
21095b18fc
While for the other platforms we can simply copy our binaries (maybe after signing them), for Fedora and Ubuntu we have to trigger fresh builds. The most logical way that I could think of to do this was to push the same commit corresponding with the intended current release into a branch named 'current' and have that trigger Copr and Launchpad builds that post into our release repos. So 'master' keeps moving forward, keeps creating new build numbers. At some point we pick a build number that we want to be the next 'current' release. We then update the current branch to the commit that corresponds to that build number and push the current branch which triggers new builds in the correct repos on Copr and Launchpad. This commit removes the silly 'push' argument from the make-package scripts (after all, they are used to push those packages to the respective build services) and instead use the branch name as argument to those scripts - allowing us to pick which repo to push into. Signed-off-by: Dirk Hohndel <dirk@hohndel.org> |
||
|---|---|---|
| .. | ||
| scripts | ||
| android-dockerimage.yml | ||
| android.yml | ||
| codeql-analysis.yml | ||
| coverity-scan.yml | ||
| fedora-copr-build.yml | ||
| ios.yml | ||
| linux-bionic-5.9.yml.disabled | ||
| linux-dockerimage.disabled | ||
| linux-fedora-qt6.yml | ||
| linux-focal-5.12.yml | ||
| linux-jammy-5.15.yml | ||
| linux-snap.patch | ||
| linux-snap.yml | ||
| linux-trusty-5.12.yml | ||
| mac.yml | ||
| post-releasenotes.yml | ||
| snap_usns.yml | ||
| ubuntu-launchpad-build.yml | ||
| windows-mxe-dockerimage.yml | ||
| windows.yml | ||