mozilla / mozilla/bugbug

Support a graph of jobs

Open
#6,667 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

hackbot idea
Dominant language
Python
Stars
570
Forks
351
Avg merge
2d 13h
Merged PRs (30d)
65

Description

The platform should support a DAG of jobs triggered by the API run. It can include agentic analysis, actions, and deterministic steps. It can run on the same or multiple machines.

One example is the CI repair workflow:
[Prepare data -> Analyze the failure] -> Notify sheriffs in Slack -> [Generate a fix -> Build locally] -> Run TRY push and wait -> Revise the fix if failed and repeat -> Notify the developer

This one looks linear for now, but we might want to parallelize things later on to reduce latency. Like Run Try push and notify the developer that it's running, and maybe continue some deep review at the same time. This definitely adds quite a bit of complexity, so we can enforce the process to be linear until we run into issues.

There are a few things that might benefit from this:
https://github.com/mozilla/bugbug/issues/6579
https://github.com/mozilla/bugbug/issues/6621
https://github.com/mozilla/bugbug/issues/6623
https://github.com/mozilla/bugbug/issues/6663

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the API run entry point and read the linked issues for the concrete workflows this graph should support. Done means defining a workable job graph that handles the described linear workflow, with room for later parallel execution across one or more machines.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend-api-design, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.