If I understood it correct you should be able to do this by following these Steps:
- First Build Step:
- Does the regular work. In your case: building, unit testing and packaging of the web application
- Depending on the result let it create a file with a specific name.
- This means if you want the low-risk-change to run afterwards create a file low-risk.prop
- Second Build Step:
- Create a Trigger/call builds on other projects Step from the Parameterized-Trigger
plugin. - Entery the name of your low-risk job into the Projects to build field
- Click on: Add Parameter
- Choose: Parameters from properties File
- Enter low-risk.prop into the Use properties from file Field
- Enable Don’t trigger if any files are missing
- Create a Trigger/call builds on other projects Step from the Parameterized-Trigger
- Third Build Step:
- Check if a low-risk.prop file exists
- Delete the File
Do the same for the high-risk job
Now you should have the following Setup:
- if a file called low-risk.prop occurs during the first Build Step the low-risk job will be started
- if a file called high-risk.prop occurs during the first Build Step the high-risk job will be started
- if there’s no .prop File nothing happens
And that’s what you wanted to achieve. Isn’t it?