[Jenkins-infra] Headsup: Another safe restart scheduled for jenkins.ci.cloudbees.com

Adam Papai apapai at cloudbees.com
Fri Nov 20 12:39:08 UTC 2015


Nah, it's the slaves not the master. It's not the restarts of the master
but the elimination of the slaves completely. They need to be rotated
sometimes.

On Fri, Nov 20, 2015 at 1:36 PM, Baptiste Mathus <bmathus at batmat.net> wrote:

> I suppose this is a freestyle job?
>
> How about converting it to a workflow one? Because if this is the Jenkins
> restart that mostly bothers you, as workflow can continue where it left off
> after restart, that shouldn't be an issue anymore then?
>
> HTH
>
> 2015-11-20 12:03 GMT+01:00 Adam Papai <apapai at cloudbees.com>:
>
>> For example at Prezi, my main job was to speed up the 1-2hr jobs to run
>> them as fast as we can.
>>
>> So I had a job which parsed all the tests and updated/creaed a matrix
>> configuration job  based on the specific test run-times. We had several
>> thousand tests. Before the whole test suite took 1-2hrs. After this "hack",
>> the test suit took around 90sec.
>>
>> The downside was that sometimes a few jobs were running in a different
>> configuration - based on the previous run time - so they were shifted
>> +1/-1, so I had another job which collected all test results from this
>> matrix job, concatenated all of them into 1 test result and did the report.
>> :)
>>
>> On Fri, Nov 20, 2015 at 11:30 AM, Adam Papai <apapai at cloudbees.com>
>> wrote:
>>
>>> I wanted to ask you guys if it's possible to split this 4+hrs long test
>>> harness job to smaller pieces.
>>>
>>> https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/
>>>
>>> It makes it pretty hard to do maintenance during CET timezone (my
>>> timezone) while there is always a job running. If we could split it up to
>>> smaller pieces, that would be much faster and won't allocate a slave for
>>> 5-6 hrs. Sometimes we need to terminate / replace slaves and usually this
>>> jobs blocks the procedure.
>>>
>>> I could of course just abort the job, but I don't want to do that.
>>>
>>>
>>> On Wed, Nov 18, 2015 at 6:38 PM, R. Tyler Croy <tyler at monkeypox.org>
>>> wrote:
>>>
>>>> I've downloaded some upgraded workflow jobs to fix some little bumps I
>>>> was
>>>> hitting with workflowization of things.
>>>>
>>>> I'm waiting for the acceptance tests to finish, so maybe sometime
>>>> tonight the
>>>> Jenkins instance will restart :P
>>>>
>>>>
>>>> Cheers
>>>> - R. Tyler Croy
>>>>
>>>> ------------------------------------------------------
>>>>      Code: <https://github.com/rtyler>
>>>>   Chatter: <https://twitter.com/agentdero>
>>>>
>>>>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
>>>> ------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Jenkins-infra mailing list
>>>> Jenkins-infra at lists.jenkins-ci.org
>>>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> Jenkins-infra mailing list
>> Jenkins-infra at lists.jenkins-ci.org
>> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>>
>>
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20151120/7a05a907/attachment.html>


More information about the Jenkins-infra mailing list