Deploy Folio with custom modules versions
- Sergii Masiuk
- Dima Tkachenko
- Eldiiar Duishenaliev
As of Apr 22, 2025 below guide will be using 2 Jenkins servers: Community(C) and Kitfox(K)
Please pay attention to server’s highlights (C) || (K)
Purpose
Deploy new EUREKA environment with custom version of any module (e.g. folio-module-sidecar)
To deploy environment with version you need to pre-build and push image to ECR first.
In case of UI modules there is no need to pre-build step.
Destroy existing environment, if exists via job: Link ***(K)***
On Jenkins (Dashboard > v2 > DevOps_Tools > modules > build_push) Link ***(C)***
Parameter | Required/Optional | Value |
|---|---|---|
PLATFORM | Required | Select platform (OKAPI/EUREKA) |
MODULE_NAME | Required | Select the module to install |
MODULE_BRANCH | Required | Select what module branch to use for build |
MAVEN_ARGS | Optional | Maven build arguments, default value -DskipTests to skip tests after build |
PUSH_IMAGE_TO_ECR | Optional | Check to push image to ECR |
PUSH_DESCRIPTOR_TO_ECR | Optional | Check to push descriptor |
AGENT | Required | Select agent to build on |
On platform complete repo create separate branch from snapshot and change selected modules versions in files install.json and eureka-platform.json (eureka specific) to new image version you builded in step 1.
in case of UI modules changes should also be made in files stripes-install.json and package.json with the branch or commit hash specified.
On Jenkins (Dashboard > folioRancher > tmpFolderForDraftPipelines > Eureka > createNamespaceFromBranch-Eureka) In this job select FOLIO_BRANCH from step 2 and other parameters according to your needs and deploy the environment. ***(K)***
After successful deployment confirm the version via GUI or with command:
kubectl get deployment <deployment name> -n <namespace name> -o jsonpath="{.spec.template.spec.containers[*].image}"