Louis - It sounds like you are trying to bring up multiple services in order to run end-to-end tests. Most people do this via a single agent do everything: - start services - wait for services - run tests - shut down services
I would typically write scripts for managing the services and have go execute the scripts. I believe you will have a hard time trying to co-ordinate multiple agents to do the job. But I might have misunderstood what you are trying to do. On Fri, Jul 1, 2016 at 2:05 AM Zabil C M <[email protected]> wrote: > > How would I go about running a job on multiple agents at the same time? > > https://docs.go.cd/current/advanced_usage/admin_spawn_multiple_jobs.html > > > Would this involve dynamically provisioning the web server and workers? > So, I would have a Go agent setup the web server and workers, and then pass > their IP addresses to the stage that executes tests? > > Yes that's what I meant. > > On Fri, Jul 1, 2016 at 1:46 PM Louis Rose <[email protected]> wrote: > >> Hi Zabil, >> >> Thanks for the quick and helpful reply. Could I ask for a little more >> detail on a couple of your suggestions? >> >> You can run a job on multiple agents but again, they execute the same set >>> of tasks. >> >> >> How would I go about running a job on multiple agents at the same time? >> >> Consider setting up your web server and workers on the first stage and >>> executing of tests on another. >> >> >> Would this involve dynamically provisioning the web server and workers? >> So, I would have a Go agent setup the web server and workers, and then pass >> their IP addresses to the stage that executes tests? >> >> Cheers, >> Louis. >> >> On Friday, 1 July 2016 05:32:15 UTC+1, Zabil C M wrote: >> >>> Hey Louis, >>> >>> You can't do that. >>> >>> The agent picks up the job as a unit while executing the job's tasks. >>> You can run a job on multiple agents but again, they execute the same >>> set of tasks. >>> >>> Consider setting up your web server and workers on the first stage and >>> executing of tests on another. >>> You can also use environments >>> <https://docs.go.cd/current/configuration/managing_environments.html> >>> to group pipelines and agents to make sure that they run only on specific >>> agents. >>> >>> >>> On Fri, Jul 1, 2016 at 1:58 AM Louis Rose <[email protected]> wrote: >>> >> Hi there, >>>> >>>> I'm looking into the feasibility for using Go CD as our new build >>>> server. >>>> >>>> A few of our most rigorous automated acceptance tests require a >>>> multi-machine environment (e.g., a web server box and a worker box >>>> communicating over a message queue). Is it possible for a GoCD job to >>>> acquire more than 1 agent? For example, could our "acceptance test" job >>>> acquire a "web server" agent *and* a "worker" agent at the same time? >>>> >>>> Many thanks, >>>> Louis. >>>> >>>> -- >>>> 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. >>>> >>> -- >> 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. >> > -- > 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. > -- 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.
