Migrating Coveralls Report from Travis-CI to GitHub Actions

Search for a command to run...

No comments yet. Be the first to comment.
Create your personal cloud at home

ML lifecycle - https://www.coursera.org/learn/introduction-to-machine-learning-in-production This course introduces us to the ML lifecycle and some real life examples (yes, ML is not just used to predict house prices on a Jupyter notebook!). It walks...

For the ones migrating over from Windows/Linux ecosystem

SEO optimization, Functionalities, and PWA

Boost your system performance in just $135

Disclaimer: This is a very specific problem. It is relevant only if you had a travis ci pipeline setup for your GitHub repository and using
nycandcoveralls, and thinking of migrating to GitHub actions.
I followed this setup guide: Integrating with coveralls.io
I thought of migrating the build pipeline to GitHub Actions, but was hindered by this error:
> js-big-decimal@1.3.3 coverage /home/runner/work/js-big-decimal/js-big-decimal
> nyc report --reporter=text-lcov | coveralls
/home/runner/work/js-big-decimal/js-big-decimal/node_modules/coveralls/bin/coveralls.js:19
throw err;
^
Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}
(Use `node --trace-uncaught ...` to show where the exception was thrown)
npm ERR! code ELIFECYCLE
Now time to reveal the solution:
lcov"coverage": nyc report --reporter=lcov
Modify the pipeline to use the official Coveralls stage
- name: Test
run: |
npm run ci-test
npm run coverage
- name: Publish to coveralls.io
uses: coverallsapp/github-action@v1.1.2
with:
github-token: ${{ github.token }}
If you need a working example, check JS Big Decimal