build binaries with github actions

[oxr463]

Closes: #331

[oxr463]

See also: https://rtyley.github.io/bfg-repo-cleaner

git clone --mirror https://github.com/cs01/gdbgui.git
bfg --delete-files downloads gdbgui.git

[bjorn3]

You could also use https://github.com/actions/upload-artifact to attach artifacts to the current github actions run.

[cs01]

There is some documentation that points to those binaries which will need to be updated.

[oxr463]

Depends on: #335

[cs01]

Thanks, I will try to take a look this weekend

[oxr463]

Thanks, I will try to take a look this weekend

Cool, once we have the binaries compiled, then we'll be good to go!

[cs01]

I noticed there were some syntax errors and lint errors preventing basically anything from working, including building the executables. I fixed the, so this PR should be rebased on the latest master commit.

I verified the ubuntu build still works, but the Windows build failed. I didn't re-test on a mac since I'm on unix right now. The windows build might do better outside of docker in github actions, with a runs-on of windows-2019. I'll be happy to delete that windows Dockerfile since it contains a lot of black magic, so hopefully it works. If not, it will have to be fixed up to account for whatever changed in the the apt repos, etc.

How do we confirm the GitHub actions are working? I want to be sure they work and inspect the published files before deleting them from the gdbgui github repo. I went to the actions tab but didn't see anything.

[cs01]

why is this being built with so many versions?

[cs01]

I made a new branch based off this and got everything working except for associating the artifacts with the release itself: https://github.com/cs01/gdbgui/tree/cs01/test-actions. I recommend resetting this PR to that branch.

Re associated artifacts with github releases: I can look up how to do it, but if you have any tips or can reset this PR to the cs01/test-actions branch, and make changes on top of that, that would be preferred. https://github.com/cs01/gdbgui/actions/runs/166916337 shows all the OS's have the executables built and artifacts stored. I don't think it's necessary to store artifacts for all pushes, only for actual github releases.

[cs01]

I will probably end up migrating all the Travis tests to GitHub actions. The actions will build the executable as well, and at the end the executable will be published.

[cs01]

Since this PR allowed edits from maintainers I went ahead and pushed to it. Thanks for kicking off this PR and motivating me to look into GitHub actions.

I'm going to land now with the following:

• Executables built on all pushes/pull requests for all OS's
• Artifacts are stored if on the master branch

Some other changes made along with this:

• Smoke test that executable works after building it
• Add md5 checksum file of executable
• nox sessions for each OS with verification that the expected OS is being used

Future work:

• [DONE] Delete executables from source code. I am going to wait for a successful release with artifacts attached to a release in GitHub before doing this.
• Potentially automatically associate a build with a release. For now I'll just download the artifacts, then drag & drop them manually to associate with a release.