Automate CI Build for Existing Targets

[aspickard]

{NOTE} CI currently running for Web Target on Travis-CI. (iOS in progress..)
No static analysis is setup or running.

[gavinhenderson]

Just wanting to start around automation, I know we might get round to it for a while.

Are we set on continuing to use Travis CI for our automation?

I have been using Github actions a lot for projects lately and its really good. There is a huge marketplace of prebuilt actions you can pull from, and there is bound to be stuff for iOS build and electron builds that we can use.

My vote would be to migrate to Actions

[aspickard]

+1 for utilizing actions, but that does lock us in to GitHub

[gavinhenderson]

Yeah that's a good point but I think we are already pretty locked into GitHub anyway with the amount of stuff we have on it so we might as well double down

[jcope]

I second moving it over to GitHub actions- currently it is set up on my Travis CI account, but needs updating to reflect the new repo layout. I having used the actions before, but it seems similar and should support our environment.

…

On Jun 4, 2021, at 3:38 AM, Gavin Henderson ***@***.***> wrote:  Yeah that's a good point but I think we are already pretty locked into GitHub anyway with the amount of stuff we have on it so we might as well double down — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[gavinhenderson]

• Signing stuff
• Add a simple link to website to download binaries (for folk who are afraid of github)