Rancher may be logged into here: https://rancher.ci.folio.org/dashboard/auth/login .
The deployment process is undergoing changes by the DevOps team and this process is accurate as of 2024/10/30.
The official documentation is found here: https://folio-org.atlassian.net/wiki/spaces/FOLIJET/pages/1396559/How+to+work+with+Rancher+environments .
The deployment process involves deploying back-end modules and front-end modules (UI modules).
The process for deploying for active development for back-end module involves Deploying via a Feature Branch.
Deploying Back-end Module Feature Branch
A feature branch is simply a branch on Github that is to be deployed.
These branches are classified as a “feature branch” even if they are bug fixes or something else that is not a “feature”.
The pipeline build select lists filtering can be slow and generally processes one character at a time.
It is easier and faster to type the search filter in another place (text editor, command line, browser tab, etc…) and then copy that over in the the filter.
The Aggies team deploys a module using the Jenkins Feature Branch Deployment process as follows:
The CLUSTER is set to
folio-dev.The NAMESPACE is set to
aggies.The MODULE_NAME is set to either
mod-workfowormod-camunda.The MODULE_BRANCH is set to the desired Github branch name for the given module (aka: Feature Branch).
The CONFIG_TYPE is set to
development.The MAVEN_ARGS is set to
-DskipTests.The LOAD_REFERENCE is left unchecked.
The LOAD_SAMPLE is left unchecked.
The SIMULATE is left unchecked.
The IGNORE_ERRORS is left unchecked.
The AGENT is set to
jenkins-agent-java17.The REFRESH_PARAMETERS is left unchecked.
Pushing the Build button will build the image.