Build Tilesets
A collection of Build Tiles that work together to create a releasable unit of software
e.g. lint, test, build docker image, test docker image, create kubernetes resources, package up change notes.
| Component Name | Description |
|---|---|
| chalk-environment | Tile aggregation to declare how to create Environment images Building environment images for managing namespaces on Kubernetes |
| chalk-dockerfile | How to build dockerfiles into docker images Building a docker image from a Dockerfile |
| chalk-micronaut-v3 | Packaging up Micronaut V3 applications as an uberjar on openjre slim To build applications based on the Micronaut framework |
| chalk-micronaut-v3-library | Building java libraries that include Aspects to enable Micronaut components To build libraries based on the Micronaut framework |
| chalk-micronaut-v2 | Packaging up Micronaut applications as an uberjar on openjre slim To build applications based on the Micronaut framework |
| chalk-micronaut-v2-library | Building java libraries that include Aspects to enable Micronaut components To build libraries based on the Micronaut framework |
| chalk-composite | Build tiles for validating and packaging Java dependency compositions Building a stricly defined set of Java dependencies for reuse, while validating the resolved dependency tree is free from known CVE |
| chalk-microfrontend | Packaging react applications with yarn to deploy statically on Nginx Build react frontends ready to deploy on Kubernetes |
| chalk-nodefrontend | Run npm and package the result on a node image Building front ends with npm that deploy using express on a nodejs base image |
| chalk-api | Build Tiles for verifying and packaging Restful apis Building projects that represent restful contracts in Java |
| chalk-decisions | Tile aggregation for building decisions documentation templates Building documentation projects with decisions (ADR) |
| chalk-developer-experience | The standard tiles for creating environment images Building the standard documentation with a local flavour |
| chalk-dockerfile-application | Aggregate the rules for how to build dockerfiles into Applications Building a docker image from a Dockerfile with manifests for deploying it to Kubernetes |
| chalk-documentation | The standard tiles for building documentation templates Packaging documentation templates into zips for reuse |
| chalk-jar | Adding build information to the jar so we can see the state of the environment when it was created Building Java Libraries |
| chalk-jenkins | Rules for building a customised Jenkins image Building a Customer configured Jenkins with extra plugins, volumes and secret templates |
| chalk-jenkins-scripts | Rules for building a customised Jenkins pipelines and scripts Packaging Jenkins scripts for deployment |
| chalk-kubernetes-aggregate | Rules for validating and create zips of kubernetes resources Packaging up a set of distinct Applications as siblings |
| chalk-kubernetes-application | Rules for validating and create zips of scoped kubernetes resources Packaging up the definition of how to deploy an application to Kubernetes |
| chalk-kubernetes-applications | Rules for validating and create zips of kubernetes resources Packaging up a set of distinct Applications as siblings |
| chalk-kubernetes-product | Rules for validating and create zips of nested kubernetes resources Declaring a group of Applications to be deployed together |
| chalk-namespace | The namespace tile aggregation is about creating a simple namespace without ingress controllers |
| chalk-nodefrontend-yarn | Run yarn and package the result on a node image Building front ends with yarn that deploy using express on a nodejs base image |
| chalk-pipeline | The pipeline tile aggregation is about creating a Run Platform subset in a multi tenant build environment To deploy pipelines on clusters where you don’t need to manage the RUN platform deployment as well |
| chalk-run-platform-eks | Build a run platform image suitable for deploying on an EKS cluster Automatically managing the RUN platform on an EKS cluster |
| chalk-run-platform-gke | Build a run platform image suitable for deploying on a GKE cluster Automatically managing the RUN platform on a GKE cluster |
| chalk-run-platform-kops | Build a run platform image suitable for deploying on a Kops Kubernetes cluster on AWS Automatically managing the RUN platform on a self managed Kubernetes cluster |
| chalk-sonarqube | Rules for building a customised Sonarqube image for deploying Developer edition To build a local version of SonarQube at the declared version |
| chalk-thorntail | Build thorntail applications into non optimised runnable docker images Building applications based on the Thorntail application server |
| chalk-tile | Testing tiles and packaging correctly is critical to the health of the whole system, this tile makes it easy Building tiles and ensuring they are highly like to work as intended |
| tuff-keycloak-integration-test | Composition of tiles for running Keycloak during integration testing Testing applications that require a keycloak connection during integration tests |
| tuff-keycloak-tile | Run keycloak as a support app Testing applications that require a keycloak connection to run |
| tuff-mysql-integration-test | Composition of tiles for running mysql during integration test Testing applications that require a mysql database during integration tests |
| tuff-mysql-tile | Run mysql as a support app Testing applications that require a mysql database to run |
| tuff-oracle-database | Run oracle database as a support app Testing applications that require an oracle database to run |
| tuff-oracle-database-xe11 | Run oracle express database version 11 as a support app Testing applications that require an oracle express 11 to run |
| tuff-oracle-database-xe18 | Run oracle express database version 18 as a support app Testing applications that require an oracle express 18 to run |
| tuff-percona-tile | Run percona as a support app Testing applications that require an percona database to run |