Task #3234
closed
What's the hardware/CI cost of keeping the 10.8 slave alive for a few more releases?
"hardware/CI cost" is not a problem, but 10.8 support is dropped as soon as 10.11 is released per platform policy, which means developers are not required to fix any 10.8-specific error.
As long as everything works, I can keep everything running as is. The only issue comes when something going to break (I mean slave) and will require non-trivial intervention.
As for VM requirement. I'm currently running 10.8 slaves with following resources:
- 4096 MB ram
- 1 cpu
- 30 GB disk
- Status changed from New to Feedback
- % Done changed from 0 to 100
- Estimated time changed from 3.00 h to 10.00 h
Two new OSX 10.11 slaves added to the build matrix (hosted in CSU)
- Status changed from Feedback to Closed
ndn-tools does not have a 10.11 build slave. Is it intentional?
We were having issues with 10.11 slave and it was removed from builds. I have added it back.
- Target version changed from v0.5 to v0.4
Also available in: Atom
PDF