Semantic release blocked by always-failing Travis CI on merge push
See original GitHub issueWe have semantic-release setup but it never triggers because the Travis CI always fails on push
.
I think the sequence is:
- PR is ready, Merge button pushed.
- Github signal merge commit pushed to master
- Travis gives event, starts build with TRAVIS_EVENT_TYPE = “push”
- test fail to contact browserstack browsers.
- CI exits before running semantic-release.
The travis Build History is red for branch master going back months: https://travis-ci.org/github/karma-runner/karma/builds?utm_medium=notification&utm_source=github_status
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Push rules not working as expected using semantic release
On our GitLab pipeline, when enabling Push Rules for commit messages the pipeline fails when running npx semantic-release.
Read more >Travis CI - semantic-release
It's recommended to run the semantic-release command in the Travis deploy step so if an error occurs the build will fail and Travis...
Read more >Travis failed push but passed PR
PR will merge your changes into the base branch and run CI tests. Push will run CI tests on the current branch. Merging...
Read more >sbt Reference Manual — Combined Pages
Setting up Travis CI with sbt ... Execution semantics of tasks ... to test across large projects of independent releases before pushing the...
Read more >⚓ Query: Advanced Search
T321021 MediaWiki core CI failing: OutputPageTest::testAddBodyClasses ... T295341 `npm -s run test:size` is blocking merges to many extensions.
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
Ok excellent, thanks! I can’t use that link either but I know how to reset the travis values to ones I can access. I will be able to do that Monday.
AFAICT the karmarunnerbot has to be a project Admin, not Maintainer. (The github protected branches are confusing and buggy0.