Friday, 2021-04-09

*** GomathiselviS has joined #zuul00:13
*** GomathiselviS has quit IRC00:31
*** y2kenny has quit IRC00:39
*** rlandy|rover|afk is now known as rlandy|rover01:00
*** rlandy|rover has quit IRC01:15
*** hamalq has quit IRC01:32
*** spotz has quit IRC01:36
openstackgerritJames E. Blair proposed zuul/zuul-operator master: WIP: Use kopf operator framework  https://review.opendev.org/c/zuul/zuul-operator/+/78503902:02
*** sam_wan has joined #zuul02:31
*** evrardjp has quit IRC02:33
*** evrardjp has joined #zuul02:33
*** ykarel has joined #zuul03:48
*** bhavikdbavishi has joined #zuul03:55
openstackgerritJames E. Blair proposed zuul/zuul-operator master: WIP: Use kopf operator framework  https://review.opendev.org/c/zuul/zuul-operator/+/78503903:56
*** vishalmanchanda has joined #zuul04:16
*** bhavikdbavishi has quit IRC04:50
*** bhavikdbavishi has joined #zuul05:14
*** bhavikdbavishi has quit IRC05:36
*** bhavikdbavishi has joined #zuul05:37
*** bhavikdbavishi has quit IRC05:43
*** bhavikdbavishi has joined #zuul05:54
*** bhavikdbavishi1 has joined #zuul05:57
*** bhavikdbavishi has quit IRC05:58
*** bhavikdbavishi1 is now known as bhavikdbavishi05:58
*** jcapitao has joined #zuul06:46
*** bhavikdbavishi has quit IRC06:49
openstackgerritTobias Henkel proposed zuul/zuul master: WIP: Save the repo state in the job log dir  https://review.opendev.org/c/zuul/zuul/+/78556207:02
*** bhavikdbavishi has joined #zuul07:32
*** rpittau|afk is now known as rpittau07:33
*** bhavikdbavishi has quit IRC07:37
*** ChanServ has quit IRC07:58
*** ykarel has quit IRC07:58
*** paladox has quit IRC07:58
*** vishalmanchanda has quit IRC07:59
*** iurygregory has quit IRC07:59
*** mugsie has quit IRC07:59
*** cloudnull has quit IRC07:59
*** sduthil has quit IRC07:59
*** johanssone has quit IRC07:59
*** ianw has quit IRC07:59
*** Pilou has quit IRC07:59
*** odyssey4me has quit IRC07:59
*** mordred has quit IRC07:59
*** tristanC has quit IRC07:59
*** parallax has quit IRC07:59
*** donnyd has quit IRC07:59
*** gmann has quit IRC07:59
*** leoluk_ has quit IRC07:59
*** ironfoot has quit IRC07:59
*** mwhahaha has quit IRC07:59
*** erbarr has quit IRC07:59
*** webknjaz has quit IRC07:59
*** iamweswilson has quit IRC07:59
*** persia has quit IRC07:59
*** fdegir has quit IRC07:59
*** Eighth_Doctor has quit IRC07:59
*** Tahvok has quit IRC07:59
*** PrinzElvis has quit IRC07:59
*** avass has quit IRC07:59
*** logan- has quit IRC07:59
*** zbr has quit IRC07:59
*** smyers has quit IRC07:59
*** pleia2 has quit IRC07:59
*** jpena|off has quit IRC07:59
*** ajitha has quit IRC07:59
*** samccann has quit IRC07:59
*** rpittau has quit IRC07:59
*** maxamillion has quit IRC07:59
*** mgagne has quit IRC07:59
*** ofosos has quit IRC07:59
*** clarkb has quit IRC07:59
*** mnasiadka has quit IRC07:59
*** guilhermesp has quit IRC07:59
*** felixedel has quit IRC07:59
*** fungi has quit IRC07:59
*** dcastellani has quit IRC07:59
*** SotK has quit IRC07:59
*** ericsysmin has quit IRC07:59
*** johnsom has quit IRC07:59
*** mnaser has quit IRC07:59
*** melwitt has quit IRC07:59
*** reiterative has quit IRC07:59
*** openstackgerrit has quit IRC07:59
*** bschanzel has quit IRC07:59
*** mgoddard has quit IRC07:59
*** ianychoi has quit IRC07:59
*** icey has quit IRC07:59
*** shanemcd has quit IRC07:59
*** nhicher has quit IRC07:59
*** freefood_ has quit IRC07:59
*** tobberydberg has quit IRC07:59
*** tflink has quit IRC07:59
*** SpamapS has quit IRC07:59
*** pabelanger has quit IRC07:59
*** amotoki has quit IRC07:59
*** guillaumec has quit IRC07:59
*** kgz has quit IRC07:59
*** tobiash has quit IRC07:59
*** lyr has quit IRC07:59
*** aluria has quit IRC07:59
*** arxcruz has quit IRC07:59
*** andreaf has quit IRC07:59
*** jhesketh has quit IRC07:59
*** corvus has quit IRC07:59
*** pots has quit IRC07:59
*** bodgix has quit IRC07:59
*** yoctozepto has quit IRC07:59
*** jonass has quit IRC07:59
*** ttx has quit IRC07:59
*** swest has quit IRC07:59
*** gouthamr has quit IRC07:59
*** sam_wan has quit IRC07:59
*** dpawlik has quit IRC07:59
*** decimuscorvinus has quit IRC07:59
*** bhagyashris has quit IRC07:59
*** jcapitao has quit IRC07:59
*** evrardjp has quit IRC07:59
*** fsvsbs has quit IRC07:59
*** EmilienM has quit IRC07:59
*** mhu has quit IRC07:59
*** Pilou has joined #zuul08:04
*** ianw has joined #zuul08:04
*** johanssone has joined #zuul08:04
*** sduthil has joined #zuul08:04
*** ChanServ has joined #zuul08:04
*** verne.freenode.net sets mode: +o ChanServ08:04
*** vishalmanchanda has joined #zuul08:04
*** iurygregory has joined #zuul08:04
*** mugsie has joined #zuul08:04
*** cloudnull has joined #zuul08:04
*** evrardjp has joined #zuul08:04
*** fsvsbs has joined #zuul08:04
*** mhu has joined #zuul08:04
*** EmilienM has joined #zuul08:04
*** tristanC has joined #zuul08:05
*** parallax has joined #zuul08:05
*** sam_wan has joined #zuul08:05
*** dpawlik has joined #zuul08:05
*** decimuscorvinus has joined #zuul08:05
*** bhagyashris has joined #zuul08:05
*** lyr has joined #zuul08:05
*** aluria has joined #zuul08:05
*** arxcruz has joined #zuul08:05
*** andreaf has joined #zuul08:05
*** jhesketh has joined #zuul08:05
*** corvus has joined #zuul08:05
*** ykarel has joined #zuul08:05
*** paladox has joined #zuul08:05
*** ttx has joined #zuul08:05
*** swest has joined #zuul08:05
*** gouthamr has joined #zuul08:05
*** fdegir has joined #zuul08:06
*** persia has joined #zuul08:06
*** iamweswilson has joined #zuul08:06
*** webknjaz has joined #zuul08:06
*** erbarr has joined #zuul08:06
*** mwhahaha has joined #zuul08:06
*** ironfoot has joined #zuul08:06
*** leoluk_ has joined #zuul08:06
*** donnyd has joined #zuul08:06
*** gmann has joined #zuul08:06
*** PrinzElvis has joined #zuul08:06
*** Tahvok has joined #zuul08:06
*** tobiash has joined #zuul08:06
*** guillaumec has joined #zuul08:06
*** kgz has joined #zuul08:06
*** amotoki has joined #zuul08:06
*** SpamapS has joined #zuul08:06
*** tflink has joined #zuul08:06
*** tobberydberg has joined #zuul08:06
*** pabelanger has joined #zuul08:06
*** freefood_ has joined #zuul08:06
*** bschanzel has joined #zuul08:06
*** mgoddard has joined #zuul08:06
*** ianychoi has joined #zuul08:06
*** icey has joined #zuul08:06
*** shanemcd has joined #zuul08:06
*** nhicher has joined #zuul08:06
*** avass has joined #zuul08:06
*** logan- has joined #zuul08:06
*** zbr has joined #zuul08:06
*** smyers has joined #zuul08:06
*** pleia2 has joined #zuul08:06
*** jpena has joined #zuul08:06
*** ajitha has joined #zuul08:06
*** mgagne has joined #zuul08:06
*** samccann has joined #zuul08:06
*** rpittau has joined #zuul08:06
*** maxamillion has joined #zuul08:06
*** ofosos has joined #zuul08:06
*** mnasiadka has joined #zuul08:06
*** guilhermesp has joined #zuul08:06
*** clarkb has joined #zuul08:06
*** fungi has joined #zuul08:06
*** felixedel has joined #zuul08:06
*** dcastellani has joined #zuul08:06
*** SotK has joined #zuul08:06
*** johnsom has joined #zuul08:06
*** mnaser has joined #zuul08:06
*** melwitt has joined #zuul08:06
*** ericsysmin has joined #zuul08:06
*** holser has joined #zuul08:06
*** reiterative has joined #zuul08:06
*** openstackgerrit has joined #zuul08:06
*** odyssey4me has joined #zuul08:06
*** mwhahaha has quit IRC08:07
*** parallax has quit IRC08:08
*** gouthamr has quit IRC08:08
*** mnasiadka has quit IRC08:08
*** mnasiadka has joined #zuul08:09
*** gouthamr has joined #zuul08:09
*** dcastellani has quit IRC08:09
*** mwhahaha has joined #zuul08:09
*** tosky has joined #zuul08:09
*** dcastellani has joined #zuul08:10
*** parallax has joined #zuul08:13
*** fsvsbs has quit IRC08:15
*** mnasiadka has quit IRC08:20
*** mnasiadka has joined #zuul08:20
*** gouthamr has quit IRC08:20
*** gouthamr has joined #zuul08:20
*** mwhahaha has quit IRC08:20
*** mwhahaha has joined #zuul08:20
*** dcastellani has quit IRC08:20
*** dcastellani has joined #zuul08:20
*** parallax has quit IRC08:20
*** parallax has joined #zuul08:20
*** Eighth_Doctor has joined #zuul08:38
*** pots has joined #zuul08:49
*** bodgix has joined #zuul08:49
*** yoctozepto has joined #zuul08:49
*** jonass has joined #zuul08:49
*** yoctozepto has quit IRC08:50
*** yoctozepto has joined #zuul08:50
*** yoctozepto has quit IRC08:53
*** yoctozepto has joined #zuul08:53
*** mordred has joined #zuul08:54
*** sam_wan has quit IRC08:57
*** ykarel has quit IRC10:44
*** ykarel has joined #zuul10:45
*** ykarel has quit IRC10:47
*** ykarel has joined #zuul10:48
*** ykarel_ has joined #zuul10:56
*** ykarel has quit IRC10:59
*** ykarel_ is now known as ykarel11:17
*** jpena is now known as jpena|lunch11:30
*** rlandy has joined #zuul11:47
*** rlandy is now known as rlandy|rover11:59
*** Goneri has joined #zuul12:05
*** jpena|lunch is now known as jpena12:29
*** lyr has quit IRC12:29
*** lyr has joined #zuul12:29
*** bhavikdbavishi has joined #zuul12:52
*** rlandy|rover is now known as rlandy|rover|mtg13:00
*** jfoufas1 has joined #zuul13:07
*** rpittau is now known as rpittau|bbl13:29
*** rlandy|rover|mtg is now known as rlandy|rover13:47
*** bhavikdbavishi has quit IRC13:50
*** bhavikdbavishi has joined #zuul13:53
corvustobiash: what do you think about https://review.opendev.org/785536 ?  my thoughts are that it looks feasible and reasonable, and we should go ahead and start a -discuss thread.14:13
tobiashcorvus: I've looked at that and I agree14:14
corvustobiash: okay, i'll work on an email later today then, unless you want to14:15
*** bhavikdbavishi has quit IRC14:23
tobiashthanks14:32
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Bump API version to v1alpha2  https://review.opendev.org/c/zuul/zuul-operator/+/78504714:46
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Support externally managed Zookeeper and DB  https://review.opendev.org/c/zuul/zuul-operator/+/78527314:46
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Pass through extra scheduler config options  https://review.opendev.org/c/zuul/zuul-operator/+/78527714:47
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Add merger support  https://review.opendev.org/c/zuul/zuul-operator/+/78527814:47
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Support imagePrefix and versions  https://review.opendev.org/c/zuul/zuul-operator/+/78527914:47
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Support fingergw  https://review.opendev.org/c/zuul/zuul-operator/+/78530014:47
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Add docs  https://review.opendev.org/c/zuul/zuul-operator/+/78508314:47
*** fsvsbs has joined #zuul14:55
*** ykarel is now known as ykarel|away15:07
*** ykarel|away has quit IRC15:13
*** lyr has quit IRC15:26
corvuszuul-maint, swest: fyi i restarted zuul on opendev just now.  i observed the semaphore leak clanup in action (since we leaked them due to the unclean shutdown) -- so that looks good.15:27
*** lyr has joined #zuul15:27
tobiashcool15:27
*** bhavikdbavishi has joined #zuul15:33
*** Goneri has quit IRC15:47
*** evrardjp has quit IRC16:00
*** evrardjp has joined #zuul16:05
*** jfoufas1 has quit IRC16:11
*** bhavikdbavishi has quit IRC16:17
*** bhavikdbavishi has joined #zuul16:52
*** jpena is now known as jpena|off16:58
*** fsvsbs has quit IRC17:05
avasssetting up zuul to gate projects where self approval is necessary is a big hassle right now. So far I tried setting up self approval by having zuul run a job and approve the PR on "/approve" from people in the CODEOWNERS file (thanks mnaser!) but there's still a problem where the bot shows up as "read" access.17:23
mnaseravass: happy that is working for you. I wonder if that ended up landing.17:24
avassso I tried circumventing that by instead of requiring approval from users with write access to the repo to requiring approval and rejecting approvals with read access that isn't the user <bot-name>. However that rejects normal write access approvals now for some reason17:24
avasssince my username != <bot-name> and write access > read access I suppose17:25
avassmnaser: it didn't but it was easy to modify to suit my needs :)17:26
mnaserAh i see. I was hoping it ended up landing upstream and stuff17:30
avassoh and this is specific to github by the way, gerrit has none of these problems. I've been thinking on how to get this working in a better way but the only thing I can think of is adding the ability to construct more sophisticated rules, like the ability to not only "AND" requirements but also "OR" them.17:34
*** spotz has joined #zuul18:41
*** bhavikdbavishi has quit IRC18:51
*** vishalmanchanda has quit IRC18:55
*** ajitha has quit IRC19:04
*** fsvsbs has joined #zuul20:08
*** josefwells has joined #zuul20:28
josefwellsI totally have zuul zuuling things!  I'm using an enterprise gihub instance.  The docs here seem to indicate that the Checks API is not well suited for zuul's concepts: https://zuul-ci.org/docs/zuul/discussion/github-checks-api.html20:29
josefwellsThe example pipeline in the quickstart, however seems to favor the Checks API.  It is not clear to me which way to go, or really how to select one vs. the other.20:30
fungii think the explanation in the design decisions section is just an attempt to square how zuul is treating the checks api with possible user expectations20:31
clarkbfungi: yup exactly. josefwells: basically it is trying to explain to you that the checks api will report the entire pipeline result together rather than as a bunch of independent jobs20:31
clarkbthe reported link will then go to a buildset page on the zuul dashboard which will break things down20:32
fungiit says a lot, but the takeaway is the final sentence in that section, "Each pipeline execution will map to a check-run result reported to Github."20:32
fungiso it's not saying don't use the checks api, just setting expectations for how zuul will interact with it20:32
*** rpittau|bbl is now known as rpittau20:39
josefwellsThanks for the clarification.20:40
josefwellsIt seems like zuul needs a restart to pick up new tenants and projects since zuul.conf specifies the [scheduler] config..  would be nice if it could also be reconfigured on the fly.  As the pipelines and the zuul-config trusted repos20:45
clarkbjosefwells: changes to zuul.conf requires a restart but not to the tenant config20:49
clarkbjosefwells: there is a command to run to reload those configs /me looks20:49
josefwellsso if I edit the main.yaml in /etc/zuul, zuul can pick it up?  is there a web API for that, or from the machine?20:50
clarkbits via a deprecated signal handler or a gearman based command I'm trying to find the docs for it20:51
clarkbjosefwells: https://zuul-ci.org/docs/zuul/discussion/components.html#reconfiguration20:51
corvusjosefwells: 'zuul-scheduler smart-reconfigure'20:52
josefwellsnice.. I can probably set up some automation to do that, then put the tenant config in a git repo20:53
*** sduthil has quit IRC20:53
corvusjosefwells: ++; you can even have a zuul job that runs that :)20:54
corvusclarkb: signal handler is gone as of 4.0 :)20:54
clarkbya after I typed that I figured 4.0 was a likely cleanup for deprecated items :)20:55
josefwellsoh sadpanda, don't want to build on deprecated items.  Restarting scheduler is not a biggie.. I have been keeping a keen eye on the k8s operator stuff, so that is where I hope to have this in production20:57
josefwellsthe new kopf stuff is you right @corvus?20:58
corvusjosefwells: yep20:58
clarkbjosefwells: only the signal handler is deprecated and removed. The command corvus  gave you and as documented in my link are not depreacted20:58
corvusjosefwells: oh, 'zuul-scheduler smart-reconfigure' has been there for ages; you should use that.  yeah what clarkb said :)20:58
josefwellsthe dhall stuff was interesting but I didn't have time to really wrap my brain around it.20:58
josefwellsthanks clarkb20:58
josefwellsSince you experts are around, I'd like to throw out by biggest issue and see what you think zuul can do about it.  In my organization, we have a "main" branch, where most new work goes.  Typically we freeze the code by branching, to say ProductA.   Any changes to ProductA need to go on main, but we don't want main leaking onto ProductA.  Later21:10
josefwellswe might also have ProductB come off ProductA.  Similar story, changes from ProductB need to get to main AND ProductA, But nothing from main or ProductA should get to ProductB.  We accomplish this by testing changes to ProductB in the branch for ProductB, ProductA, and main (Optimistically merged) at the same time.  Not unlike zuul.  Problem is21:10
josefwellsLOTS of people are doing this at the same time, and since we are not doing the zuul trick of testing all of their changes together, we sometimes hit the classic non-conflicting-merge-is-functionally-bad .. hence the need for zuul.21:10
*** josefwells has quit IRC21:10
*** josefwells has joined #zuul21:11
josefwells(In the above example we merge the feature branch to main, then to ProductA, then to ProductB)21:12
clarkbmy first instinct is that you may want to control that a level above zuul. However, you could also have a CI job that compared branches and ensured that there wasn't leakage in the wrong direction21:13
fungijosefwells: i'm not sure i get where the problem is, but one of the things some of our projects do is have jobs which automatically propose ports (essentially cherry-pick) changes from the main branch to other branches in an automated fashion21:13
josefwellsI expected zuul could handle this for exactly tha reason fungi but cherry-pick has shown itself not to work for us, it would need to be merges, so despite being in the same repo, thinking of them as cross-repo is conceptually right.. I think21:14
josefwellsWe generally don't worry too much about the leakage, we have generated git hooks to ensure we don't pull in sha's we don't want, it is more ensuring that the code we do want is tested/merged forward.21:15
josefwellsI think it zuul's gate was configured to test against each branch we would be ok, and I assumed also that zuul would allow me to hold back mergers until all the tests completed (don't want code going into ProductA if it breaks main and can't be merged there).  Does that make sense?21:17
clarkbyup, by default zuul's gate pipeline will mix everything together. I think this would allow you to check in each job that the expect "parent branch" commits are present21:18
clarkbif not you could just fail21:18
clarkbthis means in the gate you'd want dev <- main <- productA and if they enqueued as dev <- productA <- main you would have the productA job fail beacuse inspecting the main branch in its job wouldn't show the expected commit(s)21:19
clarkbthen zuul would reorder to dev <- main and you could reenqueue productA behind main (Zuul doesn't do this last bit automatically though)21:22
josefwellsI'm unclear how to arrange such a gate, are there docs or examples that would lay it out to some degree?21:26
clarkbhttps://zuul-ci.org/docs/zuul/howtos/cross-project-gating.html hrm that is a bit sparse21:30
clarkbessentially you set the same project queue name, https://zuul-ci.org/docs/zuul/reference/project_def.html#attr-project.queue, on all of the projects you want to be gated together21:31
clarkbthen you set up a DependenPipelineManager and they will automatically get enqueued in sequence based on whatever trigger criteria you have set on that pipeline21:32
clarkbhttps://zuul-ci.org/docs/zuul/reference/pipeline_def.html#value-pipeline.manager.dependent for info on the dependent pipeline manager21:33
josefwellsBeautiful, thanks @clarkb!21:41
*** rpittau is now known as rpittau|afk22:04
fungiahh, it sounded like you were asking to have zuul target multiple branches with a single pull request, and not just the branch the pull request was targeted for22:09
*** avass has quit IRC22:13
*** rlandy|rover has quit IRC22:15
josefwells@fungi it is not entierly unlike that.. currently our developers end up only opening one PR and indeed target multiple branches22:18
josefwellsthey are hardware people.. nuff said22:18
*** fsvsbs has quit IRC22:18
openstackgerritJames E. Blair proposed zuul/zuul-operator master: WIP: Use kopf operator framework  https://review.opendev.org/c/zuul/zuul-operator/+/78503922:18
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Bump API version to v1alpha2  https://review.opendev.org/c/zuul/zuul-operator/+/78504722:18
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Support externally managed Zookeeper and DB  https://review.opendev.org/c/zuul/zuul-operator/+/78527322:18
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Pass through extra scheduler config options  https://review.opendev.org/c/zuul/zuul-operator/+/78527722:18
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Add merger support  https://review.opendev.org/c/zuul/zuul-operator/+/78527822:18
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Support imagePrefix and versions  https://review.opendev.org/c/zuul/zuul-operator/+/78527922:18
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Support fingergw  https://review.opendev.org/c/zuul/zuul-operator/+/78530022:18
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Add docs  https://review.opendev.org/c/zuul/zuul-operator/+/78508322:18
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Run a git server in k8s for functional tests  https://review.opendev.org/c/zuul/zuul-operator/+/78573822:18
josefwellsmy team expects that we can nudge them over to opening a PR per target branch if we can show them the magic of zuul.. but those PR's need to be merged all-or-none22:20
corvusjosefwells: circular dependencies may be useful in obtaining an all-or-none behavior across multiple branches22:24
josefwellscorvus: That does look like it would fit the bill.. lots of challenges as mentioned in the proposed docs.. atomicity certainly, but compute is precious around here22:35
*** ajitha has joined #zuul22:51
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Run a git server in k8s for functional tests  https://review.opendev.org/c/zuul/zuul-operator/+/78573823:04
openstackgerritJames E. Blair proposed zuul/zuul-operator master: Upload release images on tag  https://review.opendev.org/c/zuul/zuul-operator/+/78573923:17
corvustristanC: ^ re your comment; how about we land that and then tag/release HEAD (maybe as something like 0.1.0?)23:18
*** tosky has quit IRC23:29
*** josefwells has quit IRC23:53

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!