Travis CI API issues (backlogged recipes)
See original GitHub issueWe are waiting for conversion to go through. Travis CI seems quite slow to start this process. As that has gotten a couple pings, I’m opening an issue here to track status of this issue.
If you have PR on staged-recipes that you are working on actively, please try merging with master
and removing any recipes from the directory recipes
that you are not proposing. Commit those changes and push.
Issue Analytics
- State:
- Created 7 years ago
- Comments:88 (88 by maintainers)
Top Results From Across the Web
API fails occassionally · Issue #6284 · travis-ci/travis-ci - GitHub
We are seeing a 403 Client Error on Travis CI's API periodically for about the last week. ... Travis CI API issues (backlogged...
Read more >Common Build Problems - Travis CI Docs
One possible cause for builds failing unexpectedly can be calling set -e (also known as set errexit ), either directly in your .travis.yml...
Read more >Unpatched Travis CI API Bug Exposes Thousands of Secret ...
An unpatched security issue in the Travis CI API has left tens of thousands of developers' user tokens exposed to potential attacks.
Read more >Continuous Integration and Delivery - Microsoft Open Source
Travis CI can be used for open source projects at no cost but developers must purchase an enterprise plan for private projects. This...
Read more >Sources Catalog - Faros AI
Backlog, Beta. Bitbucket, GA. Bitbucket Server, GA. Buildkite, GA. Circle CI, GA. Clubhouse, GA. DataDog, Beta ... Travis CI Enterprise, GA. VictorOps, GA....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We have drawn the conclusion, based on testing within conda-smithy, that the TravisCI API is currently broken and will be raising it with them. I do not believe we are in a position to merge anything to staged-recipes until this is resolved (or we cease registering with TravisCI).
Just opened #1114 which should solve these issues (exchanging this problem for a need for a recurring update of the token - I do not know at what frequency that will be).