|
Instead of running the module deployment as a stage of the snapshot/release build, create a pipeline to deploy modules to kubernetes.
Requirements:
- takes a module/version as a parameter
- fails if module is not successfully deployed to kubernetes
- can be triggered when a release/snapshot job is complete.
Benefits over existing kubeDeploy step in the buildMvn pipeline:
- Increased transparency: The current deployment method deploys a job on kubernetes which in turn deploys the. module. If the job itself is deployed correctly, but the tasks in the job failed then it's hard to see the failure from jenkins (pipeline will succeed)
- Better separation from release job. This can be triggered by release jobs, but insulates the release process itself from depending on the health of the k8 infrastructure (which isn't specifically related to releasing a module.
|