We currently create child configurations to set combinations of build schedules that can't be declared with a single cron expression and set different variable values (like disabling unit tests or enabling coverage reports). In order to keep all the statistics contained in s singular configuration, these child configs have a single step to trigger their parent. (If you still have the last backup I sent you can see for example root/maven/DSBASE_5000_10_0_0/{daily,nightly,weekly}. It would be helpful to declare all the different schedules locally on the config that does the actual build, where each schedule has a name field. So then when setting variables on the configuration I can use script to set the value based on name of the schedule that triggered the running build.
Description
We currently create child configurations to set combinations of build schedules that can't be declared with a single cron expression and set different variable values (like disabling unit tests or enabling coverage reports). In order to keep all the statistics contained in s singular configuration, these child configs have a single step to trigger their parent. (If you still have the last backup I sent you can see for example root/maven/DSBASE_5000_10_0_0/{daily,nightly,weekly}. It would be helpful to declare all the different schedules locally on the config that does the actual build, where each schedule has a name field. So then when setting variables on the configuration I can use script to set the value based on name of the schedule that triggered the running build.