I use build.snapcraft.io to build snaps for one of my GitHub repos. In that repo, I have a devel branch and a master branch (loosely following Gitflow). The devel branch is the default, as that’s where changes should land, which means (I believe) that it’s also the place that build.snapcraft.io builds from, in to edge.
This is fine in the general case, as most of my changes do flow linearly from devel to master, but I just received (an extremely cool!) email informing me that my snap contains an old OpenSSL. I want to rebuild the snap using the contents of master, so I only pull in the updated OpenSSL and not the changes that have landed in devel but not yet in a release.
As far as I can tell, there isn’t a way to do this in build.snapcraft.io so I would have to switch the default branch in Github, manually kick off a build and then switch it back. Is there a better way of doing this that I’m missing? Are there any plans to support switching the built branch in build.snapcraft.io?
(My preferred workflow, which is a bit more complex than the above, would be to build from devel in to edge and from master in to beta or candidate, so that I can promote exactly what is in master, rather than what was in devel that I merged in to master.)