Page MenuHomePhabricator
Create Task
Maniphest T362051

[components-api] First iteration of the component API
Closed, ResolvedPublic
Actions

Description

Original doc: https://docs.google.com/document/d/1y7cIX3oiqOH8hEuPhSEuqWx-yElxTq9Ga8qJRvqAJjY/edit
Current working doc: https://docs.google.com/document/d/116eZZcEPpm-YCV25qjK3Iv8LFj2OBA4wkwYMTeJcYWo/edit#heading=h.uhbe07clzg9n

This is an epic task to keep track of all the subtasks needed for a first iteration of the Toolforge Component API.

After this iteration, the user should be able to:

  • Define build configuration and trigger the build with one or more triggers (TBD) in a yaml file and persist it in toolforge
  • Define any kind of job (webservice included) in that yaml file that will be created/restarted when depolyed (toolforge deploy)
  • Redeploy automatically components (jobs) when their images are built by a trigger
  • Specify the dependencies between the jobs to deploy in a specific order
  • Specify ports to expose to other components defined in the yaml (internal services)

This will be open only as 'preview' for users.

Potential example:

$ cat mytool.yaml
config-version: 0.1

metadata:
 name: Toolhunt
 description: A web application for editing Toolhub records in a fun and easy way.
 version: v1.0.0

components:
 toolhunt-ui:
   description: a vue.js frontend
   type: webservice
   build:
     repository: https://github.com/wikimedia/toolhunt-ui
     triggers:
       - webhook
   wait-for:
      - toolhunt-api

 toolhunt-api:
   description: a python-flask api
   type: continuous
   build:
     repository: https://github.com/wikimedia/toolhunt
   run:
     port: 5000

 toolhunt-flower:
   description: dashboard for monitoring and managing celery
   type: continuous
   build:
     reuse-from: toolhunt-api
   run:
     port: 5555
     command: flower
   wait-for:
      - toolhunt-api


$ toolforge deploy mytool.yaml  # or toolforge component deploy mytool.yaml if we don't have a single cli yet
Starting deploy for toolhunt v1.0.0...
Building images:
   [✅] toolhunt-ui
   [✅] toolhunt-api
Deploying components:
   [✅] toolhunt-api
   [✅] toolhunt-ui (waiting for toolhunt-api)
   [✅] toolhunt-flower (waiting for toolhunt-api)
All components deployed



$ toolforge status  # very speculative, might be toolforge components status if we don't have a single cli yet
Current components:  # similar to `toolforge jobs list` with deployment info
---------------------------------------------------------------------------
name            status     build-id         deploy time  ports   type
---------------------------------------------------------------------------
toolhunt-ui     RUNNING    build-id-12345   12:15:00     -       webservice
toolhunt-api    RUNNING    build-id-12344   12:12:00     5000    continuous
toolhunt-flower ERROR      build-id-12344   12:12:00     5555    continuous


Last triggered builds:  # similar to `toolforge build list` with deployment info
   2024-04-04 12:11:00 UTC  OK  build-id-12345   toolhunt-ui    triggerd by webhook   some more information
   2024-04-04 12:00:00 UTC  OK  build-id-12344   toolhunt-api   triggerd manually    some more information


Last deployments:
   toolhunt-ui
      2024-04-04 12:15:00 UT build-id-12345 Current
      2024-03-02 12:00:00 UT build-id-12342 OK

   toolhunt-api
      2024-04-04 12:15:00 UT build-id-12344 Current
      2024-03-02 12:00:00 UT build-id-12222 FAILED

   toolhunt-flower (image: toolhunt-api)
      2024-04-04 12:15:00 UT build-id-12344 Current
      2024-03-02 12:00:00 UT build-id-12322 OK

The details on how that configuration file looks like and the command line interface are to be defined.

Direct subtasks:

  1. T362070: [components-api] Get a minimal version of the config with build-only data
  2. T362069: [components-api] Get a skeleton of API webservice and implement `/tool/<toolname>/deploy` with single continuous job deployment only
  3. T362066: [components-api] Develop the webhook mechanism to trigger a deployment
  4. T362075: [components-api] add order to the components deployment
  5. T348755: [jobs-api,webservice] Run webservices via the jobs framework
  6. T362077: [components-api] Add webservice support
  7. T362072: [components-api] Add support for port/healthcheck for continuous jobs in tool config/depolyment
  8. T362076: [components-api] Add support for pre-built images (ex. python3.11, to refine)
  9. T362071: [components-api] Add source polling build trigger

Related Objects
Search...

StatusSubtypeAssignedTask
 ResolvedLucasWerkmeisterT320140 Migrate wd-shex-infer from Toolforge GridEngine to Toolforge Kubernetes
 ResolvedmatmarexT319707 Migrate dtcheck from Toolforge GridEngine to Toolforge Kubernetes
 ResolvedLegoktmT320062 Migrate steve-adder from Toolforge GridEngine to Toolforge Kubernetes
 ResolvedLegoktmT320011 Migrate rfa-voting-history from Toolforge GridEngine to Toolforge Kubernetes
 In ProgressdcaroT194332 [builds-api,components-api,webservice,jobs-api] Make Toolforge a proper platform as a service with push-to-deploy and build packs
 ResolveddcaroT393564 [Hypothesis] WE6.3.10 start a beta for the push-to-deploy features
 ResolveddcaroT386829 [components-api] Rename the CRDs groups to be `components-api.toolforge.org`
 ResolvedRaymond_NdibeT389044 [components-api,buildsa-api] When building and deploying, if none of the settings changed, the jobs are not restarted
 ResolveddcaroT389043 [builds-api] Store the commit hash that was used for the build
 OpenNoneT314729 [jobs-cli,components-api] Provide YAML schema file for toolforge-jobs definition files
 ResolvedRaymond_NdibeT394273 [components-api] add tool config version check
 ResolveddcaroT394280 [components-api] Add admin documentation page
 ResolveddcaroT394279 [components-api,components-cli] add user documentation page
 ResolvedRaymond_NdibeT394276 [components-api] Add basic prometheus metrics
 ResolvedRaymond_NdibeT394275 [components-api] Add alerts and runbooks for basic service health
 Resolved• ChuckonwumeluT394277 [components-cli,components-api, toolforge-weld] Add a warning message saying it's 'beta'
 Duplicate• ChuckonwumeluT395911 [components-cli] Add the beta warning to CLI outputs
 ResolvedtaaviT397718 [components-cli] Deploy to tools
 ResolveddcaroT394337 [components-api] deploy on tools
 ResolveddcaroT397724 [components-api] Provide a standalone version of tool config schema
 ResolvedFeaturedcaroT398485 [components-api,beta] CI pipelines should wait until Toolforge deployment is 100% successful
 ResolveddcaroT398623 [components-api,api-gateway] allow getting a deployment status using the deployment token
 OpenNoneT398497 [components-api,beta] Generated configs should contain cpu values as numbers, not strings
 OpenNoneT401851 [components-api,beta] Image should only be build once when re-used in components
 ResolvedDamianZarembaT401893 [components-api] Allow reusing another component build
 OpenNoneT401894 [builds-api] Allow queuing builds
 StalledRaymond_NdibeT402568 [components-api] Queue builds when the build queue is full
 OpenBUG REPORTNoneT401868 [components-api,beta] Config not updated from remote source
 OpendcaroT402764 [components-api] allow specifying `source_repo`+`ref` for the config
 In ProgresskomlaT368600 [KR] WE6.3 Introduce a sustainability scoring system for the Toolforge platform
 ResolveddcaroT375199 [Hypothesis] WE6.3.4 If we enable the automatic deployment of a minimal tool, we will be able to evaluate the end to end flow and set the groundwork for adding support for more complex tools and deployment flows.
 ResolveddcaroT362051 [components-api] First iteration of the component API
 ResolveddcaroT362066 [components-api] Develop the webhook mechanism to trigger a deployment
 OpendcaroT362071 [components-api] Add source polling build trigger
 ResolvedRaymond_NdibeT362072 [components-api] Add support for port/healthcheck for continuous jobs in tool config/depolyment
 ResolveddcaroT362076 [components-api] Add support for pre-built images (ex. python3.11, to refine)
 OpendcaroT362075 [components-api] add order to the components deployment
 ResolveddcaroT362224 Decision request - What to use for toolforge components api task execution
 OpendcaroT362077 [components-api] Add webservice support
 In ProgressFeatureRaymond_NdibeT348755 [jobs-api,webservice] Run webservices via the jobs framework
 ResolvedFeatureRaymond_NdibeT341066 [jobs-api,jobs-cli] Support multiple replicas of continuous jobs
 ResolvedFeatureRaymond_NdibeT348758 [jobs-api,jobs-cli] Support services in jobs
 OpenRaymond_NdibeT359804 [jobs-api] Refactor before webservice support
 ResolveddcaroT359806 [jobs-api] Remove flask-restful
 ResolvedRaymond_NdibeT359808 [jobs-api] Split the API, core, and storage and runtime modules
 In ProgressRaymond_NdibeT359650 [jobs-api] Create storage layer, and save business models in persistent storage
 OpenRaymond_NdibeT358815 [jobs-api] separate jobs-framework k8s object templates from code
 ResolvedRaymond_NdibeT390135 [jobs-api] Split the core layer and create the core models
 DeclinedNoneT360016 [jobs-api,buildservice-api,envvars-api] evaluate crossplane for composite objects creation and maintenance
 ResolvedRaymond_NdibeT385904 [jobs-api] move jobs.toolforge.org/* labels to annotations
 ResolvedRaymond_NdibeT390136 [jobs-api] Split the `*Job` API models into three
 ResolvedRaymond_NdibeT390137 [jobs-api] Introduce deprecation metrics
 OpenRaymond_NdibeT390138 [jobs-api] Generate the openapi definition from the code
 ResolvedtaaviT401113 [jobs-api] Migrate to FastAPI
 ResolvedRaymond_NdibeT362520 [maintain-kubeusers] Increment default services quota
 In ProgressRaymond_NdibeT359649 [jobs-api,infra] upgrade all the existing toolforge jobs to the latest job version
 OpenNoneT311917 [webservice,toolforge-cli] Make `webservice shell` a standalone tool
 ResolvedFeatureRaymond_NdibeT362621 Support HTTP health checks in jobs framework
 ResolvedFeatureRaymond_NdibeT335592 [jobs-api,jobs-cli] Support job health checks
 InvalidRaymond_NdibeT388088 [jobs-api] add -l|--last to toolforge jobs logs ...
 InvalidRaymond_NdibeT388090 [jobs-api] jobs-api should be able to read webservices started with toolforge webservice
 DuplicateRaymond_NdibeT388091 [jobs-api] add toolforge jobs shell feature
 In ProgressRaymond_NdibeT388092 [jobs-api] expose jobs-api continuous jobs to the internet via `toolname.toolforge.org`, just like webservice
 InvalidRaymond_NdibeT392717 [jobs-api] check for diff in services when running diff_with_running_job
 OpenRaymond_NdibeT409728 [image-config] deprecate and move all data to builds-api
 OpenRaymond_NdibeT409725 [jobs-api,webservice] Fetch images from builds-api
 OpenRaymond_NdibeT409726 [builds-api] Add an endpoint to get all available images
 In ProgressRaymond_NdibeT409727 [builds-api,harbor,image-config] Move pre-built images to harbor
 DuplicateRaymond_NdibeT409900 [jobs-api,image-config] Deprecate/update the list of supported pre-built images
 In ProgressRaymond_NdibeT415322 Replace job image variants with webservice image variants
 ResolvedRaymond_NdibeT409191 [jobs-api] Investigate if we can reuse the 'web' flavour pre-built images as regular images
 ResolveddcaroT362082 [components-api] Add minimal cli with build-only features
 ResolvedSlst2020T362069 [components-api] Get a skeleton of API webservice and implement `/tool/<toolname>/deploy` with single continuous job deployment only
 ResolveddcaroT362070 [components-api] Get a minimal version of the config with build-only data
 ResolvedSlst2020T363346 [jobs-api, jobs-cli] Prefix all endpoints with `/tool/<toolname>`
 ResolvedSlst2020T363808 [builds-api, builds-cli] Prefix all endpoints with `/tool/<toolname>`
 ResolveddcaroT368909 [toolforge,replica_cnf] Use tool-prefixed urls for envvars
 ResolvedSlst2020T363809 [envvars-api, envvars-cli] Prefix all endpoints with `/tool/<toolname>`
 OpenNoneT363983 [toolforge] Investigate authentication
 Resolved• aborreroT365681 toolforge: kubernetes can't revoke certificates
 ResolveddcaroT367179 [api-gateway] Move authentication from the APIs
 ResolveddcaroT367180 [jobs-api] Remove authentication and use the api-gateway provided headers
 ResolveddcaroT367181 [envvars-api] Remove authentication and use api-gateway provided headers
 ResolveddcaroT367182 [builds-api] Remove authentication and use the api-gateway provided headers
 InvaliddcaroT379053 [components-api] Use an asynchronous toolforge client to interact with toolforge
 ResolveddcaroT379092 [components-api] Add functional tests for the components api
 ResolvedSlst2020T379091 [components-cli] Create cli with subcommand
 ResolveddcaroT384203 [components-cli,lima-kilo] deploy compontents-cli on lima-kilo by default
 ResolvedSlst2020T379093 [components-api] Add endpoint to delete a deployment
 ResolveddcaroT380283 [components-api] Limit the amount of deployments to (say) 25
 ResolveddcaroT384634 [components-api] Trigger builds on every deploy
 ResolveddcaroT388830 [components-api] use the component name for the image instead of the default tool
 ResolveddcaroT388706 [builds-api] Limit the amount of running builds
 ResolvedNoneT388644 [components-api] allow stopping a deployment that's running
 ResolveddcaroT388643 [components-api] restrict running deployments to 1

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
dcaro triaged this task as High priority.Apr 8 2024, 10:12 AM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 8 2024, 10:12 AM
dcaro updated the task description. (Show Details)Apr 8 2024, 12:30 PM
dcaro added a subtask: T348755: [jobs-api,webservice] Run webservices via the jobs framework.Apr 8 2024, 12:32 PM
dcaro renamed this task from [component] First iteration of the component API to [component-api] First iteration of the component API.Apr 8 2024, 12:47 PM
dcaro updated the task description. (Show Details)Apr 8 2024, 1:21 PM
Slst2020 subscribed.Apr 8 2024, 2:03 PM
• aborrero added a project: User-aborrero.Apr 8 2024, 2:41 PM
fnegri updated the task description. (Show Details)Apr 9 2024, 4:03 PM
fnegri subscribed.Apr 9 2024, 4:18 PM

@dcaro I edited the description of this task to reflect what we discussed in the Toolforge Monthly Meeting.

It's somewhat duplicating the information in the Phabricator Task Graph, but I think listing the main sub-tasks in the task description is more readable. In the task graph, it's hard to see which tasks are the top-level subtasks (there's an icon in the first column, but you still have the noise of all the other tasks in between).

I hope this helps, but feel free to undo my change and explore different ways to organize things.

dcaro added a comment.Apr 9 2024, 4:30 PM
In T362051#9701785, @fnegri wrote:

@dcaro I edited the description of this task to reflect what we discussed in the Toolforge Monthly Meeting.

It's somewhat duplicating the information in the Phabricator Task Graph, but I think listing the main sub-tasks in the task description is more readable. In the task graph, it's hard to see which tasks are the top-level subtasks (there's an icon in the first column, but you still have the noise of all the other tasks in between).

I hope this helps, but feel free to undo my change and explore different ways to organize things.

Thanks, I agree that is more readable, but it's harder to maintain xd

dcaro updated the task description. (Show Details)Apr 10 2024, 9:09 AM
dcaro updated the task description. (Show Details)Apr 10 2024, 9:13 AM
dcaro updated the task description. (Show Details)Apr 10 2024, 12:52 PM
• aborrero moved this task from Backlog to Radar/observer on the User-aborrero board.Apr 11 2024, 9:08 AM
dcaro renamed this task from [component-api] First iteration of the component API to [components-api] First iteration of the component API.Apr 16 2024, 12:28 PM
Raymond_Ndibe subscribed.May 16 2024, 7:33 PM
• joanna_borun subscribed.May 30 2024, 7:54 AM
dcaro added a parent task: T194332: [builds-api,components-api,webservice,jobs-api] Make Toolforge a proper platform as a service with push-to-deploy and build packs.Jul 3 2024, 8:58 AM
• joanna_borun added a project: cloud-services-team (FY2024/2025-Q1-Q2).Jul 22 2024, 10:09 AM
dcaro added a parent task: T375199: [Hypothesis] WE6.3.4 If we enable the automatic deployment of a minimal tool, we will be able to evaluate the end to end flow and set the groundwork for adding support for more complex tools and deployment flows..Sep 19 2024, 2:03 PM
dcaro mentioned this in T375199: [Hypothesis] WE6.3.4 If we enable the automatic deployment of a minimal tool, we will be able to evaluate the end to end flow and set the groundwork for adding support for more complex tools and deployment flows..Sep 19 2024, 2:08 PM
dcaro updated the task description. (Show Details)Sep 19 2024, 2:36 PM
dcaro changed the task status from Open to In Progress.Oct 8 2024, 8:38 AM
dcaro moved this task from Ready to be worked on to Toolforge iteration 15 on the Toolforge board.
dcaro edited projects, added Toolforge (Toolforge iteration 15); removed Toolforge.
dcaro moved this task from Next Up to In Progress on the Toolforge (Toolforge iteration 15) board.
dcaro changed the status of subtask T362066: [components-api] Develop the webhook mechanism to trigger a deployment from Open to In Progress.Oct 9 2024, 4:52 PM
dcaro edited projects, added Toolforge (Toolforge iteration 16); removed Toolforge (Toolforge iteration 15).Oct 15 2024, 7:33 AM
dcaro moved this task from Next Up to In Progress on the Toolforge (Toolforge iteration 16) board.
dcaro changed the status of subtask T362076: [components-api] Add support for pre-built images (ex. python3.11, to refine) from Open to In Progress.Nov 5 2024, 9:55 AM
dcaro added a subtask: T379053: [components-api] Use an asynchronous toolforge client to interact with toolforge.Nov 5 2024, 10:39 AM
dcaro removed a subtask: T379091: [components-cli] Create cli with subcommand.Nov 5 2024, 4:17 PM
dcaro changed the status of subtask T379053: [components-api] Use an asynchronous toolforge client to interact with toolforge from Open to In Progress.Nov 5 2024, 4:27 PM
dcaro closed subtask T362076: [components-api] Add support for pre-built images (ex. python3.11, to refine) as Resolved.Nov 6 2024, 10:20 AM
dcaro closed subtask T379053: [components-api] Use an asynchronous toolforge client to interact with toolforge as Resolved.Nov 7 2024, 11:30 AM
dcaro changed the status of subtask T379053: [components-api] Use an asynchronous toolforge client to interact with toolforge from Resolved to Invalid.
Slst2020 changed the status of subtask T379093: [components-api] Add endpoint to delete a deployment from Open to In Progress.Nov 7 2024, 12:54 PM
CodeReviewBot added a project: Patch-For-Review.Nov 7 2024, 1:47 PM

dcaro opened https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/583

enable components in gateway

CodeReviewBot added a comment.Nov 7 2024, 1:48 PM

dcaro updated https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/583

enable components in gateway

Maintenance_bot removed a project: Patch-For-Review.Nov 7 2024, 2:31 PM
CodeReviewBot added a comment.Nov 7 2024, 3:04 PM

dcaro merged https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/583

enable components in gateway

dcaro closed subtask T362066: [components-api] Develop the webhook mechanism to trigger a deployment as Resolved.Nov 8 2024, 12:57 PM
Slst2020 closed subtask T379093: [components-api] Add endpoint to delete a deployment as Resolved.Nov 12 2024, 1:50 PM
dcaro added a subtask: T380283: [components-api] Limit the amount of deployments to (say) 25.Nov 19 2024, 3:23 PM
dcaro changed the status of subtask T380283: [components-api] Limit the amount of deployments to (say) 25 from Open to In Progress.Nov 20 2024, 12:57 PM
dcaro closed subtask T380283: [components-api] Limit the amount of deployments to (say) 25 as Resolved.Nov 25 2024, 9:31 AM
Slst2020 changed the status of subtask T379092: [components-api] Add functional tests for the components api from Open to In Progress.Dec 2 2024, 9:43 AM
dcaro edited projects, added Toolforge (Toolforge iteration 17); removed Toolforge (Toolforge iteration 16).Jan 8 2025, 12:49 PM
dcaro moved this task from Next Up to In Progress on the Toolforge (Toolforge iteration 17) board.
fnegri moved this task from Backlog to In progress on the cloud-services-team (FY2024/2025-Q1-Q2) board.Jan 13 2025, 4:28 PM
fnegri edited projects, added cloud-services-team (FY2024/2025-Q3-Q4); removed cloud-services-team (FY2024/2025-Q1-Q2).Jan 14 2025, 2:36 PM
fnegri moved this task from Backlog to In progress on the cloud-services-team (FY2024/2025-Q3-Q4) board.
dcaro closed subtask T362082: [components-api] Add minimal cli with build-only features as Resolved.Jan 15 2025, 2:29 PM
dcaro closed subtask T379092: [components-api] Add functional tests for the components api as Resolved.Jan 22 2025, 6:29 PM
dcaro edited projects, added Toolforge (Toolforge iteration 18); removed Toolforge (Toolforge iteration 17).Feb 25 2025, 3:29 PM
dcaro moved this task from Next Up to In Progress on the Toolforge (Toolforge iteration 18) board.
dcaro changed the status of subtask T384634: [components-api] Trigger builds on every deploy from Open to In Progress.Feb 26 2025, 2:27 PM
Raymond_Ndibe changed the status of subtask T348755: [jobs-api,webservice] Run webservices via the jobs framework from Open to In Progress.Mar 13 2025, 2:51 PM
dcaro added a subtask: T388830: [components-api] use the component name for the image instead of the default tool.Mar 13 2025, 6:41 PM
dcaro added a subtask: T388706: [builds-api] Limit the amount of running builds.
dcaro added a subtask: T388644: [components-api] allow stopping a deployment that's running.
dcaro added a subtask: T388643: [components-api] restrict running deployments to 1.
dcaro closed subtask T384634: [components-api] Trigger builds on every deploy as Resolved.
dcaro edited projects, added Toolforge (Toolforge iteration 19); removed Toolforge (Toolforge iteration 18).Mar 18 2025, 3:56 PM
dcaro moved this task from Next Up to In Progress on the Toolforge (Toolforge iteration 19) board.
dcaro changed the status of subtask T388643: [components-api] restrict running deployments to 1 from Open to In Progress.Mar 24 2025, 5:27 PM
dcaro changed the status of subtask T388706: [builds-api] Limit the amount of running builds from Open to In Progress.Mar 24 2025, 6:57 PM
dcaro changed the status of subtask T388830: [components-api] use the component name for the image instead of the default tool from Open to In Progress.Mar 25 2025, 11:32 AM
dcaro closed subtask T388643: [components-api] restrict running deployments to 1 as Resolved.
Raymond_Ndibe closed subtask T388706: [builds-api] Limit the amount of running builds as Resolved.Apr 8 2025, 3:20 AM
Raymond_Ndibe closed subtask T388830: [components-api] use the component name for the image instead of the default tool as Resolved.Apr 8 2025, 2:20 PM
dcaro edited projects, added Toolforge (Toolforge iteration 20); removed Toolforge (Toolforge iteration 19).May 14 2025, 2:30 PM
dcaro moved this task from Next Up to In Progress on the Toolforge (Toolforge iteration 20) board.
dcaro changed the status of subtask T362072: [components-api] Add support for port/healthcheck for continuous jobs in tool config/depolyment from Open to In Progress.May 20 2025, 9:38 AM
dcaro edited projects, added Toolforge (Toolforge iteration 21); removed Toolforge (Toolforge iteration 20).Jun 11 2025, 10:38 AM
dcaro moved this task from Next Up to In Progress on the Toolforge (Toolforge iteration 21) board.
dcaro closed subtask T362072: [components-api] Add support for port/healthcheck for continuous jobs in tool config/depolyment as Resolved.Jun 16 2025, 1:06 PM
dcaro changed the status of subtask T388644: [components-api] allow stopping a deployment that's running from Duplicate to Resolved.Jun 30 2025, 9:51 AM
dcaro closed this task as Resolved.Jun 30 2025, 4:11 PM

This task is not useful anymore, I'll close (the subtasks are still useful, it just makes no sense anymore to address them as 'first iteration').

dcaro moved this task from In Progress to Done on the Toolforge (Toolforge iteration 21) board.Jul 3 2025, 10:51 AM
Raymond_Ndibe changed the status of subtask T348755: [jobs-api,webservice] Run webservices via the jobs framework from In Progress to Stalled.Jul 15 2025, 11:30 AM
fnegri moved this task from In progress to Done on the cloud-services-team (FY2024/2025-Q3-Q4) board.Jul 15 2025, 1:09 PM
fnegri changed the status of subtask T348755: [jobs-api,webservice] Run webservices via the jobs framework from Stalled to Open.Jan 13 2026, 4:51 PM
Raymond_Ndibe changed the status of subtask T348755: [jobs-api,webservice] Run webservices via the jobs framework from Open to In Progress.Tue, Jan 27, 10:19 PM
Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits