Changes between Version 3 and Version 4 of DeveloperGuidelines/Testing/CI


Ignore:
Timestamp:
10/24/14 21:09:49 (7 years ago)
Author:
anirudh.tiwari
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperGuidelines/Testing/CI

    v3 v4  
    2121Along the way, commit status of the commits involved is updated, which in turn shows on !GitHub as either a warning that the build is still running, that the pull request should be merged with caution because the build failed, or that it can be merged safely because the build was successful.
    2222
    23 Travis CI builds a pull request when it's first opened and when commits are added to the pull request throughout its lifetime.
     23Travis CI builds a pull request when it's first opened and when commits are added to the pull request throughout its lifetime. Rather than test the commits from the branches the pull request is sent from, it tests the merge between the origin and the upstream branch.
    2424
    25 Rather than test the commits from the branches the pull request is sent from, it tests the merge between the origin and the upstream branch
    26 Rather than test the commits from the branches the pull request is sent from, it tests the merge between the origin and the upstream branch
    27 Rather than test the commits from the branches the pull request is sent from, it tests the merge between the origin and the upstream branch
     25To enable Travis CI for your developer branch. Sign in with your !GitHub account on [https://travis-ci.org/ Travis CI], in the process you'll be asked to grant Travis CI a set of access permissions. Once you are done with it, go to the profile page of your Travis account. There you'll find all your repositories, flip the switch for those repositories for which you want to enable the Travis CI service.