Portal:Toolforge/Changelog
Appearance
In this page you will find a list of smaller user-facing updates to Toolforge services, new small features and similar news. Major changes are announced at News and/or the cloud-announce@ mailing list.
2024
- 2024-11-25
- Added three global environment variables with the Elasticsearch, Redis and Toolforge API URLs. (see Help:Toolforge/Envvars and the global envvars definitions)
- 2024-11-14
- Changed
toolforge webservice
to output warning if there are any unknown keys in theservice.template
file. - 2024-09-20
- Added
--replicas
to continuous jobs to allow for running multiple job instances/processes. (learn more) - 2024-08-05
- Announced the global availability of the Toolforge API.
- 2024-07-11
- Rolled out toolforge-jobs 16.0.13 that can run inside buildservice containers. This is the first step towards being able to run the clients inside k8s.
- 2024-06-11
- Increased the default quota for Deployments (continuous jobs and webservices) from 3 to 16.
- 2024-05-30
- Added
--port
to continuous jobs to allow backend services in a single tool (learn more) - 2024-04-03
- Added a
--health-check-script
totoolforge jobs run --continuous
to specify a script to run that will ceck the health of a continuous job and restart it when unhealthy. (learn more) - Added
toolforge jobs dump
subcommand to generate a YAML file with the current jobs that can be usedtoolforge jobs load
. (learn more) - 2024-03-14
- Turned off the Grid Engine. Kubernetes is now the only runtime available.
- 2024-03-07
- Added support for jobs using buildservice images to enable file logging with
toolforge jobs run --filelog ...
- 2024-02-28
- Added a TCP health check probe to webservices by default. Added support for configuring an HTTP probe with the
--health-check-path
option (for example--health-check-path /healthz
). - 2024-02-13
- Change the build service to users when starting a new build without having much quota left (and added some followup options).
- 2024-01-31
- Fixed support for envvars on lighthttp (php7.4, etc.) based k8s images
- Improved Apt buildpack dependency resolution and rolled out broken link fixes.
- 2024-01-11
- Restored support for clojure, which was dropped from upstream and got removed it with the latest builder upgrade.
- 2024-01-05
- Updated the builder image to heroku/builder:22 latest, with 2.6.1 nodejs buildpack supporting pnpm install
- 2024-01-04
- Added support for passing envvars through stdin or hidden prompt.
2023
- 2023-12-19
- Added support for Rust tools to the build service.
- 2023-12-15
- Added the
toolforge build clean
subcommand to allow freeing quota for the build service. - 2023-12-13
- 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.
- 2023-12-12
- Added a note in the My first Buildpack PHP tool on how to serve the
index.php
from a subdirectory. - 2023-12-08
- Added the `toolforge build quota` subcommand to check how much resources you are using (working on a way to release them if needed).
- 2023-12-04
- Added support for following build logs (as
tail -f
would) with the build service, which is enabled by default when starting a build. - 2023-11-17
- Added a Pywikibot image for running Pywikibot scripts.
- 2023-10-19
- Added support for canceling jobs in the build service.
- 2023-10-12
- Added support running build service images without NFS storage mounted using the jobs framework.
- 2023-10-11
- Created this Toolforge changelog page for small updates! :)
- 2023-10-05
- Added support for supports building static assets with NodeJS while having any other language for the service (Python/Ruby/...) in the build service.
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
- Chat in real time in the IRC channel #wikimedia-cloud connect or the bridged Telegram group
- Discuss via email after you have subscribed to the cloud@ mailing list
Stay aware of critical changes and plans
- Subscribe to the cloud-announce@ mailing list (all messages are also mirrored to the cloud@ list)
- Read the News wiki page
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)