lint/.automation
Lukas Gravley ab24b82199
Adding actionlint (#1775)
* Adding action lint

* adding tests

* adding tests

* Update Dockerfile

Co-authored-by: Masaya Suzuki <15100604+massongit@users.noreply.github.com>

* cleanup name

* fix test

* typo

* fix file name

* fix our own errors

* more cleanup

* angry

* make it happy

* stop double jobs

Co-authored-by: Masaya Suzuki <15100604+massongit@users.noreply.github.com>
2021-07-19 09:28:49 -05:00
..
test Adding actionlint (#1775) 2021-07-19 09:28:49 -05:00
clean-code-base-for-tests.sh Inspec additional Tests (#1497) 2021-05-03 16:30:02 -05:00
cleanup-docker.sh Inspec additional Tests (#1497) 2021-05-03 16:30:02 -05:00
README.md Format Markdown 2020-07-21 12:08:05 -05:00
update-actions-version.sh Adding actionlint (#1775) 2021-07-19 09:28:49 -05:00
upload-docker.sh adding fixes (#1516) 2021-05-04 11:33:21 -05:00
validate-docker-labels.sh Use GitHub Action cache (#1687) 2021-06-24 10:19:42 -05:00

.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.