Think 2:00am deployments. I guess it could be manually disabled the next day (if one remembers). Doing stuff manually is not what jenkins is all about though. Its like asking why use jenkins and do all the repetitive tasks manually. On Mar 25, 2013 9:53 PM, "Les Mikesell" <lesmikes...@gmail.com> wrote:
> On Mon, Mar 25, 2013 at 8:11 PM, Nathan Overbey <overb...@gmail.com> > wrote: > > I've considered putting it windows task scheduler. Although i prefer to > keep everything in jenkins because i like to source control all my scripts. > The once a year cron syntax sounds ok until a production install gts > accidently rolled back to a one year old version. That woudnt be good. > > I guess I don't understand the scenario. Why does the one-off build > need to be scheduled as opposed to run 'now', and why can't you > disable it at some convenient time after the cron-syntax schedule runs > the 1st time? And if source control is involved, why not make the > job poll the SCM so it will only build if there have been changes on > the target path (branch?) since the last build? > > -- > Les Mikesell > lesmikes...@gmail.com > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/LPXPx_ftQZ0/unsubscribe?hl=en > . > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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/groups/opt_out.
