When using Travis with GitHub, why are some build numbers missing? E.g. at https://travis-ci.org/FezVrasta/bootstrap-material-design/builds, we can see a few missing build numbers between the last successful build (232), and the first build with an error (237).
How can one find the missing builds?
Travis separates commits that are part of pull requests from commits that are not.
The missing builds are under the Pull Requests tab.
Related
Using Groovy and Jenkins Pipeline, is there any method of listing all git repositories and commits checked out using checkout during the course of a build aside from manually parsing the build log? I'm aware that changeSets allows one to see what changes have been made between runs, and that by bookkeeping all of these commits, it is possible to piece together the last known set of commits that were successful in building, but deleting/losing any of these builds would result in an incomplete log and prevent reconstruction. I'd like to know if there's an easier way of obtaining a git configuration for a given build.
I am pushing a PR on a project, and the build fails.
I know that the master branch works.
How do I tell circleCI to build all the commits in-between so that I see which change broke?
This isn't currently possible. If you push one commit at a time, CircleCI will build each one. If you push multiple commits at once though, it will only build the head commit.
We do have a feature request open for this, which can "heart" to add your support: https://discuss.circleci.com/t/manually-trigger-a-build-all-commits-between-two-revisions/10160
Ricardo N Feliciano
Developer Evangelist, CircleCI
I just set up Travis CI and I noticed that every time I push a branch to the remote repo, it kicks off a build. From my reading of the docs, this is not expected behavior...it should instead only kick off builds when a pull request is opened and on subsequent pushes to that branch.
Also, when I do open a pull request, it kicks off two builds, as shown in the
image.
What I want is the following:
push remote branch (Travis CI does nothing)
create PR (Travis CI kicks off 1 build)
push commit to the branch (Travis CI kicks off 1 build).
Does anyone know what additional configuration is required to achieve this result? Many Thanks.
The expected workflow can be achieved by disabling the "Build Pushes" feature as described here: https://blog.travis-ci.com/2014-03-05-repository-settings/
I submitted this pull request and the Travis-CI build failed.
I pushed another commit to fix the failing test and the second build failed.
I posted this comment asking why is it falling (I could not reproduce locally and I noticed this failure on other pull requests).
One day after I posted this comment I noticed that the build status is passing and the failing job which I linked to shows that the job finished successfully.
When I look in the pull request build history I notice my first failing build and my second build which it now says it passed.
But I cannot find my second failing build.
Can anyone explain how something like this can happen?
Is there any way to find and see that failing build?
Unfortunately, when you restart a build on Travis CI, the previous build log is lost at the moment.
It's possible that the build failure is intermittent hence restarting the build might make it fail again.
Each time I push to Github, it appears to trigger two Travis CI builds - one for the PR and one for the Push itself. They also appear to be separate builds, judging by the links.
What's the exact difference between the two, and how can I enable it so that only one runs?
You can uncheck either building pushes or PRs in the TravisCI settings for the repository:
The difference between them is:
/pr builds automerged state (as if you merged the PR and ran the tests on that, note: it won't run if the PR can't be automerged).
/push builds for the current state of the branch you pushed to (as if you ran the tests on your local copy you just pushed),
What's happening in your scenario looks like this:
continuous-integration/travis-ci/push - only run test on branch
continuous-integration/travis-ci/pr - merge and run tests
And this is completely okay - but if you want to get rid of one of the builds you need to disable Build pushes or Build pull requests in your project settings on Travis.
Sources:
https://github.com/travis-ci/travis-ci/issues/1504
https://github.com/twisted/twistedchecker/pull/93
https://blog.travis-ci.com/2014-03-05-repository-settings/