Trigger a Travis-CI rebuild without pushing a commit?

Question

Using Travis-CI, is it possible to trigger a rebuild without pushing a new commit to GitHub?

Use case: A build fails due to an externality. The source is actually co

Answer 1

Here's what worked for me to trigger a rebuild on a PR that Dependabot had opened, but failed due to errors in .travis.yml:

1. Close the PR
2. Wait for Dependabot to comment ("OK, I won't notify you again about this release, but will get in touch when a new version is available."). It will remove its branch.
3. Restore the branch Dependabot removed (something like dependabot/cargo/tempfile-3.0.4).
4. Open the PR again

Answer 2

I have found another way of forcing re-run CI builds and other triggers:

1. Run git commit --amend --no-edit without any changes. This will recreate the last commit in the current branch.
2. git push --force-with-lease origin pr-branch.

Answer 3

Travis now offers a way to trigger a "custom" build from their web UI. Look for the "More Options" menu button on the right side near the top of your project's page.

You'll then be presented with a dialog box in which you can choose the branch and customize the configuration:

At the time I'm writing this it is in beta, and appears to be slightly buggy (but I expect they'll get the problems ironed out soon).

Answer 4

I just triggered the tests on a pull request to be re-run by clicking 'update branch' here:

Answer 5

sometimes it happens that server do made some mistakes. try log out/sign in and everything might be right then. (Yes it happened this afternoon to me.)

Answer 6

If the build never occurred (perhaps you didn't get the Pull-Request build switch set to on in time), you can mark the Pull Request on Github as closed then mark it as opened and a new build will be triggered.