-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Added github actions workflow #325
Added github actions workflow #325
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So exciting, thank you!
I see an error in the logs
Error: Failed to execute goal org.eluder.coveralls:coveralls-maven-plugin:4.3.0:report (default-cli) on project cwlviewer: Build error: Either repository token or service with job id must be defined -> [Help 1]
Can we name the workflow some different than |
Can you also delete |
I edited the description to say "Fix #" and then the issue number so that merging this pull request will automatically close that issue :-) |
Sure, can you suggest something? |
We have to add the Coverall authentication token to secrets of this repository, only after that, it will be able to upload the coverage report on Coveralls. More about adding secrets to here:https://docs.github.com/en/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository |
- Removed travis.yml - Updated README.md badge and target URL - Updated pom.xml profile for CI Fixes #318
Secrets are not available to GitHub Actions workflows running from a PR based upon a fork of the main repo where the secret is stored, except for
https://docs.github.com/en/actions/reference/encrypted-secrets#using-encrypted-secrets-in-a-workflow So as documented in trautonen/coveralls-maven-plugin#136 (comment) you can pass the |
Made the changes! |
Fixes #318 Migrate from TravisCI to GitHub Actions
Description
We need to migrate from Travis CI to GitHub Actions
Motivation and Context
#318
How Has This Been Tested?
I created the GitHub actions workflow and checked it by running it on my forked repository, and it did pass all the checks.
Screenshots (if appropriate):
Types of changes
Checklist: