Friday, 2020-04-17

*** cdearborn has quit IRC00:28
*** jamesmcarthur has joined #zuul01:01
*** ysandeep|away is now known as ysandeep01:03
ianwi feel like a builder-only nodepool configuration doesn't actually need labels: ?  only the launchers?01:12
*** swest has quit IRC01:15
clarkbianw: I think we only build imagesif nodepool sees labels use them01:18
clarkbwhich us why we have that stub like config there01:18
ianwhrm, i wonder if the config validator should ensure diskimages have labels then01:19
ianw| centos-8-arm64-0000000001       | centos-8-arm64       | nb03        | qcow2         | ready    | 00:00:16:31 |01:20
*** jamesmcarthur has quit IRC01:24
*** swest has joined #zuul01:32
*** sugaar has quit IRC01:55
*** sugaar has joined #zuul01:56
*** Goneri has quit IRC01:59
*** Pilou has joined #zuul02:07
*** ysandeep is now known as ysandeep|afk02:21
openstackgerritMerged zuul/zuul-jobs master: fetch-subunit-output test: use ensure-pip  https://review.opendev.org/71822502:42
*** igordc has joined #zuul02:46
*** igordc has quit IRC02:52
*** igordc has joined #zuul02:52
openstackgerritMerged zuul/zuul-jobs master: ensure-tox: use ensure-pip role  https://review.opendev.org/71766302:55
*** igordc has quit IRC02:57
*** jamesmcarthur has joined #zuul03:24
*** bhavikdbavishi has joined #zuul03:25
*** bhavikdbavishi1 has joined #zuul03:28
*** bhavikdbavishi has quit IRC03:30
*** bhavikdbavishi1 is now known as bhavikdbavishi03:30
*** ysandeep|afk is now known as ysandeep04:22
*** evrardjp has quit IRC04:37
*** evrardjp has joined #zuul04:37
*** ysandeep is now known as ysandeep|reboot04:49
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Update Fedora to 31  https://review.opendev.org/71765704:51
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Make ubuntu-plain jobs voting  https://review.opendev.org/71970104:51
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Document output variables  https://review.opendev.org/71970404:51
openstackgerritIan Wienand proposed zuul/zuul-jobs master: Python roles: misc doc updates  https://review.opendev.org/72011104:51
*** ysandeep|reboot is now known as ysandeep04:53
*** swest has quit IRC05:00
*** swest has joined #zuul05:00
*** zxiiro has quit IRC05:10
*** mnasiadka has quit IRC05:10
*** adam_g has quit IRC05:10
*** zxiiro has joined #zuul05:15
*** mnasiadka has joined #zuul05:15
*** adam_g has joined #zuul05:15
*** jamesmcarthur has quit IRC05:30
*** jamesmcarthur has joined #zuul05:30
*** sgw has quit IRC05:41
*** ysandeep is now known as ysandeep|brb05:49
*** jamesmcarthur has quit IRC05:53
*** ysandeep|brb is now known as ysandeep06:12
*** zxiiro has quit IRC06:16
*** jamesmcarthur has joined #zuul06:43
*** jamesmcarthur has quit IRC06:47
*** jamesmcarthur has joined #zuul06:55
*** yolanda has quit IRC06:59
*** jamesmcarthur has quit IRC06:59
*** yolanda has joined #zuul07:00
*** jamesmcarthur has joined #zuul07:01
*** jhesketh has quit IRC07:04
*** jamesmcarthur has quit IRC07:05
*** jamesmcarthur has joined #zuul07:07
*** harrymichal has joined #zuul07:10
*** jamesmcarthur has quit IRC07:11
*** jamesmcarthur has joined #zuul07:13
*** jcapitao has joined #zuul07:16
*** jamesmcarthur has quit IRC07:17
*** jamesmcarthur has joined #zuul07:19
*** rpittau|afk is now known as rpittau07:19
*** jpena|off is now known as jpena07:22
*** jamesmcarthur has quit IRC07:23
*** tosky has joined #zuul07:30
*** bhavikdbavishi has quit IRC07:34
*** jamesmcarthur has joined #zuul07:46
*** jamesmcarthur has quit IRC07:46
*** jamesmcarthur has joined #zuul07:46
*** jamesmcarthur has quit IRC07:49
*** jamesmcarthur has joined #zuul07:49
*** threestrands has quit IRC07:56
*** jamesmcarthur has quit IRC07:57
*** ysandeep is now known as ysandeep|lunch07:57
*** ysandeep|lunch is now known as ysandeep08:25
*** jamesmcarthur has joined #zuul08:28
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Make ubuntu-plain jobs voting  https://review.opendev.org/71970108:45
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Document output variables  https://review.opendev.org/71970408:45
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Python roles: misc doc updates  https://review.opendev.org/72011108:45
*** bhavikdbavishi has joined #zuul09:09
*** ysandeep is now known as ysandeep|afk09:21
*** yolanda has quit IRC09:23
*** yolanda has joined #zuul09:29
*** jamesmcarthur has quit IRC09:34
zbrwhat is the correct way to detect zuul presence from ansible?09:44
zbri used "zuul_work_dir is not defined" but apparently it is not reliable enough.09:45
*** jamesmcarthur has joined #zuul10:03
*** bhavikdbavishi1 has joined #zuul10:08
*** bhavikdbavishi has quit IRC10:08
*** bhavikdbavishi1 is now known as bhavikdbavishi10:08
*** yolanda has quit IRC10:10
avasszbr: I guess you can check the zuul dict: https://zuul-ci.org/docs/zuul/reference/jobs.html#zuul-variables10:12
zbravass: yep, i dediced to check for presence of zuul dict. if someone defines it I can go deeper :D10:12
avasszbr: otherwise I don't know if there's a better way to do it :)10:13
zbris fine, the previous attempt was wrong because it was using the outcome from a role10:13
*** bhavikdbavishi1 has joined #zuul10:24
*** bhavikdbavishi has quit IRC10:26
*** bhavikdbavishi1 is now known as bhavikdbavishi10:26
*** rpittau is now known as rpittau|bbl10:30
*** bhavikdbavishi has quit IRC10:34
*** bhavikdbavishi has joined #zuul10:34
*** bhavikdbavishi has quit IRC10:39
*** bhavikdbavishi has joined #zuul10:44
*** bhavikdbavishi has quit IRC10:48
*** bhavikdbavishi has joined #zuul10:51
*** bhavikdbavishi has quit IRC10:57
*** jcapitao is now known as jcapitao_lunch11:05
tobiashyeah, I think checking for zuul or maybe even zuul.project is the safest thing11:16
avasstobiash: I guess you can do a duck test by checking zuul.project, zuul.build, zuul.buildset, zuul.executor_work root etc and their content would make it robust enough :)11:19
*** jpena is now known as jpena|lunch11:37
*** hashar has joined #zuul11:43
*** rfolco has joined #zuul11:47
*** rlandy has joined #zuul12:06
*** rpittau|bbl is now known as rpittau12:19
*** jcapitao_lunch is now known as jcapitao12:22
*** ysandeep|afk is now known as ysandeep12:35
openstackgerritSimon Westphahl proposed zuul/zuul master: Keep task stdout/stderr separate in result object  https://review.opendev.org/65027612:40
*** Goneri has joined #zuul12:41
*** jpena|lunch is now known as jpena12:44
jktan interesting thing with artifacts: https://gerrit.cesnet.cz/c/CzechLight/netconf-cli/+/2449/4#message-19bab471d8890a29f16a004ecedf3f1798c2f0c213:00
jktthere's a parent commit, its build failed because of some transient race in our tests, yet for this item this "lack of artifacts" from the previous change resulted in cancelation of this job13:02
jkteven though the same artifacts are provided by other jobs for *this* change13:02
jktI wonder if it's possible to tell zuul "hey, please only take this artifact from jobs queued for the current item, not from its parent changes"13:03
*** harrymichal has quit IRC13:15
*** cdearborn has joined #zuul13:39
openstackgerritSimon Westphahl proposed zuul/zuul master: Keep task stdout/stderr separate in result object  https://review.opendev.org/65027613:54
*** ysandeep is now known as ysandeep|away14:31
*** tjgresha_ has joined #zuul14:46
*** jamesmcarthur has quit IRC14:47
*** jamesmcarthur has joined #zuul14:47
*** tjgresha has quit IRC14:49
*** tjgresha__ has joined #zuul15:15
*** tjgresha_ has quit IRC15:18
*** harrymichal has joined #zuul15:26
*** harrymichal has quit IRC15:26
*** harrymichal has joined #zuul15:27
*** saneax has quit IRC15:39
*** dpawlik has quit IRC15:50
*** armstrongs has joined #zuul15:56
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add support for custom container image name  https://review.opendev.org/72076215:58
*** jamesmcarthur has quit IRC15:58
*** jamesmcarthur has joined #zuul15:59
*** dustinc has joined #zuul16:01
corvuszbr: in opendev, we generally avoid switching on whether zuul is present.  our goal is to run tests the same way in or out of zuul.16:03
clarkbjkt: I think that would violate existing zuul behavior. Basically zuul is always trying to test the future proposed outcome16:04
clarkbjkt: if you dropped an intermediate state you'd be half testing that outcome at best16:04
corvusjkt, clarkb: we're still trying to find the best practice there though -- because if the issue is that change A built the project, and change B depends on A, but *also* built the project, then B doesn't *really* depend on the artifact from A.  that's why in the nodepool, zuul, and system-config projects we've been experimenting with more fine-grained provides/requires16:05
corvusi think there's still probably something more to be done in zuul to handle this16:06
*** y2kenny has joined #zuul16:12
*** jcapitao has quit IRC16:14
*** rpittau is now known as rpittau|afk16:17
y2kennyI just want to double check... zuul configs are speculatively run for untrusted-projects but not for config-projects, is that true?16:19
y2kennyIs this due to the privleged nature of config-projects?16:20
clarkby2kenny: yes and yes16:22
y2kennyclarkb: thanks for confirming.  Does the post-review property over ride this behaviour or can this not be override at all?  (I am wondering if I can setup a trigger such that trusted user can trigger the speculative run)16:25
y2kenny(on the config-project change)16:25
clarkby2kenny: post review should override it iirc16:26
clarkbthere might be some aspects that still won't but for things like secrets and playbook content I think it would work fine that way16:26
y2kennyum... ok.  I should probably describe the context a bit just to explain why I am going down this path.16:29
*** ianychoi_ has joined #zuul16:29
y2kennyI am looking at this because most of the projects won't be zuul native so I will need to have a separate project to store zuul job/project definitions.  In order for the side definitions to trigger off the non-zuul-native project, I will have to make it a config-project.16:31
y2kennyBut at the same time, I am writing a tutorial for the developer to build their own jobs/projects in this config-project, so it would be good to be able to speculatively run these changes (especially when the team is still learning about zuul)16:31
*** ianychoi has quit IRC16:31
y2kennythis is why I am looking to have speculatively run on a config-project.  Down the line I might tighten it such that the speulative run only trigger if trusted user comment !recheck or something in the change comment.16:31
*** webknjaz has quit IRC16:33
*** webknjaz has joined #zuul16:33
*** evrardjp has quit IRC16:37
*** evrardjp has joined #zuul16:37
clarkby2kenny: I'll need to think about that more16:38
y2kennyclarkb: actually... now that I gave it some more thought... I think I can improve this by splitting the projects and job configs.  Essentially just following what you guys are doing for the openstack (i didn't know why you guys did it that way but may be this is why.)16:40
y2kennyso I can have a untrusted-project for the jobs so people can speculatively define the jobs.  And an config-projects that would include the 'non-zuul-native' project but consume the job from the untrusted project.  That should work right?16:42
clarkbyes16:43
y2kennyso essentially devs can just iterate in the untrusted jobs project (using required-project to bring in the non-zuul-native project(s))16:43
y2kennywhen they are done, add the job to a project definition in the config-project for triggering on changes from the non-native project16:44
*** y2kenny has quit IRC16:44
*** y2kenny has joined #zuul16:46
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add support for global image prefix  https://review.opendev.org/72078016:51
*** igordc has joined #zuul17:04
fungiy2kenny: that's precisely why we do it that way in fact17:08
fungiwe try to limit what we put into trusted config repos as much as possible because changes to them can't be exercised speculatively17:08
*** igordc has quit IRC17:09
fungiif something can safely go in an untrusted repo, then we try to put it in one17:09
*** harrymichal has quit IRC17:12
*** hashar has quit IRC17:18
*** jpena is now known as jpena|off17:40
*** bhavikdbavishi has joined #zuul17:42
y2kennyfungi: thanks for confirming.  I was wondering about the setup but didn't realize it until I ran into the problem myself.17:45
*** bhavikdbavishi1 has joined #zuul17:52
*** bhavikdbavishi has quit IRC17:54
*** bhavikdbavishi1 is now known as bhavikdbavishi17:54
*** bhavikdbavishi has quit IRC17:58
*** bhavikdbavishi has joined #zuul17:58
*** y2kenny has quit IRC17:59
*** jamesmcarthur has quit IRC18:07
*** jamesmcarthur has joined #zuul18:08
*** jamesmcarthur has quit IRC18:13
*** harrymichal has joined #zuul18:27
*** harrymichal has quit IRC18:41
*** harrymichal has joined #zuul18:41
*** jamesmcarthur has joined #zuul18:42
*** harrymichal has quit IRC18:53
*** jamesmcarthur has quit IRC19:00
*** jamesmcarthur has joined #zuul19:01
*** bhavikdbavishi has quit IRC19:07
*** jamesmcarthur has quit IRC19:15
*** bhavikdbavishi has joined #zuul19:20
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor ZooKeeper service configuration  https://review.opendev.org/72082219:53
*** jamesmcarthur has joined #zuul20:02
*** dustinc has quit IRC20:29
*** bhavikdbavishi has quit IRC20:35
*** rfolco has quit IRC21:11
*** hashar has joined #zuul21:20
*** hashar has quit IRC21:46
*** jamesmcarthur has quit IRC21:47
jktclarkb, corvus: this was with coverage jobs (where I have a build-this-version job and a build-previous-version job and a generate-coverage-diff job), the are provided and configured in the same project22:15
jktclarkb: how is that dropping intermediate state?22:17
clarkbjkt: in the coverage case you wouldn't be considering the coverage delta produced by the intermediate change22:17
clarkbjkt: if the goal is to ensure that coverage always increases then that could break22:17
jktit's late here so I might be dumber than usual, but I really don't follow22:18
jktI understand that one can use artifacts for a lot of purposes :)22:18
jktbut here I'm not really intending to be passing any state between gerrit changes22:19
clarkbjkt: it was my understanding that you were trying to compare coverage artifacts from the previous changes to ensure that the current change tests/covers what was updated22:19
clarkbin that case you are probably fine22:19
clarkbanother coverage related thing that comes up is ensuring coverage doesn't regress ( I personally think that isn't a great practice) and this would break without intermediate results potentially22:19
jktyeah, but consider a change that's just a gerrit change whose parent in tip of the target branch22:20
jktthere's no parent change22:20
jktwhat artifacts would you use?22:20
jkttherefore I have an extra job which is essentially doing a `git reset --hard origin/{{ zuul.branch }}` in its pre-run22:21
clarkbjkt: you'd use the most recent published artifact from the promote queue22:21
clarkband if that doesn't exist then you assume you are first I guess22:21
jktthat would require a registry of artifacts, similarly to what opendev/openstack is doing with their docker registry I guess22:22
jktand also gating, which we do not do22:22
jkt(see that mail to the zuul ML I wrote this Monday I think, it has links to working roles and playbooks)22:22
jktbut anyway, that part works, that's not a problem22:22
jktthe unexpected behavior I brought up today is that I have my pipelines configured with fail-fast: True, and a transient failure of build-this-version job in change 1 led to a failure of compare-coverage in change 2 becase compare-coverage need current-coverage artifact22:27
jktand Zuul apparently infers that if a job requires an artifact that's provided by several "instances" of some jobs in a queue, then all of these jobs must succeed22:28
*** igordc has joined #zuul23:08
*** rlandy has quit IRC23:13
*** tosky has quit IRC23:21
*** igordc has quit IRC23:27

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!