I too use bash files (see
https://github.com/PersianWikipedia/fawikibot/tree/master/HujiBot/grid/jobs)
and am planning to move them from grid to k8s in the next few weeks. I have
found the process well-documented and am hoping for the transition to be
easy, like Amir said.
Since at least two
I recently migrated most of pywikibot jobs from grid engine to k8s and to
my surprise, it was actually quite easy. I have lots of tasks (been running
bots since 2008). So much that it showed redaction in the total number of
jobs in SGE.
One thing that helped me that I collapsed everything into a
On 2/16/22 17:34, Russell Blau wrote:
Also, it is not possible to load Pywikibot in the tf-python39 runtime because a
required module (requests, fromhttps://python-requests.org) is not available.
What is the process for requesting (no pun intended) that this (or any other
resource) be added
I can see already that trying to migrate to this new toolforge-jobs framework
is going to be a long and winding road.
First of all, the documentation on "choosing the execution runtime" leaves much
to be desired. There is a list of 23 available runtimes to choose from, but no
guidance on how
From my perspective of a Toolforge user, one of the issues I see is that it's
often not clear how to map the "friendly command line interface" into concepts
I already understand about the lower level tools.
For example, the webservice script does some useful stuff. But, it wasn't
clear
On 2/15/22 21:46, Maarten Dammers wrote:
Hi,
Why are we upgrading to Buster instead of Bullseye? According to
https://wikitech.wikimedia.org/wiki/Operating_system_upgrade_policy
Buster will be end of life around August this year.
So we're either stuck with an older version for a while or we
Hi,
Why are we upgrading to Buster instead of Bullseye? According to
https://wikitech.wikimedia.org/wiki/Operating_system_upgrade_policy
Buster will be end of life around August this year.
So we're either stuck with an older version for a while or we have to do
this whole exercise again much
