Opened 5 years ago
Closed 4 years ago
#5595 closed enhancement (fixed)
Add continuous integration for macOS
| Reported by: | Krinkle | Owned by: | Itms |
|---|---|---|---|
| Priority: | Should Have | Milestone: | Alpha 24 |
| Component: | Build & Packages | Keywords: | |
| Cc: | Patch: | Phab:D2523 |
Description
The Jenkins jobs that performs compilation of libs and source, and runs the tests, is currently testing Linux (GCC) and Windows (VS2015).
It'd be nice if we could get a third slave for macOS. Or if direct integration with code review isn't feasible yet, a first step could be to have post-merge builds on commit, hourly or nightly.
Some prior discussion:
Change History (4)
comment:1 by , 5 years ago
comment:2 by , 4 years ago
| Keywords: | macos removed |
|---|---|
| Milestone: | Backlog → Alpha 24 |
| Owner: | set to |
| Patch: | → Phab:D2523 |
This is being tested since a few weeks. We use a machine from MacStadium.
comment:3 by , 4 years ago
I saw it on a few diffs some weeks ago, but not today, for example at https://code.wildfiregames.com/D2279.
Note:
See TracTickets
for help on using tickets.
The easiest option would be to setup a Travis CI yaml file in the GitHub mirror that would do run the build upon each syncing of the mirror (once a day currently). Travis CI also supports notifications through IRC which means we could be notified if the build starts failing, for example. The downside is that it is limited in frequency and does not prevent a failing build with early feedback in code review.
A more difficult option would be to have a macOS node added to our Jenkins server. I think if we ask MacStadium (<https://www.macstadium.com/opensource>) there's also a chance they might sponsor us a Mac mini, macOS VM. These could be attached to Jenkins via the SSH plugin (e.g. with a private key stored on the Jenkins master). If not sponsored, dedicated Mac mini starts at $59/mo, or cloud (vCPU) at $50/mo.