Set up CI to run tests before merge master about chaincase-ios-beta HOT 4 CLOSED

I would agree with the label size - once you know what you want the actual configuration is all just YAML files.

Here's some examples in a repo I maintain: https://github.com/nathan-weinberg/jeeves/tree/master/.github/workflows

• lint and pytest run on all pull requests
• codecov runs on all merges to master (something like a deployment action would operate the same way)

These actions are all running on an Ubuntu box, but GitHub does have OSX runners available: https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners

That being said, y'all may want to configure a custom runner due to the nature of your work - this will give you more control but you will need to dedicate some compute resources to host/run the runner. My recommendation would be to see if the GitHub runners work for you first and only go custom if/when you know you need it.

from chaincase-ios-beta.

Hey @nathan-weinberg do you have thoughts on this and what about that label?

from chaincase-ios-beta.

This looks like a good guide https://www.raywenderlich.com/12258400-xcode-server-for-ios-getting-started#toc-anchor-001 .

I wonder if we can containerize xcode server / OSX Server?

from chaincase-ios-beta.

The minimum test here would be whether or not we can build in Release configuration. Having this alone would have saved loads of time and be a great threshold to merge. This would have been useful yesterday.

Far out I can see us spinning up an ephemeral regtest backend to test coinjoin rounds

from chaincase-ios-beta.