superlint/.automation
Lukas Gravley cf19607c3c
Gherkin (#1011)
* adding gherkin

* adding to array

* fix space

* Update Dockerfile

* adding rules

* adding rules

Co-authored-by: SVN Migrator <someone@somewhere.com>
2020-11-19 09:54:20 -06:00
..
test Gherkin (#1011) 2020-11-19 09:54:20 -06:00
clean-code-base-for-tests.sh break out: (#990) 2020-11-12 11:27:34 -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
upload-docker.sh break out: (#990) 2020-11-12 11:27:34 -06:00
validate-docker-labels.sh break out: (#990) 2020-11-12 11:27:34 -06: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.