Travis CI (.travis.yml)
Travis CI configuration file
| File match |
.travis.yml
|
|---|---|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/travis-ci-travis-yml/latest.json |
| Source | https://www.schemastore.org/travis.json |
Validate with Lintel
npx @lintel/lintel check
All of
Definitions
Your account name, token and optional channel
2 nested properties
When the optional solution key is present, Travis will run NuGet package restore and build the given solution.
By default, Travis CI will assume that your Podfile is in the root of the repository. If this is not the case, you can specify where the Podfile is
A list of packages to install via brew. This option is ignored on non-OS X builds.
CRAN mirror to use for fetching packages
Dictionary of repositories to pass to options(repos)
The CPU Architecture to run the job on
The operating system to run the job on
The Ubuntu distribution to use
sudo is deprecated
16 nested properties
To install packages not included in the default container-based-infrastructure you need to use the APT addon, as sudo apt-get is not available
3 nested properties
To update the list of available packages
To install packages from the package whitelist before your custom build steps
If your build requires setting up custom hostnames, you can specify a single host or a list of them. Travis CI will automatically setup the hostnames in /etc/hosts for both IPv4 and IPv6.
Firefox addon
Chrome addon
RethinkDB addon
PostgreSQL addon
MariaDB addon
Sauce Connect addon
Coverity Scan addon
5 nested properties
GitHub project metadata
Where email notification of build analysis results will be sent
Commands to prepare for build_command
The command that will be added as an argument to 'cov-build' to compile your project for analysis
Pattern to match selecting branches that will run analysis. We recommend leaving this set to 'coverity_scan'
Homebrew addon
5 nested properties
SourceClear addon
Snaps addon
BrowserStack addon
7 nested properties
Travis CI clones repositories without the quiet flag (-q) by default. Enabling the quiet flag can be useful if you're trying to avoid log file size limits or even if you just don't need to include it.
Control whether submodules should be cloned
Skip fetching the git-lfs files during the initial git clone (equivalent to git lfs smudge --skip),
In some work flows, like build stages, it might be beneficial to skip the automatic git clone step.
Specify handling of line endings when cloning repository
Specify which branches to build