The workflowScripts table of the rd_workflow database lists all the programs used by the Release Manager system and their associated workflow (currently there is only one). The table contains the following columns:
- scriptId - the ID for the specific script. This is used in other tables to identify the script the data is for
- workflowId - The ID of the workflow the script is part of. This value is the primary key of the workflows table. Currently there is only one workflow defined.
- script - The path to the program/script that should be executed
- queue - The LSF batch queue the program/script should be executed in
- user - The user name that the program/script should be executed under
- description - A short name describing the program/script that is used in LSF job names as well as RM settings in the settings table.
The current (July 2013) contents of the table are:
scriptId | workflowId | script | queue | user | description |
---|---|---|---|---|---|
1 | 1 | /u/gl/glastrm/grits-cpp/bin/checkoutBuild | medium | glastrm | Checkout |
2 | 1 | /u/gl/glastrm/grits-cpp/bin/compileBuild | buildq | glastrm | Compile |
3 | 1 | /u/gl/glastrm/grits-cpp/bin/testBuild | buildq | glastrm | Test |
4 | 1 | /u/gl/glastrm/grits-cpp/bin/finishBuild | express | glastrm | Finalize |
5 | 1 | /u/gl/glastrm/grits-cpp/bin/createReleaseBuild | medium | glastrm | Installer |
6 | 1 | /u/gl/glastrm/grits-cpp/bin/cleanBuild | short | glastrm | Clean |
7 | 1 | /u/gl/glastrm/grits-cpp/bin/eraseBuild | short | glastrm | Erase |
8 | 1 | /u/gl/glastrm/grits-cpp/bin/createDoxygen | medium | glastrm | Doxygen |
9 | 1 | /u/gl/glastrm/jenkinsTest.pl | express | glastrm | Launch |