Test your Travis CI knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What is a reasonable general principle for deciding what belongs in a project's `script` step versus its `install` step in a Travis CI configuration?
Questions in this quiz
What is a reasonable general principle for deciding what belongs in a project's `script` step versus its `install` step in a Travis CI configuration?
What is the standard configuration file name Travis CI looks for in a repository?
What are the standard build lifecycle phases in a Travis CI build, in their typical execution order?
What does the `language` key in a `.travis.yml` file specify?
What does `env` (environment variable configuration) in `.travis.yml` typically enable, particularly when combined with a build matrix?
What does it mean that Travis CI builds run in an isolated, ephemeral environment (like a fresh virtual machine or container) for each build?
What is a general reason a project might migrate away from Travis CI to an alternative like GitHub Actions in more recent years?
What is Travis CI?
What is a "build matrix" in Travis CI, and what problem does it solve?
What does the `branches` configuration key in `.travis.yml` typically control?
What is a general reason a team might prefer a hosted CI service like Travis CI over running/maintaining their own self-hosted CI infrastructure (like a self-managed Jenkins server)?
What is the purpose of `after_failure` in a Travis CI build lifecycle?
Gaps to close?
Read the curated Travis CI notes — core concepts, patterns, interview prep.