| @pernordeman:matrix.org | Hi! | 08:47 |
|---|---|---|
| Does anyone know if its possible to set a dynamic job scope for projects/pipelines or if its possible to add arguments to a pipeline trigger in Gerrit. | ||
| For example posting to gerrit: | ||
| check [A.py, B.py, C.py] | ||
| which will only run these three jobs. | ||
| @pernordeman:matrix.org | * Hi! | 08:48 |
| Does anyone know if its possible to set a dynamic job scope for projects/pipelines or if its possible to add arguments to a pipeline trigger in Gerrit. | ||
| For example posting to gerrit: | ||
| `check \[A.py, B.py, C.py\]` | ||
| which will only run these three jobs. | ||
| @pernordeman:matrix.org | * Hi! | 08:48 |
| Does anyone know if its possible to set a dynamic job scope for projects/pipelines or if its possible to add arguments to a pipeline trigger in Gerrit. | ||
| For example posting to gerrit: | ||
| `check [A.py, B.py, C.py]` | ||
| which will only run these three jobs. | ||
| @carlozermo:matrix.org | Hi guys, I would like to build the original Dockerfile, but why are the oc client and skopeo being downloaded? Are they needed for Zuul if I'm in a Kubernetes cluster? Do you think it's possible to remove them? | 08:54 |
| @mnaser:matrix.org | I believe they are used in two different things: | 10:23 |
| - oc client acting as a kubectl replacement but that can also talk to normal k8s client for k8s pods as “workers” | ||
| - skopeo is used for some promotion jobs if you’re using speculative images to make it available in Zuul-executor | ||
| I believe if you don’t care about these you can strip that. | ||
| @sp-bmilanov:matrix.org | hi everyone, is it possible to configure reporters per-project inside a connection? I have a connection with projects I don't want my Zuul to vote. One workaround I image is splitting the connection into two, carry over the projects I do not want to report to into one of them, and disable reporters for that connection | 10:38 |
| @carlozermo:matrix.org | Ok, thanks a lot for your answer mnaser | 10:39 |
| @sp-bmilanov:matrix.org | * hi everyone, is it possible to configure reporters per-project inside a connection? I have a connection where I don't want my Zuul to vote on some of the projects. One workaround I image is splitting the connection into two, carry over the projects I do not want to report to into one of them, and disable reporters for that connection | 10:40 |
| @fungicide:matrix.org | > <@sp-bmilanov:matrix.org> hi everyone, is it possible to configure reporters per-project inside a connection? I have a connection where I don't want my Zuul to vote on some of the projects. One workaround I image is splitting the connection into two, carry over the projects I do not want to report to into one of them, and disable reporters for that connection | 16:29 |
| is there a reason you need them to be in a pipeline? zuul's only going to run jobs for events events on projects that are added to pipelines | ||
| -@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 914161: Add buildset event db table https://review.opendev.org/c/zuul/zuul/+/914161 | 16:29 | |
| @fungicide:matrix.org | > <@sp-bmilanov:matrix.org> hi everyone, is it possible to configure reporters per-project inside a connection? I have a connection where I don't want my Zuul to vote on some of the projects. One workaround I image is splitting the connection into two, carry over the projects I do not want to report to into one of them, and disable reporters for that connection | 16:29 |
| * is there a reason you need them to be in a pipeline? zuul's only going to run jobs for events on projects that are added to pipelines | ||
| @fungicide:matrix.org | in opendev, some projects get "retired" by being removed from the tenant config. we've observed that remaining jobs in other projects where the definition lists the removed project as a `required-projects` entry, whether directly or through inheritance, are not added to the in-memory configuration when reconfiguration occurs (an entry for them is correctly added to the config-errors list of course). when this happens, those broken jobs are ignored in any pipelines where they were added. the upshot of this is that project maintainers get surprised when a removal they were unaware of that appears in some lengthy `required-projects` list used by a parent of most of their jobs leads to changes only running the remaining jobs (in a case that came up yesterday, one project was only running its documentation build jobs in the gate pipeline). aside from the obvious ("don't do that," or "try to make sure you clean up all references before removing"), could we make zuul more robust in such situations? keep those broken jobs in the pipeline but insta-fail them? always report configuration errors on changes and refuse to enqueue them? ignore `required-projects` entries that refer to unknown projects and try to run the job anyway? | 17:56 |
| @fungicide:matrix.org | for now i'm advising folks to just be more careful, announce removals well in advance, and try to keep a close eye on changes to the config-errors list any time a project gets removed from the tenant | 17:58 |
| @fungicide:matrix.org | just wondering 1. whether that's the intended behavior for nonexistent `required-projects` and 2. if another behavior might make more sense (perhaps as a tenant config option in order to preserve backward compatibility) | 18:01 |
| @sp-bmilanov:matrix.org | fungi: this is for a third-party Cinder CI, I would like to inherit jobs from opendev (devstack, tempest, etc).. but even if I only include jobs from a project, a change in an upstream nodeset, for example, would make my Zuul report on upstream of a configuration error (nodeset <new nodeset> was not found). And if I understand correctly, `pipeline.config-error` will also apply for all connections, so again not what I am looking for | 18:56 |
| -@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 916141: Support negated regexes in files/irrelevant-files https://review.opendev.org/c/zuul/zuul/+/916141 | 21:14 | |
| -@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 916142: Ignore /COMMIT_MSG in files matchers even more https://review.opendev.org/c/zuul/zuul/+/916142 | 21:16 | |
| -@gerrit:opendev.org- Zuul merged on behalf of James E. Blair https://matrix.to/#/@jim:acmegating.com: [zuul/zuul] 916684: Gitlab: make change.files persistent https://review.opendev.org/c/zuul/zuul/+/916684 | 21:29 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!