Travis CI and Appveyor aren't working properly due to erroneous configs.
Opened this issue · 5 comments
Travis and Appveyor are only working as far as checking compiles. OTOH they are unable to push releases to GitHub and we don't have other options rn D: so here we will discuss how to push releases to GitHub..
- Put a separate repo which Appveyor and Travis can deploy to.
- Keep spamming commits and perfect build pushes. Travis is only able to push releases for Linux rn, as in v1.2 is using Travis builds for Linux, Windows was locally compiled BTW.
also, travis-ci keeps returning pass for failing commits, lawls fixed with upgrade to CircleCI :D
Patch solution:
create a separate branch which the CI systems will keep up to date with master by compiling the master branch, then checking out the build branch and then commiting instead of pulling, then pushing it to the branch. Ta-da! done 🥇 : 3
Will be releasing 1.2.1 with a scaffolded version of this
further more, electron-packager will also resolve the always passing even when it fails :3
Linux deploys are working with CircleCI, fixing the pass for failing commits.
Travis and AppVeyor will probably be deploying to S3 soon.
This means that we might not be deploying to a separate branch, but to S3 :D
I'm setting up S3, the commit will come and close this, but there's a problem with macOS tho D:
AppVeyor won't be deploying to S3 lolz, apparently I didn't notice that AppVeyor already uploads artifacts to its' servers.