deployModule Jenkins Pipeline
- Yaroslav Ishchenko
deployModule Jenkins Pipeline helps Dev Teams to deploy Application Module Versions to Dev Environments from a range of available sources for verification.
Pipeline description
This Pipeline is used when Developer Engineer needs to deploy an Application Module Version from a range of application sources like Github (source code repository branch), Dockerhub (container image repository) to existing Dev Environment (Kubernetes Cluster Namespace).
Steps to trigger
To deploy new module version you need to follow steps:
Log into Jenkins instance: https://jenkins-aws.indexdata.com/
Navigate to Pipeline: folioRancher → tmpFolderForDraftPipelines -> Eureka -> deployModule
Click on Build with Parameters button
Set Required pipeline parameters
Click Build button
Wait for pipeline completion (it takes about 3-7 minutes to complete)
Known issues
To deploy Application Module from Source Code Repository located on Github you have to use jenkins-agent-java17 value for AGENT pipeline parameter or run fails on CI part.
To deploy Application Module from Cointainer Image Repository located on Dockerhub you are free to use either jenkins-agent-java17 or rancher value for AGENT pipeline parameter.
Parameter description
Parameter name | Default Value | Description |
|---|---|---|
MODULE_NAME | n/a | Folio Module name |
MODULE_SOURCE | github/folio-org | Application Module Source:
|
MODULE_BRANCH | dynamic depends on MODULE_NAME | Module Branch name in Github repository |
MAVEN_ARGS | -DskipTests | Don’t run unit tests on build |
CONTAINER_IMAGE_TAG | n/a | Container Image Tag to deploy from selected Docherhub Repository (see MODULE_SOURCE parameter value) |
CLUSTER | folio-edev | Kubernetes Cluster name |
NAMESPACE | dynamic depends on CLUSTER | Kubernetes Cluster namespace |
CONFIG_TYPE | development | Configuration profile name:
|
AGENT | rancher | Jenkins Agent name:
|
REFRESH_PARAMETERS | unchecked | Re-read existing pipeline params |
Parameter set example
