Jump to content


From Wikitech

In this page you will find a list of smaller user-facing updates to toolforge services, new small features and similar news.


Increased the default quota for deployments from 3 to 16 (this affects continuous jobs and webservices)
Added --port to continuous jobs to allow backend services in a single tool (docs to come soon)
Added a --health-check-script to toolforge jobs run --continuous to specify a script to run to test the health of your continuous job and restart it when unhealthy (learn more)
Added toolforge jobs dump subcommand to generate a yaml file you can use toolforge jobs load with the current jobs (learn more)
Grid engine is turned off, kubernetes is now the only runtime available.
Toolforge jobs using buildservice images can explicitly use now filelog as regular jobs toolforge jobs run --filelog ...
Webservices now include a tcp health probe by default, and allow to configure an http probe with the --health-check-path option, for example --health-check-path /healthz.
The build service will now alert users when starting a new build and not having much quota left (and add some followup options).
Fixed support for envvars on lighthttp (php7.4, etc.) based k8s images
Apt buildpack dependency resolution improved and broken link fixes rolled out
Support for clojure has been restored, it was dropped from upstream and got removed it with the latest builder upgrade.
Updated the builder image to heroku/builder:22 latest, with 2.6.1 nodejs buildpack supporting pnpm install
Now new envvars values can be passed through stdin or hidden prompt.


Added support for Rust tools to the build service.
Added the toolforge build clean subcommand to allow freeing quota for the build service.
The --wait argument of the jobs framework now supports specifying a custom timeout.
Added support for dotnet/mono stack for the build service.
Added support to specify build environment variables to the toolforge build command (toolforge build start --envvar MYVAR=myvalue --envvar MYVAR2=myvalue2 https://url/to/my/repo.git).
Created the My first Buildpack static tool tutorial.
Added a note in the My first Buildpack PHP tool on how to serve the index.php from a subdirectory.
Added the `toolforge build quota` subcommand to check how much resources you are using (working on a way to release them if needed).
The build service now supports following build logs (as tail -f would) and it's enabled by default when starting a build.
There is now a custom Pywikibot image available.
The build service now supports canceling jobs.
The jobs framework now supports running build service images without NFS storage mounted.
New toolforge changelog page for small updates created! :)
The build service now supports building static assets with nodejs while having any other language for the service (python/ruby/...).

Communication and support

Support and administration of the WMCS resources is provided by the Wikimedia Foundation Cloud Services team and Wikimedia movement volunteers. Please reach out with questions and join the conversation:

Discuss and receive general support
Stay aware of critical changes and plans
Track work tasks and report bugs

Use a subproject of the #Cloud-Services Phabricator project to track confirmed bug reports and feature requests about the Cloud Services infrastructure itself

Read stories and WMCS blog posts

Read the Cloud Services Blog (for the broader Wikimedia movement, see the Wikimedia Technical Blog)