You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EDIT: I tried to do things through the config file which are only available for the web UI. Solution is to go to https://travis-ci.org/owner/repor/settings
and click the pretty button beside "build pull requests".
The problem is probably with either the documentation or the branch restriction commands themselves.
Expected behavior:
I Google for "Travis skip building PR" or "Travis build only on push to master" and find a section of Travis docs telling me how to prevent builds from being triggered by pull requests.
Or documentation around branches.only explicitly states whether the branches.only setting is meant to dissable building on pull requests, and directs the user to how to do that.
Or documentation for before_deploy and related commands explicitly states whether or not those steps will be run when Travis builds a PR
Or the docs on deploying to S3 discuss the problem of building PRs.
What I find when trying to build only on commits to master (and never build PRs) is an inconclusive closed issue and the related Travis docs. The docs do not specify which commands will be run when Travis runs on PRs and which will only be run on commits to master.
However, when I make a pull request to the repo, Travis runs on the PR (and obviously fails, since it can't decrypt the keys for very good security reasons).
The only reason I'm using Travis on this repository at all is to build and deploy the site when PRs are merged into the master branch. These are not actions that should ever be taken at the time a PR is first opened.
The text was updated successfully, but these errors were encountered:
EDIT: I tried to do things through the config file which are only available for the web UI. Solution is to go to
https://travis-ci.org/owner/repor/settings
and click the pretty button beside "build pull requests".
The problem is probably with either the documentation or the branch restriction commands themselves.
Expected behavior:
branches.only
explicitly states whether thebranches.only
setting is meant to dissable building on pull requests, and directs the user to how to do that.before_deploy
and related commands explicitly states whether or not those steps will be run when Travis builds a PRActual behavior:
What I find when trying to build only on commits to master (and never build PRs) is an inconclusive closed issue and the related Travis docs. The docs do not specify which commands will be run when Travis runs on PRs and which will only be run on commits to master.
An Example:
I followed the deploying to S3 docs to write this .travis.yml. Note that I tried to tell it to build only on master with
However, when I make a pull request to the repo, Travis runs on the PR (and obviously fails, since it can't decrypt the keys for very good security reasons).
The only reason I'm using Travis on this repository at all is to build and deploy the site when PRs are merged into the master branch. These are not actions that should ever be taken at the time a PR is first opened.
The text was updated successfully, but these errors were encountered: