Try using SWAMP
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
I'm assuming we could use SWAMP to do everything I wanted with SonarQube and then we wouldn't be responsible for maintaining our own code analysis.
It would be especially useful if we could tie SWAMP analysis to jenkins jobs, in response to github pushes.
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
The issue names no files or tests. Start by researching how SWAMP compares with SonarQube and whether it integrates with Jenkins and GitHub push events; done would require a decided, scoped integration plan rather than an open-ended proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, java
- Domain
- ci-cd, devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100