Set up additional github integrations
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
There are a few other useful things we can do using github integrations:
- Code coverage:
- codecove.io
- See https://github.com/codecov/example-gradle
- Static analysis:
- lgtm.com
- See https://lgtm.com/projects/g/linkedin/ambry/ci/ for PR integration
- Continuous integration:
- travis-ci improvements
- Increase timeouts in integration tests so we can run them on travis
- Set up additional build environments (like OSX)
- Possibly test with openjdk in addition to oraclejdk
- Add the fancy "build passing" icon to our readme
If anyone else has other ideas, feel free to add to this issue.
Contributor guide
No contributing guide indexed for this repository
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
Review the repository's current Travis CI setup and integration-test configuration, then compare the Codecov example-gradle and LGTM PR integration references. Establish which coverage, static-analysis, build-environment, timeout, and README changes are in scope. Done means the selected integrations and build environments run successfully and the README reflects the resulting build status.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, java
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100