...
| 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.
Each build in the pipeline ends up with a build hash appended to the end of the package version.
The hash is generally a short github hash, which as an example might be something like 70a44d3.
GIven a mod-workflow with a package version of say 1.2.0-SNAPSHOT, then the resulting pipeline built version would be mod-workflow-1.2.0-SNAPSHOT.70a44d3.
This can be confirmed or denied by visiting the Aggies Scratch Environment Software Versions page.
Under the OKAPI Services column, there should be two particular modules of concern, mod-workflow and mod-camunda.
The mod-workflow module might look like this:
| Code Block |
|---|
Workflow Module (mod-workflow-1.2.0-SNAPSHOT.70a44d3) |
The mod-camunda module might look like this:
| Code Block |
|---|
Camnuda BPM Module (mod-camunda-1.2.0-SNAPSHOT.d18c2f2) |