Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Use the Scale Up or Down a Pod via Manage Pods to bring the Pod up.
The How to Start/Activate Rancher Environment guide describes how to do this.

Deploying

...

Feature

...

Branches

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”.

Deploying Back-end Module Feature Branch

Some of this the back-end module deplyoment feature branch process is still described in the (Deprecated) Deploy/Update back-end module from feature branch documentation.

...

The Aggies team deploys a back-end module using the Jenkins Feature Branch Deployment process as follows:

...

Info

To determine what has been run previously (and with what parameters) the job history should be used:

Confirming a Back-end Module Feature Branch is Deployed

The build process should show success, but one should also visit the Aggies Scratch Environment to confirm that the back-end module is correctly deployed, registered, and enabled.

...

Code Block
Camnuda BPM Module (mod-camunda-1.2.0-SNAPSHOT.d18c2f2)

Deploying Front-end Module Feature Branch

The feature branch is deployed using the platform-complete-aggies branch from the ui-workflow project. That branch should be updated to contain the desired state of the code that is intended to be deployed. This branch may be force-pushed to.

Info

Before deploying, make sure that the platform-complete-aggies branch is up to date with the desired code changes.

The Aggies team deploys a front-end module using the Deploy UI Bundle (Deprecated) process as follows:

Note

The Deprecated UI Bundle build process is currently being used because the newer one at Deploy UI Bundle is not yet ready for use. Given the deprecated state, this process is subject to change at any point in time.

  1. The REFRESH_PARAMETERS is left unchecked.

  2. The RANCHER_CLUSTER_NAME is set to folio-dev.

  3. The RANCHER_PROJECT_NAME is set to aggies.

  4. The UI_BUNDLE_TAG is set to a desired image (if one is already bundled) or left blank.

  5. The UI_BUNDLE_TAG is left unchecked when UI_BUNDLE_TAG is to be used, but when a new bundle is desired then this must be checked.

  6. The FOLIO_REPOSITORY is set to platform-complete.

  7. The FOLIO_BRANCH is set to aggies-rancher.

  8. The TENANT_ID is set to diku.

  9. The CONSORTIA_ENABLED is left unchecked.

  10. Pushing the Build button will build the image.