The use case for this option is when another Pipeline job wants call the VectorCAST pipeline job and has checked out the VectorCAST Project. This options sets up the following parameters to be passed in from another Pipeline Job.
- VCAST_PROJECT_DIR - Path to the location of the VectorCAST Project or root of the external SCM checkout. This path will be prefixed to the entry for VectorCAST Project
- VCAST_FORCE_NODE_EXEC_NAME - Forces VectorCAST Jobs to be run on a specific node instead of a node with a label matching the compiler
The two parameters can be used independently. If you are using VCAST_PROJECT_DIR to specify an external VectorCAST Project, please ensure that any setup/tear down script is properly setup. For example, if a setenv.bat is in the external repository, you can prefixed the script as follows:
call ${VCAST_PROJECT_DIR}\setenv.bat
Syntax of what a calling job may use to call a parameterized VectorCAST Pipeline job
catchError(buildResult: 'SUCCESS', stageResult: 'FAILURE', catchInterruptions : false ) {
build job: 'UnitTestingProject_vcast_pipeline',
parameters: [string(name: 'VCAST_PROJECT_DIR', value: 'C:\\UnitTesting\\Project'),
string(name: 'VCAST_FORCE_NODE_EXEC_NAME', value: 'MyTestNode')]
}