Fix coveralls Token in Azure Pipelines builds
See original GitHub issueLooking at recent build, we should not provide run_coveralls
variable from outside:
It is intended to be set on the strategy matrix for selected jobs, so passing it on queue time will overwrite the intended behavior of running coverage test on a limited number of jobs.
On the other hand, we’re missing the COVERALLS_REPO_TOKEN
that should be added on the build definition (Edit > Settings > Variables), and uncheck “Settable at queue time” as nobody should know about or change this value.
@caolan I can help out. Thanks!
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Build options - Azure Pipelines | Microsoft Learn
If the build pipeline fails, you can automatically create a work item to track getting the problem fixed. You can specify the work...
Read more >Generate Code Coverage Reports using Coveralls and ...
To demonstrate the set-up we will first generate test coverage reports manually in our local environment and then optimize the process with ...
Read more >Collect code coverage using GitHub Action - Stack Overflow
In Azure DevOps, the code coverage view is within the Azure Pipelines view, but GitHub does not provide such a view. CodeCov, Coveralls...
Read more >Testspace Client
The Client executes on a host computer and communicates with Testspace via the Internet. It's a lightweight command-line tool with versions for Windows, ......
Read more >Common Build Problems - Travis CI Docs
If your build is failing due to unexpected segmentation faults in the language interpreter, this may be caused by corrupt or invalid caches...
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 Free
Top 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
Ah, the tests tab is cool – nice being able to see all tests that fail.
Anyway, the build seems to have stabilized!
It’s one test failing, see details on the Tests tab.
Some tests like this are flaky as we discussed in #1630. They are more likely to fail in OSX and Windows, and even more in Web tests.