The workflows table of the rd_workflow database contains the descriptions of the various workflows available to the Release Manager. The workflowId from this table is used to identify what workflow various scripts and processes were run under. The table only has two columns
- workflowId - The numeric ID of the workflow used as a key in other tables
- workflowName - The name of the workflow
The table only has two entries: workflow 1 - Release Manager and workflow 2 - RM-Jenkins. However, only workflow 1 is used. In the switch to use Jenkins for some of our builds I created the second workflow. However, because of the way many of the RM programs are coded, it was much easier to add another script to the existing workflow rather than define a completely new one to call that single script. Trying to run with two different workflows would have seriously broken the existing system.