Portal:Toolforge/Previous Efforts/Toolforge Build Service/Reports

Toolforge

• Cloud Services overview
• Toolforge user docs

Get started

• Quickstart: set up and get access
• How Toolforge works
• Rules you must follow
• Tutorials

Build and run tools

• Navigate tool accounts and files
• Kubernetes backend
• Build container images for tools
• Run a web service
• Schedule and manage jobs
• Manage tool runtime configuration (envvars)
• Language-specific details:
  • Python
  • Pywikibot
  • Node.js
  • PHP
  • ...more languages/frameworks
• Use Redis for caching
• Index content with Elasticsearch

Access shared storage and databases

• Access shared storage and public wiki dumps
• Access wiki replicas
• Access replica search indices
• Manage tool databases

Share and maintain tools

• Set up version control and code review
• Develop successful tools
• Find and share tools on Toolhub
• Delete a tool
• Contribute to Toolforge

Get help

• How and where to get help
• Troubleshooting

Useful links

• Toolforge admin docs
• List of tools
• Toolforge Admin Console (toolsadmin)

[]

Toolforge Build Service Project

About

Project Overview

Documentation

Reports

Feedback

Reports

Reports include both decision records and progress reports on the implementation of Toolforge Build Service (beta). These reports are intended to keep team members and interested community members updated on progress of the project.

Decision records

Ongoing

• Decision request – Toolforge (re)architecture - Ongoing

Decided

• Decision request - How to allow installing system libraries on buildpack-based images - Decided on 2023-06-08
• Decision request - Find a standard place for all the toolforge-related config files - Decided on 2023-05-26
• Decision request - Toolforge envvars/secrets service - Decided on 2023-05-26
• Decision request - What buildpacks to allow and include for toolforge build service beta - Decided on 2023-03-10
• Decision request - Choose a lang for the toolforge build service API - Decided on 2023-02-23
• Decision request - Toolforge build service to move to an API design - Decided on 2023-02-06
• Pre-create harbor namespaces - Decided on 2022-12-15
• How to manage quotas in Toolforge Build Service - Decided on 2022-05-04

Progress reports

Read the latest sync meeting notes.

2023

• 2023-09-13: Focus on the beta rollout, improve user experience and add metrics to the services
• 2023-08-29: Focus on the second beta rollout, database credentials on envvars and harbor stability
• 2023-08-08: Focus on getting the database credentials on the envvars service to do the second beta rollout

2022

• 2022-09-27: We started working on the Toolforge Build Service [beta] project!

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, the bridged Telegram group, or the bridged Mattermost channel
• 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)