You're right but I look forward when I'll have more versions of chrome to support, more OS versions and maybe other browsers. I don't want to add more and more agents, label and manage them. I want to keep my executors independent of chrome version, a step of my job is to take care of chrome version installation.
On Saturday, April 29, 2017 at 5:54:26 PM UTC+3, Mark Waite wrote: > > I don't understand your hesitation to use dedicated agents to control > concurrency. You can have multiple agents on a single computer, with > different labels on each of the agents, and different numbers of executors > on each agent. > > I think you are expressing that you don't want a single platform to run > more than one version of Chrome at a time. I think you are doing that > because the Chrome version is somehow exclusive to the agent executing it > (for example, you can't run multiple Chrome versions on the same agent > concurrently). If so, then I think that labeling the agent and limiting > the number of executors on the labeled agent is what most closely describes > your environment. > > If you were to add more machines (additional Windows or Mac machines), I > think you would allow Chrome version specific tests to run in parallel, so > long as they were each run on an independent machine. If so, then isn't > the "one job per machine that can run a Chrome test" the preferred model? > > Mark Waite > > On Sat, Apr 29, 2017 at 8:20 AM Johnny Kigel <guy...@gmail.com > <javascript:>> wrote: > >> Hi Mark >> >> Thank you for your quick reply. >> I understand that it can be achieved by labeling my agents, but I want to >> prevent that and have any number of generic agents. >> >> By throtteling concurrent builds, can I assign specific configurations to >> run sequentially? >> >> The problem isn't limiting the number of executors on the agent but >> limiting which configurations can run parallel: >> WinChrome56 *can't *run parallel with WinChrome57 *but* >> WinChrome56 *can* run parallel with MacChrome56 *because* they run on >> different agents. >> >> I don't one to have agent for each Chrome version I test. >> >> >> Thanks again! >> >> On Saturday, April 29, 2017 at 5:02:44 PM UTC+3, Mark Waite wrote: >> >>> If you're using freestyle or multi-configuration jobs, you can control >>> concurrency at the job definition with the Throttle Concurrent Builds >>> plugin >>> <https://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin> >>> >>> (and a stackoverflow article >>> <http://stackoverflow.com/questions/20079051/how-to-put-jobs-in-a-category-for-the-throttle-concurrent-builds-plugin-for-jenk> >>> >>> that further describes it). >>> >>> For all job types, you could control concurrency at the job definition >>> by requiring those jobs only run on an agent with a specific label (for >>> example "chrome-test"), then create an agent with that label on each of the >>> target machines which has only a single executor. With only one executor >>> on that assigned agent, it will run one job at a time. >>> >>> You could control concurrency at the agent by limiting the number of >>> executors on the agent. If there is only one executor on the agent, then >>> it will only run one job. >>> >>> If you're using scripted pipeline, you can control concurrency in your >>> Jenkinsfile by limiting the number of tasks you run in parallel. I assume >>> the same is true for declarative pipeline. >>> >>> Mark Waite >>> >>> On Sat, Apr 29, 2017 at 7:32 AM Johnny Kigel <guy...@gmail.com> wrote: >>> >> Hi, >>>> >>>> I'm testing my browser plugin using Jenkins. >>>> I have 2 virtual machines, each for browser (Chrome for Windows, Chrome >>>> for Mac). >>>> >>>> I test my plugin against the 3 most recent version of chrome. >>>> So my matrix looks like the following: >>>> *Chrome for Mac:* ver 58, ver 57, ver 56 >>>> *Chrome for Windows:* ver 58, ver 57, ver 56 >>>> >>>> My problem is that when I trigger my job, *all 3 versions of Mac begin >>>> to run parallel *and *all 3 versions of Windows begin to run parallel.* >>>> >>>> *I need my execution sequence to look like this:* >>>> 1. Chrome Mac ver 56 - Chrome Windows ver 56 >>>> 2. Chrome Mac ver 57 - Chrome Windows ver 57 >>>> 3. Chrome Mac ver 58 - Chrome Windows ver 58 >>>> >>>> So that at any given moment *single version of chrome for Mac* will be >>>> executed and a *single version of chrome for Windows* will be executed. >>>> >>>> >>>> I would glad for help :) >>>> >>>> Thanks! >>>> >>>> -- >>>> 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-use...@googlegroups.com. >>> >>> >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-users/55bb3665-8dff-49df-bba6-06eeddc6015d%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-users/55bb3665-8dff-49df-bba6-06eeddc6015d%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- >> 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-use...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/f2270ae5-3908-44f2-b661-479a3266e9da%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/f2270ae5-3908-44f2-b661-479a3266e9da%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b9ef77b5-ea0a-46f7-a505-17f0e1151e61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
