actions/superlint
1
0
Fork 0
mirror of https://github.com/super-linter/super-linter.git synced 2024-12-22 15:22:16 -05:00
Code Issues Projects Releases Packages Wiki Activity
superlint/.automation
History
Marco Ferrari 527c5a3986
Generate a code coverage report (#1353) 
* Generate a code coverage report

* make linters happy

* adding action and badge

* no report for me

* Upload the test report

* adding folders

* spaces not tabs

* makefiles love tabs

* spacing is important

* rawr

* Fix makefile

* Add diagnostic info

* Set UID and GID

* Make info

* Add docker images in diagnostic info

* Move info before testing the local action

* Add missing -C to git diff-tree

* Reset ownership

* Add missing quotes

* Sudo

* Attempt to fix ARM test

* Attempt to fix go test

Co-authored-by: Admiral Awkbar <admiralawkbar@github.com>
2021-04-22 13:56:18 -05:00
..
test Generate a code coverage report (#1353) 2021-04-22 13:56:18 -05:00
clean-code-base-for-tests.sh adding Python MyPy (#1401) 2021-03-24 14:00:23 -05: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
update-actions-version.sh it wants the long one... (#1313) 2021-03-05 09:41:45 -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.