Posts: 6,485
Threads: 176
Joined: Jan 2012
Thanks: 131
Given 1074 thank(s) in 852 post(s)
Since we've established the policy that PRs can only be merged after a successful CI build, it makes little sense to have Travis do two builds - one for the Push and one for the actual PR. We could save time if only the PR build was activated.
Is it even possible to set that up? I have no idea where in the project settings to look for this.
Posts: 783
Threads: 12
Joined: Jan 2014
Thanks: 2
Given 73 thank(s) in 61 post(s)
09-25-2015, 10:18 PM
(This post was last modified: 09-26-2015, 12:25 AM by xoft.)
Its a trivial change in the travis settings, but you have to login to travis with your github account to do it. I can also turn off the fixed concurrent build limit now.
Posts: 783
Threads: 12
Joined: Jan 2014
Thanks: 2
Given 73 thank(s) in 61 post(s)
I've discovered a problem with disabling push builds. Its what we use for coverity builds.
Posts: 6,485
Threads: 176
Joined: Jan 2012
Thanks: 131
Given 1074 thank(s) in 852 post(s)
Any chance of getting it to work without the push builds? Isn't there a setting in .travis.yml to only build specific branches?
Posts: 783
Threads: 12
Joined: Jan 2014
Thanks: 2
Given 73 thank(s) in 61 post(s)
I can only find settings to turn branches off. Still we might be able to turn off every branch except coverity scan.