Hi Mark, The cron that you have given will result in this exception - 'org.quartz.SchedulerException: Based on configured schedule, the given trigger will never fire.' That's because you have scheduled the pipeline run to be February 28, 2017. Check out our documentation on timer trigger <https://docs.gocd.io/current/configuration/configuration_reference.html#format> and the quartz scheduler documentation <http://www.quartz-scheduler.org/documentation/quartz-2.x/quick-start#configuration> .
Thanks, Varsha On Thursday, 4 May 2017 18:17:00 UTC+5:30, Mark Scrymgeour wrote: > > Hi, > > I am getting a Go server error when I schedule a one time deployment > pipeline and then remove the CRON timer after this pipeline has completed > its function. > The only way I have managed to remove this error up until now is by > restarting the Go server or re-running the pipeline without the timer which > is not its intended use. > > I am using this pipeline for ad-hoc scheduling of other pipelines. > It seems like the pipeline is trying to re-register with the server after > I have removed the CRON timer from the pipeline configuration. > > I have attached a screenshot of the error and associated config. > > Thanks > Mark > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
