Hi, I'm just wondering if there's an option to start/trigger a pipeline from the go agent on demand at certain time, but still be able to trigger pipelines automatically on each commit/trigger? Or there is something else you are doing for running long running tests (in my situation - behave tests)? Usually running tests (selenium or others) last for ~10 min which is acceptable for running each time before deploying to development server, but behave tests run around 30 mins or more and it's not acceptable to run every time a commit is made.
So I've been thinking about running tests only at certain time, once (or maybe every N hours daily). Do you have any advice if not a solution for the question? How I'm supposed to run longer running tests but still be able to deploy to development in acceptable time frame? I don't know much about behave tests and if they can speed up. Sorry if the question/theme is too broad, but we are using GO-CD in our firm and really like the tool. Hope to use it further and properly. Kind regards, Matija -- 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.
