search

composer / semver

Semantic versioning utilities with the addition of version constraints parsing and checking.
MIT License
3.15k stars 76 forks source link

travis: use container based build #11

Closed TomasVotruba closed 9 years ago

alcohol commented 9 years ago

Thanks.

TomasVotruba commented 9 years ago

:+1:

localheinz commented 9 years ago

@TomasVotruba

Just as an FYI, builds were already implicitly running on container-based infrastructure, see https://travis-ci.org/composer/semver/jobs/71392653.

Also see http://docs.travis-ci.com/user/workers/container-based-infrastructure/#Routing-your-build-to-container-based-infrastructure:

The default behavior, when no sudo usage is detected in any customizable build phases, depends on the date when the repository is first recognized by Travis CI:

  • For repos we recognize before 2015-01-01, linux builds are sent to our standard infrastructure.
  • For repos we recognize on or after 2015-01-01, linux builds are sent to our container-based infrastructure.
TomasVotruba commented 9 years ago

@localheinz I know about this dating. That's kinda strange, because this repo was established in 2011.

alcohol commented 9 years ago

@TomasVotruba No actually it was created this month. But the history dates back further because it was exported from composer/composer.

TomasVotruba commented 9 years ago

@alcohol I see, interesting exception. Thanks for explaining :)

Shall I send removal PR? But I think it could be confusing for further devs as it was for me.

alcohol commented 9 years ago

No it's fine to have it in there anyway. It just makes it more explicit. No worries.

TomasVotruba commented 9 years ago

:+1:

localheinz commented 9 years ago

@TomasVotruba

:+1: