Closed rtyler closed 5 years ago
Started by user rtyler
[Sat Jun 22 16:10:23 UTC 2019] Starting branch indexing...
16:10:23 Connecting to https://api.github.com using jenkinsadmin/****** (GitHub access token for jenkinsadmin)
Examining jenkins-infra/uplink
Checking branches...
Getting remote branches...
Checking branch master
‘Jenkinsfile’ found
Met criteria
No changes detected: master (still at 578229626409b0ae7d04d3b92bd446ece06c347a)
Checking branch aci
‘Jenkinsfile’ found
Met criteria
No changes detected: aci (still at d26770da3dad479548e4f176617b65049007d96e)
2 branches were processed
Checking pull-requests...
Getting remote pull requests...
Checking pull request #38
‘Jenkinsfile’ not found
Does not meet criteria
1 pull requests were processed
Finished examining jenkins-infra/uplink
[Sat Jun 22 16:10:24 UTC 2019] Finished branch indexing. Indexing took 0.93 sec
Finished: SUCCESS
Apparently the github-branch-source plugin is bad at its job.
This is a stab in the dark, assuming that the availability issues we're seeing are relating to connections not being managed properly in uplink.