| -@gerrit:opendev.org- Doug Goldstein proposed: [zuul/zuul-jobs] 935030: add roles to install helm-docs https://review.opendev.org/c/zuul/zuul-jobs/+/935030 | 01:50 | |
| -@gerrit:opendev.org- Mohammed Naser proposed: [zuul/zuul-jobs] 935168: Add buildset registry image override https://review.opendev.org/c/zuul/zuul-jobs/+/935168 | 15:59 | |
| @mnaser:matrix.org | appreciate a quick eye on this simple change, docker limits have been destroying us :) | 16:00 |
|---|---|---|
| @clarkb:matrix.org | mnaser: the image is actually canonically hosted on quay now which shouldn't limit. Maybe we just fix the location bug and see if that addresses it? | 16:02 |
| @mnaser:matrix.org | Clark: i can change the default but i probably see value in being able to validate it i guess | 16:02 |
| @mnaser:matrix.org | * Clark: i can change the default but i probably see value in being able to override it | 16:02 |
| -@gerrit:opendev.org- Mohammed Naser proposed: [zuul/zuul-jobs] 935168: Add buildset registry image override https://review.opendev.org/c/zuul/zuul-jobs/+/935168 | 16:03 | |
| @clarkb:matrix.org | I guess if you want to run a different registry or cache it locally. I just want to call out that docker hub and it's limits shouldn't be involv re d | 16:03 |
| @clarkb:matrix.org | * I guess if you want to run a different registry or cache it locally. I just want to call out that docker hub and it's limits shouldn't be involved | 16:03 |
| @mnaser:matrix.org | yeah anything but dockerhub :) so i updated the patch to point to quay.io but still overridable | 16:04 |
| @jim:acmegating.com | mnaser: needs a fix | 16:04 |
| -@gerrit:opendev.org- Mohammed Naser proposed: [zuul/zuul-jobs] 935168: Add buildset registry image override https://review.opendev.org/c/zuul/zuul-jobs/+/935168 | 16:04 | |
| @mnaser:matrix.org | > <@jim:acmegating.com> mnaser: needs a fix | 16:04 |
| sorry, quick assumption from my side - done! | ||
| @mnaser:matrix.org | you know what | 16:05 |
| -@gerrit:opendev.org- Mohammed Naser proposed on behalf of Tobias Henkel: [zuul/zuul-jobs] 849989: Allow overriding the buildset registry image https://review.opendev.org/c/zuul/zuul-jobs/+/849989 | 16:06 | |
| -@gerrit:opendev.org- Mohammed Naser proposed on behalf of Tobias Henkel: [zuul/zuul-jobs] 849989: Allow overriding the buildset registry image https://review.opendev.org/c/zuul/zuul-jobs/+/849989 | 16:07 | |
| @mnaser:matrix.org | corvus: if i can retake your +2 into tobias original patch https://review.opendev.org/c/zuul/zuul-jobs/+/849989 with a doc change and added quay into it :) | 16:07 |
| @bennetefx:matrix.org | Subject: Promote Pipeline for GitHub in Zuul | 16:08 |
| Hello Zuul Community, | ||
| I’ve implemented promote pipelines with both Gerrit and GitLab, but I noticed the documentation doesn’t cover this feature for GitHub. Is there a way to implement a promote pipeline for GitHub in Zuul? Any guidance or suggestions would be greatly appreciated. | ||
| Thank you! | ||
| @clarkb:matrix.org | mnaser: corvus I +2'd and rechecked because the microk8s k8s check job failed. Not sure if that is a persistent issue but it appeared to fail running k8s workload rather than just installing k8s at least | 16:53 |
| @clarkb:matrix.org | > <@bennetefx:matrix.org> Subject: Promote Pipeline for GitHub in Zuul | 16:55 |
| > | ||
| > Hello Zuul Community, | ||
| > | ||
| > I’ve implemented promote pipelines with both Gerrit and GitLab, but I noticed the documentation doesn’t cover this feature for GitHub. Is there a way to implement a promote pipeline for GitHub in Zuul? Any guidance or suggestions would be greatly appreciated. | ||
| > | ||
| > Thank you! | ||
| A promote pipeline is a more generic concept and should be able to be applied to various code review systems. I would expect that you just need to map the trigger mechanisms from one system to another. And even then those may differ between teams if they have slightly different needs or use the code review systems differently. Can you be more specific about what you think is missing from a github perspective? | ||
| @bennetefx:matrix.org | > <@clarkb:matrix.org> A promote pipeline is a more generic concept and should be able to be applied to various code review systems. I would expect that you just need to map the trigger mechanisms from one system to another. And even then those may differ between teams if they have slightly different needs or use the code review systems differently. Can you be more specific about what you think is missing from a github perspective? | 17:15 |
| Thank you very much for your response—I really appreciate the guidance! | ||
| I apologize if my question was unclear. I’ll look into different trigger combinations in GitHub to see if I can set up the promote pipeline behavior I’m hoping for. If I find that I need more specific help, I’ll make sure to refine my question to be more focused. | ||
| Thank you again for your patience and support—it’s a big help as I work to understand this better! | ||
| @clarkb:matrix.org | You're welcome. FWIW we use Gerrit so I don't have any GitHub examples to share or I would. But also it should be possible if you can map the triggers for the pipeline between the systems | 17:38 |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 935221: Speed download of image artifacts in launcher https://review.opendev.org/c/zuul/zuul/+/935221 | 19:55 | |
| -@gerrit:opendev.org- James E. Blair https://matrix.to/#/@jim:acmegating.com proposed: [zuul/zuul] 935221: Speed download of image artifacts in launcher https://review.opendev.org/c/zuul/zuul/+/935221 | 23:44 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!