Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid redundant builds of OSX with xcode7.3 #4043

Merged

Conversation

matiasgarciaisaia
Copy link
Member

xcode7.3 is now the default OS X version in TravisCI, so we're building the project twice with the same configuration.

The second build was added in #2595, when xcode6.1 was the default. It doesn't make sense anymore.

I'm currently working on the project's build matrix for a long-term solution - I'll probably explicitly state each OSX version -, but this should speed builds up in the mean time.

https://docs.travis-ci.com/user/osx-ci-environment/#OS-X-Version now says:

Travis CI uses OS X 10.11.6 (and Xcode 7.3.1) by default .

xcode7.3 is now the default OS X version in TravisCI, so we're
building the project twice with the same configuration

See https://docs.travis-ci.com/user/osx-ci-environment/#OS-X-Version
@RX14
Copy link
Contributor

RX14 commented Feb 16, 2017

How useful has building on both xcode versions been? Has it caught any bugs? Would be useful to know for #3721.

@matiasgarciaisaia
Copy link
Member Author

(BTW, from the docs, we're redundantly building twice with xcode7.3 for 5 months)

@bcardiff
Copy link
Member

@RX14 i don't recall any bug catched. I think it's fine to merge this and later increase the matrix if needed.

I do think we should support older macs though.

@ysbaddaden
Copy link
Contributor

I restarted the hung OSX job on Travis.

@matiasgarciaisaia matiasgarciaisaia merged commit a068d41 into crystal-lang:master Feb 17, 2017
@matiasgarciaisaia
Copy link
Member Author

Merging, as nothing broke

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants