Ubuntu Precise edge opt-in examples

00-intro.md

Welcome to our new Ubuntu Precise infrastructure for public repositories

What should I do?

• If your current .yml file is just using our existing sudo enabled Precise builds, then look here.
• If you're using a simple os: matrix, then look here
• If you're currently using our containerized Precise builds but would like to try the new virtualized platform, then look here
• If you're using a more complex matrix:, look here

You can also review the files below for some additional details on the build routing but the items outlined above should get you going.

Getting help if you have issues?

If you currently have access to the Travis CI slack team, then reach out to Dan, Emma, or Brandon there. Otherwise, file an issue, include [precise-gce] in the issue title, and include /cc @meatballhat @emdantrim @solarce in the issue description.

00-toplevel-gce-precise.travis.yml

# Most explicit routing to GCE Precise
sudo: required
dist: precise

01-matrix-include.travis.yml

matrix:
  include:
  # Most explicit routing to GCE Precise
  - sudo: required
    dist: precise
  # GCE Precise with a default `dist: precise`
  - sudo: required
  # Explicit routing to GCE Trusty
  - sudo: required
    dist: trusty
  # Container-based Precise due to `sudo: false`
  - sudo: false
  # Blue Box (legacy) due to `group: legacy`
  - sudo: required
    dist: precise
    group: legacy
  # Blue Box (legacy) due to `group: legacy` with default `dist: precise`
  - sudo: required
    group: legacy

01-toplevel-container-precise.travis.yml

# If repo enabled on Travis in 2015+,
# will route to Container-based
group: stable

01-toplevel-gce-precise.travis.yml

# If repo enabled on Travis prior to 2015,
# will route to GCE Precise
group: stable

Otherwise, file an issue, label it with precise-gce

FYI, you can't add labels to an issue if you don't have commit access to the repo.

@lukeyeager, you're correct, including [precise-gce] in the subject is sufficient, thanks!