travis branches: Reporting stale build information

[robbieaverill]

I'm experiencing this with both travis branches on the command line, as well as using the Ruby library to list branches.

Example

git clone [email protected]:silverstripe/cwp-recipe-kitchen-sink.git
cd cwp-recipe-kitchen-sink
travis branches

$ travis branches
Detected repository as silverstripe/cwp-recipe-kitchen-sink, is this correct? |yes| 
2.1.2:        #242  failed     Update development dependencies
2.2.1:        #241  failed     Update development dependencies
# Relevant below
2.1:          #239  passed     Merge pull request #26 from creative-commoners/pulls/2.1/all-changes-config
2.2:          #225  failed     Merge pull request #25 from creative-commoners/pulls/2.2/ckan-registry-module
master:       #218  passed     Merge branch '2.2'
# Relevant above
2.2.0:        #185  failed     Require content-blocks 2.1.0 stable instead of rc1
2.2.0-rc1:    #152  errored    Update development dependencies
2.1.1:        #88   failed     Update development dependencies
2.1.1-rc2:    #68   failed     Update development dependencies
2.1.1-rc1:    #64   errored    Update development dependencies
2.1.0:        #49   failed     Update development dependencies
2.1.0-rc2:    #45   failed     Update development dependencies
2.1.0-rc1:    #44   errored    Update development dependencies
2.1.0-beta1:  #16   failed     Update development dependencies

The branches I'm concerned with above are 2.1, 2.2 and master. The latest builds for each of these in the Travis UI is:

• 2.1 branch: build #254 (failed)
• 2.2 branch: build #255 (passed)
• master branch: build #253 (passed)

As you can see, these branch build statuses are referencing old builds. Is there something I'm missing here? It seems like a bug to me.

---

System Ruby: Ruby 2.3.7-p456 Operating System: Mac OS X 10.14.3 RubyGems: RubyGems 2.5.2.3

CLI Version: 1.8.9 Plugins: none Auto-Completion: yes Last Version Check: 2019-03-04 11:47:01 +1300

Session API Endpoint: https://api.travis-ci.org/ Logged In: as "robbieaverill" Verify SSL: yes Enterprise: no

Endpoints org: https://api.travis-ci.org/ (access token, current)

[robbieaverill]

If it's helpful, I think all three of these branches mostly trigger builds from cron now, rather than from merges or pushes

[robbieaverill]

I've worked around this by using custom HTTP calls instead of using the Travis Ruby library

[az-pz]

What is the custom HTTP call for scheduling cron travis build at a certain time, @robbieaverill ?

[robbieaverill]

@arizzubair I used Faraday and connect to the Travis API manually