<div dir="ltr">Yeah I'm happy to analyse the job and the tests and write something useful.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 20, 2015 at 3:34 PM, R. Tyler Croy <span dir="ltr"><<a href="mailto:tyler@monkeypox.org" target="_blank">tyler@monkeypox.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">(replies inline)<br>
<span class=""><br>
On Fri, 20 Nov 2015, Adam Papai wrote:<br>
<br>
> Nah, it's the slaves not the master. It's not the restarts of the master<br>
> but the elimination of the slaves completely. They need to be rotated<br>
> sometimes.<br>
<br>
<br>
</span>Are you volunteering to help split it up? :)<br>
<br>
I'm 100% confident that it can be broken up (zomg workflow) but it's a question<br>
of time and effort really<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
> On Fri, Nov 20, 2015 at 1:36 PM, Baptiste Mathus <<a href="mailto:bmathus@batmat.net">bmathus@batmat.net</a>> wrote:<br>
><br>
> > I suppose this is a freestyle job?<br>
> ><br>
> > How about converting it to a workflow one? Because if this is the Jenkins<br>
> > restart that mostly bothers you, as workflow can continue where it left off<br>
> > after restart, that shouldn't be an issue anymore then?<br>
> ><br>
> > HTH<br>
> ><br>
> > 2015-11-20 12:03 GMT+01:00 Adam Papai <<a href="mailto:apapai@cloudbees.com">apapai@cloudbees.com</a>>:<br>
> ><br>
> >> For example at Prezi, my main job was to speed up the 1-2hr jobs to run<br>
> >> them as fast as we can.<br>
> >><br>
> >> So I had a job which parsed all the tests and updated/creaed a matrix<br>
> >> configuration job based on the specific test run-times. We had several<br>
> >> thousand tests. Before the whole test suite took 1-2hrs. After this "hack",<br>
> >> the test suit took around 90sec.<br>
> >><br>
> >> The downside was that sometimes a few jobs were running in a different<br>
> >> configuration - based on the previous run time - so they were shifted<br>
> >> +1/-1, so I had another job which collected all test results from this<br>
> >> matrix job, concatenated all of them into 1 test result and did the report.<br>
> >> :)<br>
> >><br>
> >> On Fri, Nov 20, 2015 at 11:30 AM, Adam Papai <<a href="mailto:apapai@cloudbees.com">apapai@cloudbees.com</a>><br>
> >> wrote:<br>
> >><br>
> >>> I wanted to ask you guys if it's possible to split this 4+hrs long test<br>
> >>> harness job to smaller pieces.<br>
> >>><br>
> >>> <a href="https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/" rel="noreferrer" target="_blank">https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/</a><br>
> >>><br>
> >>> It makes it pretty hard to do maintenance during CET timezone (my<br>
> >>> timezone) while there is always a job running. If we could split it up to<br>
> >>> smaller pieces, that would be much faster and won't allocate a slave for<br>
> >>> 5-6 hrs. Sometimes we need to terminate / replace slaves and usually this<br>
> >>> jobs blocks the procedure.<br>
> >>><br>
> >>> I could of course just abort the job, but I don't want to do that.<br>
> >>><br>
> >>><br>
> >>> On Wed, Nov 18, 2015 at 6:38 PM, R. Tyler Croy <<a href="mailto:tyler@monkeypox.org">tyler@monkeypox.org</a>><br>
> >>> wrote:<br>
> >>><br>
> >>>> I've downloaded some upgraded workflow jobs to fix some little bumps I<br>
> >>>> was<br>
> >>>> hitting with workflowization of things.<br>
> >>>><br>
> >>>> I'm waiting for the acceptance tests to finish, so maybe sometime<br>
> >>>> tonight the<br>
> >>>> Jenkins instance will restart :P<br>
> >>>><br>
> >>>><br>
> >>>> Cheers<br>
> >>>> - R. Tyler Croy<br>
> >>>><br>
> >>>> ------------------------------------------------------<br>
> >>>> Code: <<a href="https://github.com/rtyler" rel="noreferrer" target="_blank">https://github.com/rtyler</a>><br>
> >>>> Chatter: <<a href="https://twitter.com/agentdero" rel="noreferrer" target="_blank">https://twitter.com/agentdero</a>><br>
> >>>><br>
> >>>> % gpg --keyserver <a href="http://keys.gnupg.net" rel="noreferrer" target="_blank">keys.gnupg.net</a> --recv-key 3F51E16F<br>
> >>>> ------------------------------------------------------<br>
> >>>><br>
> >>>> _______________________________________________<br>
> >>>> Jenkins-infra mailing list<br>
> >>>> <a href="mailto:Jenkins-infra@lists.jenkins-ci.org">Jenkins-infra@lists.jenkins-ci.org</a><br>
> >>>> <a href="http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra" rel="noreferrer" target="_blank">http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra</a><br>
> >>>><br>
> >>>><br>
> >>><br>
> >><br>
> >> _______________________________________________<br>
> >> Jenkins-infra mailing list<br>
> >> <a href="mailto:Jenkins-infra@lists.jenkins-ci.org">Jenkins-infra@lists.jenkins-ci.org</a><br>
> >> <a href="http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra" rel="noreferrer" target="_blank">http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra</a><br>
> >><br>
> >><br>
> ><br>
> ><br>
> > --<br>
> > Baptiste <Batmat> MATHUS - <a href="http://batmat.net" rel="noreferrer" target="_blank">http://batmat.net</a><br>
> > Sauvez un arbre,<br>
> > Mangez un castor !<br>
> ><br>
<br>
- R. Tyler Croy<br>
<br>
------------------------------------------------------<br>
Code: <<a href="https://github.com/rtyler" rel="noreferrer" target="_blank">https://github.com/rtyler</a>><br>
Chatter: <<a href="https://twitter.com/agentdero" rel="noreferrer" target="_blank">https://twitter.com/agentdero</a>><br>
<br>
% gpg --keyserver <a href="http://keys.gnupg.net" rel="noreferrer" target="_blank">keys.gnupg.net</a> --recv-key 3F51E16F<br>
------------------------------------------------------<br>
</div></div></blockquote></div><br></div>