Web Interface
- Limit concurrent jobs
- Build pushed branches
- Build pushed pull requests
- User Management
- Share encrypted variables with forks
- Share SSH Keys with forks
- Enable access to old build jobs
- Limit access to build job logs
- Auto cancel branch builds
- Auto cancel pull request builds
- Environment variables
- Cron jobs
- Caches
- Trigger a custom build
This page lists settings that are only available in the Travis CI .com web user interface.
Limit concurrent jobs #
The maximum number of concurrent jobs depends on the total system load, but one situation in which you might want to set a particular limit is:
- if your build depends on an external resource and might run into a race condition with concurrent jobs.
Build pushed branches #
If ON, builds will be run on branches that are not explicitly excluded in your .travis.yml.
If OFF, builds won’t run on pushed commits on branches.
Build pushed pull requests #
If ON, builds will be run on new pull requests.
User Management #
Simple ‘trigger build’ control. Allow or prevent users with appropriate access to the repository to trigger a build for the repository. By default, all synchronized users with access to the repository are allowed to trigger a build.
Share encrypted variables with forks #
In the case of a fork-to-base pull request:
- If this setting is ON, the encrypted environment variables will be available to the forked repository, which means that builds in the forked repository will have access to the encrypted environment variables from the base repository. This may be a less secure approach yet allows for a collaboration using forks and Pull Requests (PRs).
- If this setting is OFF and the build relies on any encrypted environment variable, the PR from fork to base repository will fail. This secures your base repository encrypted environmental variables by putting a constraint on accessing them from forks.
Read more: Pull Requests and security restrictions
Share SSH Keys with forks #
In the case of a fork-to-base pull request:
- If this setting is ON, the custom SSH keys from the base repository will be available to the forked repository, which means that the build in the forked repository will be able to use the custom SSH keys from the base repository. Consider setting to ON if your collaboration model requires working with Pull Requests (PRs) from forked repositories or there are dependencies defined, which rely on SSH key from base repository.
- If this setting is OFF and the build is relying on custom SSH keys i.e. for fetching some additional dependencies, it will fail with a no access error.
Read more: Pull Requests and security restrictions
Enable access to old build jobs #
This setting allows you to increase security by preventing access to old job logs older than 360 days. Or, in the case of a necessity, users can explicitly enable access to public and private old job log repositories.
The following are the available configurations:
- If this setting is ON, it enables access to build job logs older than 365 days.
- If this setting is OFF, access to build job logs older than 365 days is unavailable via UI or API calls.
Limit access to build job logs #
Similarly, this setting allows you to restrict access to build job logs for any user without write/push access rights to the repository. Limit job log visibility to only those that needed it. Enable this setting and ensure job logs are only available to users with respective read or write access to the individual repository.
The following are the available configurations:
- If this setting is ON, it allows access to build job logs only for users with write/push permissions to this repository. Limits access to build job logs via UI and API.
- If this setting is OFF, users with read access to the repository can access the build job logs.
Please note that the ‘Limiting access to build job logs’ repository setting applies only to users with ‘write/push’ permissions.
Auto cancel branch builds #
If you are only interested in building the most recent commit on each branch you can use this new feature to automatically cancel older builds that are in the queued state and are not yet running.
Auto cancel pull request builds #
If you are only interested in building the most recent commit on each branch you can use this new feature to automatically cancel older builds that are in the queued state and are not yet running.
Environment variables #
Variables defined in repository settings are the same for all builds, and when you restart an old build, it uses the latest values. These variables are not automatically available to forks.
Define variables in the Repository Settings that:
- differ per repository.
- contain sensitive data, such as third-party credentials.
More information on environment variables.
Cron jobs #
Travis CI cron jobs work similarly to the cron utility; they run builds at regular scheduled intervals independently of whether any commits were pushed to the repository. Cron jobs always fetch the most recent commit on a particular branch and build the project at that state. Cron jobs can run daily, weekly or monthly, which in practice means up to an hour after the selected time span, and you cannot set them to run at a specific time.
Check the full cron jobs docs for more information on skipping and detecting cron jobs.
Caches #
More information on caching.
Trigger a custom build #
Custom builds exist only on Travis CI and will not appear in your Git history.
BETA Custom builds are a beta feature. Please provide feedback on GitHub.