-
Notifications
You must be signed in to change notification settings - Fork 26
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
WIP: CI: Automated Linux builds #47
Conversation
Merge changes from upstream
@@ -24,6 +35,7 @@ deploy: | |||
- dist/latest-mac.yml |
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.
When you run yarn build_electron
does that produce dist/github/latest-linux.json
& dist/latest-linux.yml
for you? If so, we may want to include them for auto-update support
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.
No,
I only get this:
$ ls dist/
linux-unpacked partyshare.busterlabs.xyz-1.2.7-linux.deb partyshare.busterlabs.xyz-1.2.7-linux.tar.gz
I'll check how electron deals with Linux builds. Have to change the file reference too :-)
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.
Ah, no worries. Auto-update might not be supported on linux, I'll check.
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.
ok, you're right. unfortunately. I noticed my build crashed when trying to update. Can/should we disable asar for linux builds?
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.
Hmm, it looks like we should be creating a latest-linux.*
file according to the docs
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.
locally I don't get one. maybe do a ls -l
at before_deploy
key in .travis.yml
, so we can see what is actually there.
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.
Regarding the "crash":
$ ipfs daemon; partyshare.busterlabs.xyz
My log output: https://gist.github.com/hexagon6/14303b59b269877eafcd384b7dc17909
It crashes with ipfs version 0.3.10
, probably I should update.
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.
Nope, even with version 0.4.13 I get this Error:
_getConfig Error: non-zero exit code 1
while running: /opt/Partyshare/resources/app.asar.unpacked/node_modules/go-ipfs-dep/go-ipfs/ipfs config show
Error: api not running
at Stream.listeners.done.once (/opt/Partyshare/resources/app.asar/node_modules/ipfsd-ctl/src/exec.js:39:11)
at Stream.f (/opt/Partyshare/resources/app.asar/node_modules/once/once.js:25:25)
at emitTwo (events.js:125:13)
at Stream.emit (events.js:213:7)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
.travis.yml
Outdated
@@ -24,6 +38,7 @@ deploy: | |||
- dist/latest-mac.yml | |||
- dist/partyshare.busterlabs.xyz-*-mac.dmg | |||
- dist/partyshare.busterlabs.xyz-*-mac.zip | |||
- dist/Partyshare.deb |
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.
I believe the linux target should follow the artifactName
scheme, producing partyshare.busterlabs.xyz-1.2.7-linux.tar.gz
and partyshare.busterlabs.xyz-1.2.7-linux.deb
for the latest release?
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.
@bhstahl true, just noticed, see my comment above
@bhstahl could you trigger a draft build so we see the contents of dist/ after building on travis? |
Hmm, it's not letting me trigger a build since the code is in your fork. Let's merge this and work off master builds & PR's. Thanks for your help! |
Alright, looks like we didn't get the auto-update files, but we do have the |
* chore(ci): add travis setup * chore(linux): extend .travis.yml from upstream * fix yaml * fix(travis): move env key to matrix.include * chore(travis): update file artifact pattern * chore(travis): checkout produced files in dist/
BusterLabs/Partyshare
atdeploy
key:Busterlabs/Partyshare
tags: true
$ gem install travis; travis setup releases
snippet from .travis.yml for help