Project

General

Profile

Actions

Task #3833

closed

Jenkins+Travis: Removal of macOS 10.9 slave

Added by Alex Afanasyev about 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:

Description

macOS 10.9 has been removed from the list of officially supported platform, but we kept it in the build matrix in Jenkins CI. As of right now, one of the VM failed and I don't plan to restore it, therefore we will remove it from the checks. As a consequence, I have a question: Are there NFD users who are bound to macOS 10.9 and cannot upgrade? (I remember there were hardware limitations for the upgrade, but not sure if it applies to 10.9->10.10).

The second task for this issue related to travis ci. Previously, travis used 10.9 slaves. Based on the current documentation (https://docs.travis-ci.com/user/osx-ci-environment/) and status of recent build this is no longer the case. The default version of used OSX is 10.11, which requires update of .travis.yml configuration in supported projects (NFD, ndn-cxx, ndn-tools, NLSR, ndns, and others).

Actions #1

Updated by Eric Newberry about 9 years ago

How long should I wait for feedback on the use of 10.9 before starting this task?

Actions #2

Updated by Alex Afanasyev about 9 years ago

The update of .travis.yml can start right away, given it is a bug. If there is a way to request a specific version of OSX, then it would be even better.

For feedback, let's wait at least a week.

Actions #3

Updated by Davide Pesavento about 9 years ago

Alex Afanasyev wrote:

If there is a way to request a specific version of OSX, then it would be even better.

That should be possible using osx_image config key: https://docs.travis-ci.com/user/osx-ci-environment/#OS-X-Version

Actions #4

Updated by Davide Pesavento about 9 years ago

Alex Afanasyev wrote:

Are there NFD users who are bound to macOS 10.9 and cannot upgrade? (I remember there were hardware limitations for the upgrade, but not sure if it applies to 10.9->10.10).

IIRC the hardware reqs were the same for 10.8, 10.9, 10.10, and 10.11. The reqs were only recently increased with Sierra (10.12). So from this point of view there is no reason not to upgrade.

Actions #5

Updated by Eric Newberry about 9 years ago

  • Status changed from New to In Progress
Actions #6

Updated by Eric Newberry about 9 years ago

  • Status changed from In Progress to Code review
  • % Done changed from 0 to 100

Commits have been pushed to Gerrit for NFD, ndn-cxx, NLSR, ndns, ndn-tools, and ndn-group-encrypt. These appear to be the only projects under github.com/named-data that use Travis CI.

Actions #7

Updated by Eric Newberry about 9 years ago

ndn-atmos also uses Travis CI, but it does not appear to attempt a build on OSX.

Actions #8

Updated by Eric Newberry about 9 years ago

  • % Done changed from 100 to 50

Reduced completion percentage to 50% because removal of the 10.9 nodes from Jenkins has not started.

Actions #9

Updated by Alex Afanasyev almost 9 years ago

Given the hardware requirements do not prevent 10.9 to be upgraded to later versions and the fact that nobody spoke up on the mailing list, we can safely remove 10.9 from the build matrix now.

Actions #10

Updated by Eric Newberry almost 9 years ago

The OSX-10.9 and OSX-10.9-64bit labels have been removed from all applicable projects.

Actions #11

Updated by Eric Newberry almost 9 years ago

  • % Done changed from 50 to 100
Actions #12

Updated by Alex Afanasyev almost 9 years ago

  • Status changed from Code review to Closed

I have removed and stopped the remaining 10.9 slave.

Actions

Also available in: Atom PDF