Versions Compared

Old Version 9

changes.mady.by.user Kevin Day

Saved on

compared with

New Version Current

changes.mady.by.user Kevin Day

Saved on

Key

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

...

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 feature branch is now deployed by modifying the package.json in the Platform Complete Aggies Rancher Branch.
The @folio/workflow must be set to the gitub repository and branch (such as my_custom_branch), like this:

Code Block
languagejson
"@folio/workflow": "https://github.com/folio-org/ui-workflow.git#my_custom_branch",
Note

The simpler approach of just using platform-complete-aggies branch from ui-workflow may not consistently due to potential build time caching.
To work-around this, the solution is to make a new commit hash in the Platform Complete Aggies Rancher Branch for every rebuild.
The method of updating the package.json file as described above achieves this result.

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

  1. The CLUSER is set to folio-dev.

  2. The NAMESPACE is set to aggies.

  3. The FOLIO_REPOSITORY is set to platform-complete.

  4. The FOLIO_BRANCH is set to aggies-rancher.

  5. The CONFIG_TYPE is set to development.

  6. The TENANT_ID is set to diku.

  7. The UI_BUNDLE_BUILD is usually checked (uncheck to select an existing bundle).

  8. The UI_BUNDLE_TAG is set left alone or blank except when UI_BUNDLE_BUILD is unchecked.

  9. The CUSTOM_HASH is set left alone.

  10. The CONSORTIA is left unchecked.

  11. The AGENT is set to jenkins-agent-java17.

  12. The REFRESH_PARAMETERS is left unchecked.

  13. Pushing the Build button will build the image.

Info

The reason for using the platform-complete-aggies branch for ui-workflow deployment is because the aggies-rancher branch in the platform-complete repository is set to point to the platform-complete-aggies branch in the ui-workflow repository.