actions/superlint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-11-22 16:51:05 -05:00
Code Issues Projects Releases Packages Wiki Activity
superlint/.automation
History
Zack Koppert 35e2d160a4
Add trivy scans for container security (#1209) 
* Create trivy.yml

* Add descriptive names

* Add fs mode to catch package.lock issues

* use script to get around timeout

* use script to get around timeout

* set it

* set it

* update deps

* Align with comment style

* fix headeer

* npm audit fix to patch vulnerabilities

Signed-off-by: Zack Koppert <zkoppert@github.com>

Co-authored-by: Lukas Gravley <admiralawkbar@github.com>
2021-02-17 16:03:30 -06:00
..
test Update snakefmt to 0.3.0 and black to 20.3 (now supported by snakefmt). (#1212) 2021-02-17 07:32:40 -06:00
clean-code-base-for-tests.sh Remove duplicated code (#1137) 2021-01-12 12:54:00 -06:00
cleanup-docker.sh break out: (#990) 2020-11-12 11:27:34 -06:00
README.md Format Markdown 2020-07-21 12:08:05 -05:00
trivy-security-scan.sh Add trivy scans for container security (#1209) 2021-02-17 16:03:30 -06:00
upload-docker.sh break out: (#990) 2020-11-12 11:27:34 -06:00
validate-docker-labels.sh Try to build with caching to help build times (#1051) 2020-12-04 12:49:09 -06:00

README.md

.automation

This folder holds automation scripts to help deploy and cleanup DockerHub images of the Super-Linter

cleanup-docker.sh

This script uses GitHub Actions so that when a PR is merged and closed, the GitHub Action is triggered. It will then search DockerHub for the image that was deployed during the development, and remove it.

upload-docker.sh

This script uses GitHub Actions so that when a push to the repository is committed, it will complete the following:

  • Checkout the source code
  • Build the Docker container for Super-Linter using that source code
  • Upload the container to DockerHub

When the script is triggered on master, it will push with the tag:latest which is used by all scripting for general availability. When the script is triggered in a branch, it will push with the tag:NameOfBranch which can be used for:

  • testing
  • troubleshooting
  • debugging
  • Note: The branch name will be reduced to alphanumeric for consistency and uploading

test

This folder holds all Test Cases to help run the CI/CT/CD process for the Super-Linter.