-
-
Notifications
You must be signed in to change notification settings - Fork 187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parallel builds webhook #212
Comments
Is this not sufficient for your use case? https://github.com/marketplace/actions/coveralls-github-action |
There is PR #216 in the works that seems to address this issue. |
Yes, I managed to get it working in my own project using the code from that PR: https://github.com/agronholm/smtpproto/tree/master/.github/workflows |
Hi, thanks everybody for your replies. I haven't tried it yet but, looking at the diff, #216 should work my end as well. Nevertheless, in my opinion it would be nice to have a dedicated CLI argument in Maybe the Thanks |
@sanjioh I've just merged #216 and am planning a release pending fixing some test issues (mostly Python/PyPy versions that got deprecated while my back was turned) in #218. I might consider accepting a PR for adding a flag for this, but I just want to get up-to-speed on this issue first (I don't use Github Actions myself) and only so long as its not easily solve-able outside this project. @agronholm 's suggestion seems to work pretty well -- looks like you could also do this in curl? Am I understanding correctly that adding the following line to your Github Actions workflow would also do the trick? - name: Tell Coveralls that the parallel build is finished
run: |
curl -k \
https://coveralls.io/webhook?repo_token=$COVERALLS_REPO_TOKEN \
-d "payload[build_num]=$GITHUB_SHA&payload[status]=done"
env:
COVERALLS_REPO_TOKEN: ${{ secrets.COVERALLS_REPO_TOKEN }} Looks like the - name: Tell Coveralls that the parallel build is finished
run: |
BUILD_NUM=$(python -c 'import coveralls; print(coveralls.Coveralls.load_config_from_github()[1])')
curl -k \
https://coveralls.io/webhook?repo_token=$COVERALLS_REPO_TOKEN \
-d "payload[build_num]=$BUILD_NUM&payload[status]=done"
env:
COVERALLS_REPO_TOKEN: ${{ secrets.COVERALLS_REPO_TOKEN }} |
It seems coveralls and github have changed stuff around again. Additionally, there now appears to be a first-class github service name, which takes the default-provided secrets.GITHUB_TOKEN for authentication, removing the need to manually enter the token. I have managed to work around this for now by doing this: In my workflow file:
In my test script:
This brings coveralls in line with the updated github action from them, and additionally now also properly works with pull requests. Workflow for reference: |
Closing, as the GH Actions specific issues have been solved and the |
Hi,
as per Coveralls docs:
https://docs.coveralls.io/parallel-build-webhook
a webhook needs to be called when parallel builds are done with reporting, to inform the service that no more submissions will be performed and thus it can start processing/displaying coverage data.
Is this something that
coveralls-python
can do? I'm running my CI on GitHub Actions and I'm not able to invoke the webhook without implementing a custom solution.Thanks!
The text was updated successfully, but these errors were encountered: