Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename the snap as barrier. #412

Merged
merged 1 commit into from
Aug 22, 2019
Merged

Conversation

maxiberta
Copy link

Rename the snap, now that the barrier snap name is owned by @AdrianKoshka at the snap store.

Then, a simple CI pipeline can be setup at https://snapcraft.io/build to build and release the snap on each commit to master :).

@AdrianKoshka AdrianKoshka merged commit 58f6c73 into debauchee:master Aug 22, 2019
@AdrianKoshka
Copy link

@maxiberta er, on each commit to master? Wouldn't we only want to release on tags?

@maxiberta
Copy link
Author

@AdrianKoshka yes, it'll just push to the edge channel on each commit to master. The idea is that edge is for testing, and when you're happy with a particular build, you promote it to candidate and/or stable for general availability. Or, you can use Launchpad.net directly for more complex setups (launchpad is the snap store builder backend).

@AdrianKoshka
Copy link

AdrianKoshka commented Aug 22, 2019 via email

@AdrianKoshka
Copy link

Aaaand, done! https://build.snapcraft.io/user/debauchee/barrier

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants