Code

Changes between Initial Version and Version 1 of Ticket #19891, comment 21


Ignore:
Timestamp:
05/18/13 05:08:50 (11 months ago)
Author:
gcc
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #19891, comment 21

    initial v1  
    1 @dokterbob I think from the discussion above that we **don't** want Travis to build master or any other branch of django, only pull requests? Core devs have their own Jenkins setups to run tests for them. 
     1@dokterbob I think that: 
    22 
    3 So polluting the timeline is not a problem, because it should never be necessary to make a commit on any branch of django/django to trigger a Travis build because these branches are not built by Travis. Is that correct? 
     3* Core devs have their own Jenkins setups to run tests for them. 
     4* So we **don't** care that Travis builds any branch of Django, only about the building of pull requests. 
     5* It appears that we can't disable building branches, but we don't need to do anything if a branch build fails, because we don't care. 
     6* So we should never need to make a commit on a branch just to force a Travis build. 
     7 
     8Is that correct? 
    49 
    510I had trouble getting started on closing this ticket so I've made a TODO list of the [wiki:ContinuousIntegration outstanding issues]. I hope this is useful. 
    6