Talk:News/Toolforge Grid Engine deprecation

This talk page is not a Toolforge support forum. Contact information for Cloud VPS and Toolforge can be found at Help:Cloud Services communication.

Build Service is not ready yet

Help:Toolforge/Build Service indicates that it’s currently in beta. Please first make it production-ready, then give tool maintainers time to migrate to it, and start stopping Grid Engine tools only after that. Kubernetes is good, but not flexible enough to cover all tools. —Tacsipacsi (talk) 20:13, 26 November 2023 (UTC)

Thanks!

The banner is off now.

After our rounds of testing with users, the service is now production-ready.

We are tracking the migration processs under grid-engine-to-k8s-migration on Phabricator.

If you run into any issues, kindly let us know. Komla Sapaty (talk) 15:00, 30 November 2023 (UTC)

Thanks for clarifying the situation! I don’t plan to use the Build Service myself, though (at least for now), as I’ve already rewritten my tool to be compatible with Kubernetes (I didn’t deploy it yet because I still need to find a time when it’s okay to temporarily break it, should I have made a mistake), but I’m sure there are tools that need it. (Maybe even tools I’m a co-maintainer of – I haven’t looked into those yet.) —Tacsipacsi (talk) 15:25, 2 December 2023 (UTC)

Re: the instructions to delete a tool

Hi. In News/Toolforge Grid Engine deprecation#What should I do? the final "delete" link points to an archived phabricator workboard. I wonder if that link should be updated to something else? Or, perhaps the description at that workboard could be made more eye-catching/obvious? (To avoid anyone being confused into adding a task there). Cheers, Quiddity (talk) 20:13, 30 November 2023 (UTC)

Fixed to point to the up-to-date section further down on the page, thanks @Quiddity! Majavah (talk!) 20:21, 30 November 2023 (UTC)