My apologies if this ticket comes as a surprise to you. In order to ensure WMCS can provide a stable, secure and supported platform, it’s important we migrate away from GridEngine. I want to assure you that while it is WMCS’s intention to shutdown GridEngine as outlined in the blog post https://techblog.wikimedia.org/2022/03/14/toolforge-and-grid-engine/, a shutdown date for GridEngine has not yet been set. The goal of the migration is to migrate as many tools as possible onto kubernetes and ensure as smooth a transition as possible for everyone. Once the majority of tools have migrated, discussion on a shutdown date is more appropriate. See T314664: [infra] Decommission the Grid Engine infrastructure.

As noted in https://techblog.wikimedia.org/2022/03/16/toolforge-gridengine-debian-10-buster-migration/ some use cases are already supported by kubernetes and should be migrated. If your tool can migrate, please do plan a migration. Reach out if you need help or find you are blocked by missing features. Most of all, WMCS is here to support you.

However, it’s possible your tool needs a mixed runtime environment or some other features that aren't yet present in https://techblog.wikimedia.org/2022/03/18/toolforge-jobs-framework/. We’d love to hear of this or any other blocking issues so we can work with you once a migration path is ready. Thanks for your hard work as volunteers and help in this migration!

This is a reminder that the tool for which this ticket is created is still running on the Grid.
The grid is deprecated and all remaining tools need to migrate to Toolforge Kubernetes.

We've sent several emails to maintainers as we continue to make the move away from the Grid.
Many of the issues that have held users back from moving away from the Grid have been addressed in
the latest updates to Build Service. See: https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Changelog

You might find the following resources helpful in migrating your tool:

1. https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service#Migrating_an_existing_tool
2. https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service#Tutorials_for_popular_languages

Don't hesitate to reach out to us using this ticket or via any of our support channels

If you have already migrated this tool, kindly mark this ticket as 'resolved'
To do this, click on the 'Add Action' dropdown above the comment text box, select 'Change Status', then 'Resolved'.
Click 'Submit'

Thank you!

My circumstances (at present) do not allow me to do much non-mobile work (there's a long story but I do not wish to be logged perpetually in phab logs) so if it needs to be shut down, so be it, and if someone has spare time to do that, that's also fine.

@revi I might be able to help, but I would need the tool code to be hosted in a public git repository somewhere (if it's already, can you share the url?)
Thanks!

(Sorry for the long delay in response)

It's been long I've touched anything wrt the bot (it's long been sort of living dead status) but as far as I recall, it is running on (probably slightly modified) https://github.com/mzmcbride/irc-bots 's snitch.py.

I'll probably need to copy and upload the current tc-rc version, but seems like fixing T320006: Migrate revibot from Toolforge GridEngine to Toolforge Kubernetes is more pressing for me, so hold on for some moment.

Hi @revi, I still see a couple of jobs running for this tool on the Grid, they will be stopped tomorrow unless you ask for an extension (tops 1 month), is there anything I can help with that's blocking you or any advice for the tool?

Cheers!