Provide support in generic worker payload builder for docker worker properties
@petemoore ya está trabajando en esto.
Desde el 7/5/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Taskgraph has worker-implementation-specific payload builders to convert abstract job definitions into taskcluster tasks. Payload builders declare a schema for the job properties they support. Jobs designed for Docker Worker contain properties that are currently not allowed by the Generic Worker payload builder, such as docker-image, allow-ptrace etc.
The d2g tool demonstrates that it is possible to transform a Docker Worker task definition into an equivalent Generic Worker task definition, and soon Generic Worker will perform this translation internally when running Docker Worker task payloads. However, task definitions designed for Docker Worker will not be able to use features that exist in Generic Worker only. Therefore it would be beneficial for the Generic Worker payload builder to support Docker Worker job definitions natively, and directly generate Generic Worker payloads that do not need to run through d2g inside of Generic Worker.
The d2g source code and command line utility can be used as a reference for understanding how to support Docker Worker features under Generic Worker. Furthermore, to validate that the updated payload builder works as anticipated, tests can be written that generate Docker Worker payloads from job definitions, transform them to Generic Worker using d2g, and compare the results to the same input job processed directly with the Generic Worker payload builder. The two should ideally be identical.
Note, the advantage of doing this, rather than having a transform step that runs d2g after generating a Docker Worker payload, is that eventually we can remove the Docker Worker payload builder altogether, and reduce the code footprint and complexity of dealing with multiple payload formats.
- Lenguaje dominante
- Python
- Estrellas
- 26
- Forks
- 55
- Merge medio
- 2 d 6 min
- PR fusionados (30 d)
- 15
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de taskcluster/taskgraph
-
Dependency Dashboard Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
taskcluster/taskgraph#952 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
taskcluster/taskgraph#915 ·
-
feature
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
taskcluster/taskgraph#911 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
taskcluster/taskgraph#882 ·
-
Further optimize Git clones Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
taskcluster/taskgraph#865 · 1 comentario ·
Todos los issues de taskcluster/taskgraph
Issues similares
-
essnmx good first issue
Dificultad 1/5 Menos de una hora Aptitud para principiantes 95/100
-
[Feature] 奇物选择添加优先级 Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
syfoud/Simulated_Scepter#174 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Giskard-AI/giskard-oss#2840 · 1 comentario ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Abiertoarea: repo bug perceived difficulty: 2
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
yeti-platform/yeti#1380 ·