This project produces the Entando Kubernetes Operator images.
mvn clean package -Pjvm,license
Notes:
jvm
is the standard profile- you can omit
license
profile if you want just compile or test, it is needed by image build
From project base dir:
cd app-controller && docker build . -f Dockerfile.jvm -t {image}
cd ../app-plugin-link-controller && docker build . -f Dockerfile.jvm -t {image}
cd ../database-service-controller && docker build . -f Dockerfile.jvm -t {image}
cd ../dbjob && docker build . -f Dockerfile.jvm -t {image}
cd ../keycloak-controller && docker build . -f Dockerfile.jvm -t {image}
cd ../plugin-controller && docker build . -f Dockerfile.jvm -t {image}
cd ../controller-coordinator && docker build . -f Dockerfile.jvm -t {image}
You can use the following command preferably in an environment without KUBECONFIG or similar configuration
ENTANDO_DEFAULT_ROUTING_SUFFIX={hostname}
\ mvn
\ -DpreDeploymentTestGroups=unit,in-process
\ -Ppre-deployment-verification,jvm
\ clean test
Notes:
- To activate mvn test plugin you need to use a specific profile (
pre-deployment-verification
) - the profile
pre-deployment-verification
is used to execute test without deploy artifacts, but for some test you need a working kubernetes configuration - the profile
post-deployment-verification
is used to execute integration tests which need a deployed artificats - the environment varible ENTANDO_DEFAULT_ROUTING_SUFFIX is used to select an hostname as prefix in tests about ingress and other components