Jump to content

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

Phabricator project: #tbs
From Wikitech
For user documentation, see Help:Toolforge/Build Service. This page contains planning documents used by the Wikimedia Cloud Services team when the build services was being developed.

Toolforge Build Service Project

Project Overview

Status:    Unresolved

Phabricator board.

This project is currently developing its beta stage. The goal for this stage is to develop a beta version of Toolforge Build Service that allows users to build an image (using a buildpack) from the CLI and deploy it on Toolforge so they can see the website running the new code.

Project organization

The project is currently being led by the Wikimedia Cloud Services team and welcomes technical contributors!

The team is working in two-week iterations, with pre-selected tasks that are estimated depending on the complexity, effort, and time they might take. Iterations can be tracked on the Toolforge Build Service Phabricator board.

Current iteration: Iteration 18

Success criteria

  • The project enables the deprecation of GridEngine.
  • There is a positive uptake by the technical contributors, which means any/all of below:
    • It is utilized as a recommended path for new projects.
    • Users use it
    • It’s perceived as an option for newcomers that is easier than the existing system.


Milestone Status
Finalize build CLI Yes Done
Set up harbor Yes Done
Complete security testing Yes Done
Automate the periodic creation of harbor namespaces Yes Done
Allow web services to deploy images from harbor Yes Done
Create documentation for users In progress
Open the beta for the users In progress
Gather feedback from the users from the beta version In progress

Beta user stories

Main beta task

These user stories come from a working document that was also open for technical contributors to comment and review on. The document is read-only now, as all its information has been moved to Phabricator tasks.

Note that some user stories have been implemented already, and related tasks that had a 'resolved' status before the definition of the user stories are not shown here. Current tasks related to user stories and future ones will be added here or in the next phase of the project. User stories are being resolved in parallel and are not necessarily linear. The following is a summary of the user stories that can be tracked on Phabricator:

How to read user stories

User stories help facilitate expectations and communication within the team and to the users. Each user story for Toolforge Build Service is accompanied by a "When do we know it's done?" section that helps list the different scenarios that have to be taken into account in order to elaborate the consequent subtasks the team will be working on to accomplish them.

Future milestones

Planning for future steps on this project will be defined upon the completion of the previous milestones. A working document with some thoughts on new user stories can be read.

  • Build Service API

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)