林博仁(Buo-ren Lin) 8aaa4edbcd Implement selective pulling for building tagged release snaps (#187) ... This patch re-implements the pull step that will only build development snapshots snaps if the latest tagged release has been promoted to the stable channel. This ensures that there's always a revision of the stable release snap available in the edge channel for the publisher to promote to stable as currently the build infrastructure only supports build on code push (but not new tagged releases) at this time. The implementation is inspired from the snapcrafters adopted snaps workflow, documented in the following forum topic: The automatic build and pubish process of snaps owned by the Snapcrafters - doc - snapcraft.io https://forum.snapcraft.io/t/autopublishing-of-snapcrafters-organizations-snaps-how/7954/2 Refer the following forum topic for a possible solution proposal of this problem: Proposal: Allow overriding the source-tag property for an one-time build in the build infrastructure - snapcraft - snapcraft.io https://forum.snapcraft.io/t/proposal-allow-overriding-the-source-tag-property-for-an-one-time-build-in-the-build-infrastructure/10303 Signed-off-by: 林博仁(Buo-ren Lin) <Buo.Ren.Lin@gmail.com>		2019-03-13 21:58:46 +01:00
..
local/launchers	snap: Use SNAPCRAFT_ARCH_TRIPLET for pulseaudio library workaround (#188)	2019-03-13 21:52:35 +01:00
snapcraft.yaml	Implement selective pulling for building tagged release snaps (#187)	2019-03-13 21:58:46 +01:00