Make a CI action to run each supported kind of analysis
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 912
- Forks
- 74
- PR merge metrics
- No merged PRs in 30d
Description
We can use scripts/run_analysis.sh to run CI for each supported kind of analysis on push. However, the trick is to be able to use a locally built image. This might take a long time to build and run on each push / PR. Possibly we should replace the current 'build_docker' action with a 'build and run analysis' action
Things that need to be run: (fixed packages can be chosen for each)
- dynamic analysis: pypi
- dynamic analysis: npm
- dynamic analysis: ruby
- dynamic analysis: crates.io
- dynamic analysis: packagist
- static analysis: npm
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
Start with scripts/run_analysis.sh and the current build_docker action to understand how analyses and locally built images are invoked. Define how the CI action should run the six listed analysis cases on push, including fixed packages for each, and verify that each case completes using the locally built image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, shell
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100