superlint/.automation
Jeremiah 00c70f4b2c
Update snakefmt to 0.3.0 and black to 20.3 (now supported by snakefmt). (#1212)
* Update snakefmt to 0.3.0 and black to 20.3 (now suppored by snakefmt).

* Update pipfile for ansible 5.0

* Align pipfile python with Docker alpine image

* Explicitly pin python minor version in dockerfile

* Ansible updates

* Add missing cryptography dependencies

* Eliminate deprecated ansible syntax

* Update expected output for ansible

* Try to add regex to handle test run length

* Yaml doc syntax fixes

* Flailing attempt at tap wildcard

* Catch dynamic output from ansible-lint

* Update regex

* Fix regex statement

* Fix tap output

* Update go error message (issue from master branch)

* Fix regex

* Ansible strikes back

* Fix tap output

* Fix json tap

* Update r tap
2021-02-17 07:32:40 -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
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

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