coverallsapp / coverallsapp/github-action
Frustrated with Jenkins/Coverall Setup.
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 520
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
We just purchased coveralls for our private Github repository and are running into some configuration issues.
- Our language is Python.
- We use jenkins to create a .coverage file and this is placed in the root of the system
- We can not seem to get the .coverage file to be given to the coveralls.io site.
Does anyone have any setup guides beyond the sparse doc on setting up Jenkins with Coveralls in a private repository setting? We are really getting frustrated.
Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Jenkins, Python, the .coverage file, Coveralls, and a private GitHub repository. Start by reviewing the existing Jenkins and Coveralls setup documentation; clarify the steps for sending the generated .coverage file to Coveralls in a private repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, documentation, testing
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100