3 ms·
> I think the most common is CI and build automation Common practice for CI is to actually run tests, though. How would you validate your macOS/iOS builds are
by dwaite 4y ago
> I think the most common is CI and build automation
Common practice for CI is to actually run tests, though. How would you validate your macOS/iOS builds are functional without still requiring VMs or real hardware?
- 90minuteAPI 4y agoIf those instances are only for tests/validation it could simplify some overall pipelines quite a bit.
- the_gipsy 4y agoThat doesn't justify the build part.
- jtdressel 4y agoYou could use this in addition to regular macOS machines. You can run tests from un-trusted branches, without worrying that something will expose the signing keys. Then after merging, you have a second machine / set of machines that only does signing. It increases the difficulty of an accidental or intentional leakage of your sensitive keys. (Note: I have not tested this yet)
- halbersa 4y agoWe have a pool of MacOS hardware to run tests, and another pool to perform signing. The latter is a security risk so very tightly controlled and locked down. They are a pita to maintain. Being able to sign on Linux will allow us to re-use the existing signing infrastructure we use for literally every other platform other than MacOS. It'll be more secure and much less maintenance.