If you turn material updates *off*, this is the expected behaviour because you've told the polling subsystem not to check this material for updates unless you manually "trigger with latest".
You probably need to leave autoUpdate turned *on* for the material and make the *first* stage a manual approval stage to get the behaviour you want using https://github.com/gocd-contrib/gocd-groovy-dsl-config-plugin/blob/6d754dfb7628f1d52e16c4e3a03c73b594fd3f31/dsl/src/main/java/cd/go/contrib/plugins/configrepo/groovy/dsl/Stage.java#L65-L72 On Thu, Mar 23, 2023 at 1:35 PM 'Alexey Savchkov' via go-cd < [email protected]> wrote: > I have a long-running set of nightly tests which I want to trigger only on > schedule during non-working hours. I have set up the following material > using the Groovy configuration plugin > materials { > git('my-repo') { > url = '[email protected]:mygroup/myrepo.git' > branch = 'mybranch' > destination = 'dest' > autoUpdate = false > } > } > with the intention that regular daily commits won't trigger the pipeline > but it will be triggered by timer in the night and pick up all the changes > which have accumulated so far, > However I see that when the pipeline starts by timer it doesn't recognise > that new commits are present and runs on some old commit. > The server log looks like this > 2023-03-23 05:04:00,001 INFO [DefaultQuartzScheduler_Worker-4] > TimedBuild:67 - Timer scheduling pipeline 'NightlyTests-Dev' using spec '0 > */2 * * * ? *' > 2023-03-23 05:04:00,720 INFO [goThreadPoolTaskScheduler-4] > ScheduleService:158 - [Pipeline Schedule] Scheduling pipeline > NightlyTests-Dev with build cause [ManualForcedBuildCause: Forced by timer] > 2023-03-23 05:04:00,730 INFO [goThreadPoolTaskScheduler-4] > PipelineRepository:78 - Start updating pipeline timeline > 2023-03-23 05:04:00,734 INFO [goThreadPoolTaskScheduler-4] > PipelineRepository:84 - Pipeline timeline updated > 2023-03-23 05:04:06,678 INFO [109@MessageListener for WorkFinder] > BuildAssignmentService:190 - [Agent Assignment] Assigned job > [JobIdentifier[NightlyTests-Dev, 26, 26, Build, 1, Postgres-14, 17323]] to > agent [Agent [linux-agent-3, 10.5.50.74, > 9254d4f7-55a2-486e-bfff-847ed8d49041]] > and so on. > > Is is not assumed that a timer-triggered pipeline should update its > materials before running? > > GoCD server version: 23.1.0 > (16079-21e78c998e1eb35d8d489c1d3e3e9813dc18233a) > GoCD Agent version: 22.3.0-15301 > > Thanks a lot. > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/go-cd/57bf6593-14b4-47ef-a1ea-5118b1e7695en%40googlegroups.com > <https://groups.google.com/d/msgid/go-cd/57bf6593-14b4-47ef-a1ea-5118b1e7695en%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAA1RwH9j-dDYqAm3F9%2Bv%2BT4jsotKVE1M5m5W7e9XRpDfV4FsZg%40mail.gmail.com.
