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
Enable github workflow for snaps. #295
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay.
Thank you for doing this! I've added the secrets.
Just one comment about whether we want to run the snap script on every push to every branch or only master or only when a release tag is created?
@@ -0,0 +1,68 @@ | |||
name: snap | |||
|
|||
on: [push] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we only push to snap from the master branch? Could do something like this?
on: [push] | |
on: | |
push: | |
branches: | |
- master |
Or we could deploy only when a release tag is pushed? (the same way continous deployment is currently configured)
on: [push] | |
on: | |
push: | |
tags: | |
- "v*.*.*" | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delay.
Thank you for doing this! I've added the secrets.
Just one comment about whether we want to run the snap script on every push to every branch or only master or only when a release tag is created?
Good question. I would run on every commit that leads to a release. That way we are warned when changes break snap builds. The workflow only pushes on tags. So if master is the only branch that ever gets released, I would run the workflow on every push to master.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got you 👍
Thanks again
After merging it fails with the above error. Any ideas on how to fix? |
This could be because the secret were copied and pasted incorrectly or were
not named appropriately.
…On Wed, Feb 19, 2020 at 10:40 AM Alexander Keliris ***@***.***> wrote:
User should be logged in
##[error]Process completed with exit code 1.
Run snapcraft whoami
snapcraft whoami
shell: /bin/bash -e {0}
/ not root-owned 501:50
##[error]Process completed with exit code 1.
After merging it fails with the above error. Any ideas on how to fix?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#295?email_source=notifications&email_token=ABMJBTNQ4CO6Y5BYQZ65ND3RDVVJNA5CNFSM4KUU45P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMIX2EI#issuecomment-588348689>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMJBTP7424RWYB6VCJE46TRDVVJNANCNFSM4KUU45PQ>
.
--
Regards,
Carlos Hernandez
|
The snapcraft secret should be snapcraft_login, as per the line below.
echo "${{ secrets.snapcraft_login }}" > "$snapcraft_creds"
…On Wed, Feb 19, 2020 at 10:40 AM Alexander Keliris ***@***.***> wrote:
User should be logged in
##[error]Process completed with exit code 1.
Run snapcraft whoami
snapcraft whoami
shell: /bin/bash -e {0}
/ not root-owned 501:50
##[error]Process completed with exit code 1.
After merging it fails with the above error. Any ideas on how to fix?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#295?email_source=notifications&email_token=ABMJBTNQ4CO6Y5BYQZ65ND3RDVVJNA5CNFSM4KUU45P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMIX2EI#issuecomment-588348689>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMJBTP7424RWYB6VCJE46TRDVVJNANCNFSM4KUU45PQ>
.
--
Regards,
Carlos Hernandez
|
@hurricanehrndz I corrected one of the secrets (was previously named However, looks like it is still failing 🤔 https://github.com/Rigellute/spotify-tui/runs/457296832?check_suite_focus=true To confirm, the files you sent me are saved as follows
|
I re-exported the login information, and email it to you. Do you have snapcraft installed? If you do you should be to test the command from any directory with the login info emailed to you. Just run the following:
|
Have debugged and fixed the snap workflow. Turns out there were a few other problems not related to login info. See the commits here if you're interested 268348e |
Alexander,
Awesome work. The original pull request also works. I am certain it is a
small piece of information I probably overlooked. I was hoping to get arm64
builds enabled. Please see here for proof:
https://github.com/hurricanehrndz/spotify-tui/runs/457707733?check_suite_focus=true
…On Thu., Feb. 20, 2020, 7:50 a.m. Alexander Keliris, < ***@***.***> wrote:
Have debugged and fixed the snap workflow. Turns out there were a few
other problems not related to login info.
See the commits here if you're interested 268348e
<268348e>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#295?email_source=notifications&email_token=ABMJBTKKJRDVED7JWTPSZ7LRD2KB7A5CNFSM4KUU45P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMOMNAI#issuecomment-589088385>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMJBTNHBUNHOMV6CSRRFELRD2KB7ANCNFSM4KUU45PQ>
.
|
If you are interested in getting the remote builds working, perhaps you can
grant me maintainer rights long enough to fix and debug. Just a thought.
…On Thu., Feb. 20, 2020, 7:50 a.m. Alexander Keliris, < ***@***.***> wrote:
Have debugged and fixed the snap workflow. Turns out there were a few
other problems not related to login info.
See the commits here if you're interested 268348e
<268348e>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#295?email_source=notifications&email_token=ABMJBTKKJRDVED7JWTPSZ7LRD2KB7A5CNFSM4KUU45P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMOMNAI#issuecomment-589088385>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMJBTNHBUNHOMV6CSRRFELRD2KB7ANCNFSM4KUU45PQ>
.
|
The reason remote build didn't work with the commit before
<https://github.com/Rigellute/spotify-tui/runs/457933133?check_suite_focus=true>
is because snapcraft in docker is version 3.8 and snapcraft version in snap
is 3.9
…On Thu, Feb 20, 2020 at 7:50 AM Alexander Keliris ***@***.***> wrote:
Have debugged and fixed the snap workflow. Turns out there were a few
other problems not related to login info.
See the commits here if you're interested 268348e
<268348e>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#295?email_source=notifications&email_token=ABMJBTKKJRDVED7JWTPSZ7LRD2KB7A5CNFSM4KUU45P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMOMNAI#issuecomment-589088385>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMJBTNHBUNHOMV6CSRRFELRD2KB7ANCNFSM4KUU45PQ>
.
--
Regards,
Carlos Hernandez
|
Hi @hurricanehrndz, I just cut a new release (v0.15.0) and encountered another issue with the snap workflow (see here https://github.com/Rigellute/spotify-tui/runs/465367238?check_suite_focus=true) Error this time is
|
I will promote the build that matches the release hash to beta for now, and
I will look into a solution.
…On Mon., Feb. 24, 2020, 12:18 p.m. Alexander Keliris, < ***@***.***> wrote:
Hi @hurricanehrndz <https://github.com/hurricanehrndz>, I just cut a new
release (v0.15.0) and encountered another issue with the snap workflow (see
here
https://github.com/Rigellute/spotify-tui/runs/465367238?check_suite_focus=true
)
Error this time is
The store was unable to accept this snap.
binary_sha3_384: A file with this exact same content has already been
uploaded
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#295?email_source=notifications&email_token=ABMJBTJ33GZBV3ATCGGUHD3REQMQVA5CNFSM4KUU45P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMZFTWA#issuecomment-590502360>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMJBTJMWNSGH6EXVDXT74TREQMQVANCNFSM4KUU45PQ>
.
|
Nice one @hurricanehrndz, thanks so much for your help |
So I touched base with @popey, because I noticed that he is still pushing
SPT and he walked me through how he is doing the snap maintenance. Anyhow,
I'm confident that we do not need the action for now. Sorry for all the
added work, it has been a blast working with you.
…On Tue, Feb 25, 2020 at 1:44 AM Alexander Keliris ***@***.***> wrote:
Nice one @hurricanehrndz <https://github.com/hurricanehrndz>, thanks so
much for your help
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#295?email_source=notifications&email_token=ABMJBTPZ2CF5A4FDTOLVYALRETLATA5CNFSM4KUU45P2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEM3CJSQ#issuecomment-590750922>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMJBTIDZ7ELZ7GNYZKQ3BTRETLATANCNFSM4KUU45PQ>
.
--
Regards,
Carlos Hernandez
|
No problem at all! And thank you. Is this to say we should remove |
Please add secrets to repo before accepting pull request. See email. If you have any question please fee free to contact me via email.