Re: [Wikitech-l] [Engineering] Long running tasks/scripts now included on [[wikitech:Deployments]]

What Alex said. This is for one off type things. -- Sent from my phone, please excuse brevity. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Engineering] Long running tasks/scripts now included on [[wikitech:Deployments]]

Let me clarify the reasoning for the idea: We realized that some schema changes (which used to be scheduled like other deployments) no longer take 1 hour (they can take 1 month, running continuously like https://phabricator.wikimedia.org/T139090 , because it affects 3 of our largest tables).

Re: [Wikitech-l] [Engineering] Long running tasks/scripts now included on [[wikitech:Deployments]]

I assumed the same, but better be explicit about those assumption :) On Thu, Sep 22, 2016 at 4:27 PM, Alex Monk wrote: > I had been assuming that puppetised crons were not really relevant... > > On 22 September 2016 at 15:19, Guillaume Lederrey >

Re: [Wikitech-l] [Engineering] Long running tasks/scripts now included on [[wikitech:Deployments]]

Hello! Increasing visibility sounds like a great idea! How far do we want to go in that direction? In particular, I'm thinking of a few of the crons we have for Cirrus. For example, we do have daily crons on terbium that re-generate the suggester indices. Those can run for > 1h. My understanding

Re: [Wikitech-l] [Engineering] Long running tasks/scripts now included on [[wikitech:Deployments]]

> How far ahead of time must entries be added? I trust most people's best judgement here :) But, as soon as you have an idea of when you'll do it is the best time to do it. Obviously if the task will impact others and/or require no other deploys at the same time that should be scheduled further