A Cartridge is a set of resources that are loaded into ADOP for a particular project. They may contain anything from a simple reference implementation for a technology to a set of best practice examples for building, deploying, and managing a technology stack that can be used by a project.
This cartridge consists of source code repositories and jenkins jobs for a sample Docker CI pipeline.
- Make sure adop-pluggable-scm is loaded into your ADOP/C.
Cartridge loads the source code repositories
This cartridge generates the jenkins jobs and pipeline views to -
- Performs static code analysis using Dockerlint on the Dockerfile in the Git repository.
- Builds the Dockerfile in the repository.
- Performs a vulnerability scan on the built image using Clair Requires Clair Platform Extension
- Image testing by analysing the outputs from docker inspect against a known configuration file.
- Container testing by creating a new testing image internally.
- Pushes the built and scanned image to a registry.
- Pull the built image from the registry and deploy it as a container.
- Manual step allowing you to clean up the deployed containers.
Note : The credential parameter used in the jenkins job expects the docker hub credentials to be added to jenkins with ID docker-credentials.
Please view license information for the software contained on this image.
Documentation will be captured within this README.md and this repository's Wiki.
If you have any problems with or questions about this repository, please contact us through a GitHub issue.
You are invited to contribute new features, fixes, or updates, large or small; we are always thrilled to receive pull requests, and do our best to process them as fast as we can.
Before you start to code, we recommend discussing your plans through a GitHub issue, especially for more ambitious contributions. This gives other contributors a chance to point you in the right direction, give you feedback on your design, and help you find out if someone else is working on the same thing.