The scheduler has no concept of the environment that's present when the test is running, because it (the scheduler) is not running in the test's environment.
To workaround, you could have a scheduler build run every 5 minutes or so that checked the environment variable and fired off a build if the conditions were correct. On Thu, Sep 4, 2014 at 12:44 PM, Drew Cox <d...@cidercafe.com> wrote: > We would like to schedule builds but have the actual schedule value > externalized in some way, such as read from an environment variable, or > properties file (with the appropriate plugin). However the schedule value > is validated and will not accept "$" env var references. Can anyone > suggest another method to achieve this? > > Thanks > Drew > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Marc MacIntyre -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
