Taskgraph init should generate configs that are compatible with org level grants
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start with the taskgraph init entry point and compare its generated configuration with the linked org-scope-test changes. Determine how org-level grants and an optional trust project should be represented in the user's context, then verify that fresh taskgraph init configurations work with both supported org setups.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
We set up some basic scopes for any repo in an org, with the intent of helping folks get setup with TC as quickly as possible. I was playing around with this and realized the index routes and caches we use by default in taskgraph init aren't compatible with this setup. Seeing as both the org level repos and taskgraph init are aimed at making things easy for newcomers, we should make sure these two features work together out of the box.
Here's what I had to change starting from a fresh taskgraph init:
https://github.com/mozilla-releng/org-scope-test/compare/7b8ace554506cba9ea199b490c7b44cce017871d..60add700bd573a8e822a384ba18a40942661c725
This will depend on the org (only mozilla and mozilla-releng are supported atm), and will be different if a trust project is specified. As taskgraph init will have no way of knowing how things are configured in fxci-config, we'll need some context provided by the user on whether the configuration has a trust project defined or not (perhaps it should default to not?)
- 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 ·