Friday, 2020-02-28

*** mattw4 has quit IRC00:09
*** jamesmcarthur has quit IRC00:09
*** Defolos has quit IRC00:13
*** tosky has quit IRC00:18
*** igordc has quit IRC00:23
*** rlandy has quit IRC00:49
*** jcapitao_off has quit IRC00:50
*** armstrongs has joined #zuul01:18
*** sgw has quit IRC01:26
*** armstrongs has quit IRC01:28
*** saneax has quit IRC02:24
*** swest has quit IRC02:27
*** swest has joined #zuul02:41
*** jamesmcarthur has joined #zuul02:53
*** jamesmcarthur has quit IRC03:22
*** swest has quit IRC05:26
*** evrardjp has quit IRC05:35
*** evrardjp has joined #zuul05:35
*** saneax has joined #zuul05:37
*** bolg has joined #zuul05:53
*** swest has joined #zuul06:10
*** felixedel has joined #zuul06:16
*** bolg has quit IRC06:27
*** sgw has joined #zuul06:30
*** felixedel has joined #zuul06:30
*** smyers has quit IRC06:45
*** smyers has joined #zuul06:45
*** Defolos has joined #zuul06:56
*** bolg has joined #zuul07:02
*** dpawlik has joined #zuul07:09
*** harrymichal has joined #zuul07:21
*** bolg has quit IRC08:06
*** bolg has joined #zuul08:11
*** jcapitao_off has joined #zuul08:11
*** jcapitao_off is now known as jcapitao08:19
*** tosky has joined #zuul08:21
*** harrymichal has quit IRC08:23
openstackgerritFelix Edel proposed zuul/zuul master: WIP Visualize retry builds as expandable rows on buildset page  https://review.opendev.org/71040808:26
openstackgerritFelix Edel proposed zuul/zuul master: WIP Visualize retry builds as expandable rows on buildset page  https://review.opendev.org/71040808:28
*** jpena|off is now known as jpena08:38
openstackgerritTobias Henkel proposed zuul/zuul master: Optimize canMerge using graphql  https://review.opendev.org/70983608:44
*** saneax has quit IRC08:45
*** saneax has joined #zuul08:59
*** harrymichal has joined #zuul09:11
*** saneax has quit IRC09:11
*** saneax has joined #zuul09:13
*** saneax has quit IRC09:13
*** saneax has joined #zuul09:14
*** saneax has quit IRC09:16
*** saneax has joined #zuul09:23
*** avass has joined #zuul09:26
*** harrymichal_ has joined #zuul09:30
*** bertu has joined #zuul09:31
*** harrymichal has quit IRC09:33
*** harrymichal_ is now known as harrymichal09:33
bertuHi! Zuul-CI newbie here.09:33
bertuIn a few places in the Zuul-CI documentation like https://zuul-ci.org/docs/zuul/reference/jobs.html09:34
bertuI read09:34
bertu"The change’s project will have the change’s branch checked out, as will all of the other projects, if that branch exists (otherwise, a fallback or default branch will be used)"09:35
bertuand the like09:35
bertuDoes it mean that if I have branch "foo" on repo A and repo B as required projects09:35
bertuwhen I trigger a build on a change pushed to A@foo also B@foo will be checked out?09:36
bertu*as long as there is a "foo" branch in B*09:36
mnaserbertu: correct09:40
openstackgerritJan Kubovy proposed zuul/zuul master: Scheduler test app manager  https://review.opendev.org/70881209:45
*** harrymichal_ has joined #zuul09:46
*** harrymichal has quit IRC09:47
*** harrymichal_ is now known as harrymichal09:47
harrymichalHi! I'm using Zuul in SoftwareFactory. I got a question. Would it be possible to add the commit hash + link to it to the summary page of a job??10:19
*** jcapitao has quit IRC10:19
*** jcapitao has joined #zuul10:19
harrymichalIt is quite inconvenient when a 'periodic' pipeline is ran on the 'master' branch. There is no way of telling if there was a change introduced between pipelines (at least I don't see one).10:20
*** jcapitao has quit IRC10:20
*** jcapitao has joined #zuul10:20
bertumnaser: that never happens on a Zuul 3.9.0 version that my company uses -> I supposed that means the configuration is customized not to do so...10:34
mnaserbertu: interesting10:34
mnaserbertu: if you are pushing a patch to A@foo, and B is inside required-projects, then B@foo should be checked out in CI10:35
mnaseris that the scenario?10:35
mnaserbertu: it is possible that you have override-branch setup? https://zuul-ci.org/docs/zuul/reference/job_def.html?highlight=override%20checkout#attr-job.override-checkout10:36
bertumnaser: Yes. But it does not work. I have to rely on "Depends-On" for that purpose (i.e. testing changes on different repos at the same time)10:36
mnaseror maybe it's overridden here https://zuul-ci.org/docs/zuul/reference/job_def.html?highlight=override%20checkout#attr-job.required-projects.override-checkout ?10:37
bertumnaser: interesting! I will try to look into the configuration to see what is going on10:37
mnaserbertu: are you trying to test changes that have not landed yet in B@foo ?10:37
bertumnaser: what I meant was that we have PR#1 (A@foo) and PR#2 (B@foo) - we use github, but that should be irrelevant here - and I want to test both before they are merged on the A and B repos10:39
bertumnaser: on the master10:39
mnaserbertu: ok so in this scenario there is 3 projects, right?10:40
mnaserA@foo, B@foo and <some other project that depends on A & B>10:40
bertumnaser: sorry I think I did not explain correctl earlier. Project/repo A, master branch, foo branch + PR#1; project/repo B, master branch, foo branch (with changes already landed)10:44
mnaserbertu: can the changes on any of those repos land in a specific order or they are both depending on each other?10:50
mnaserbertu: can you land the A change before B or vice versa or they really both need to go in together?10:50
mnaserIf they can be ordered, then what you should do is run the B jobs inside A all the time, and run the A jobs inside B all the time — as jobs are not tied to a specific repository. That will give you coverage to make sure projects aren’t breaking each other10:51
mnaserbertu: if they absolutely need to land at the same time to be functional, this is something that’s in the works on Zuul — https://zuul-ci.org/docs/zuul/reference/developer/specs/circular-dependencies.html10:53
mnaserwhich is making progress but not available yet: https://review.opendev.org/#/c/685354/10:54
bertumnaser: does it mean in the last scenario I described foo is not automatically checked out? At this point is more that I cannot match my understanding of the docs to the behaviour I see.10:57
mnaserIf you make a change to A@foo, the branch B@foo should be checked out if it’s inside required-projects10:57
bertumnaser: thanks :) I will check what is going on10:58
bertumnaser: about the use case and your other good suggestions...10:58
mnaserbertu: cool good luck, please let me know if you have other questions11:01
bertumnaser: for reasons I do not fully understand yet, people put CI code (Zuul configs, playbook, etc.) on a separate repo. Let's say CI stuff in repo A and code in repo B. There were cases where I wanted to verify a change on the code together with a change on a CI job, before any of those changes were merged on master. I managed to do that using "Depends-On" but I expected to simply happen because I used the11:03
bertusame branch name for both changes -> but that did not happen11:03
mnaserbertu: I’m that scenario, you could actually just run the repo A jobs inside repo B by appending them to the zuul yaml file11:05
mnaserIn** sorry mobile11:05
bertumnaser: thanks!11:08
mnasernp :)11:09
openstackgerritFelix Edel proposed zuul/zuul master: Dequeue changes via github checks API  https://review.opendev.org/70913511:17
openstackgerritJan Kubovy proposed zuul/zuul master: Make test setup_config more pure  https://review.opendev.org/70908411:37
openstackgerritJan Kubovy proposed zuul/zuul master: Scheduler test app manager  https://review.opendev.org/70881211:37
openstackgerritFelix Edel proposed zuul/zuul master: WIP Dequeue changes via github checks API  https://review.opendev.org/70913511:54
openstackgerritJan Kubovy proposed zuul/zuul master: Use scheduler manager consistently in tests  https://review.opendev.org/70954211:59
*** jcapitao is now known as jcapitao_lunch12:03
*** saneax has quit IRC12:16
openstackgerritJan Kubovy proposed zuul/zuul master: Scheduler test app manager  https://review.opendev.org/70881212:16
*** saneax has joined #zuul12:17
*** jfoufas1 has joined #zuul12:29
*** felixedel has quit IRC12:30
*** jpena is now known as jpena|lunch12:33
*** armstrongs has joined #zuul12:33
jfoufas1This zuul web gui looks nice, https://ci.gerritcodereview.com/t/gerrit/build/28b385d0e989449cb2ac1fcb2cb8e1ca, any info?12:35
tristanCharrymichal: indeed it seems like zuul doesn't report the exact ref used in periodic pipeline. perhaps that could be added, but that won't necessarly tell you all the commit that was introduced between two run12:41
tristanCcorvus: is a zuul release planned soon? (for the security fix)12:42
*** armstrongs has quit IRC12:44
openstackgerritJan Kubovy proposed zuul/zuul master: Scheduler test app manager  https://review.opendev.org/70881212:46
fungijfoufas1: what info are you looking for?12:51
fungiif you're looking for details of what was run and what output was emitted, then the console view may be more useful than the summary view12:54
jfoufas1fungi if the additions to the web gui, logs and console will be added12:55
fungior the logs view, though that particular build only seems to collect stdout/stderr from the commands plus some job metadata12:55
fungijfoufas1: what additions?12:55
fungiif the job collects more log files they'll appear in the logs view, yes12:55
fungiand whatever ansible playbooks/tasks are added will appear in the console view12:56
fungii feel like i might be missing your question12:56
jfoufas1fungi thank you, that answers it.12:57
fungiokay, cool. i expect all of us in here are happy to answer any questions you have12:58
*** rlandy has joined #zuul12:59
fungijfoufas1: looking at a failed build might provide a better example too: https://ci.gerritcodereview.com/t/gerrit/build/06b7799459f049b79e3d15d2e574027813:00
fungimore effort is taken to expose the likely failure point from the output stream with some context, since people tend to look at failure results a lot more often than successful build details13:02
*** jfoufas1 has quit IRC13:02
fungioh, i guess they's already disconnected13:02
fungier, they'd13:02
Shrewsfungi: you live in a southern state. "they's" is a perfectly cromulent word13:04
fungithanks, your knowledge of southern dialects embiggens us both13:05
harrymichaltristanC, that is true but it can tell me if the problem (if suddenly tests start failing) was introduced by the project itself or some of its dependencies13:07
harrymichalfor my use case that is quite handy to know13:07
*** jamesmcarthur has joined #zuul13:09
*** jcapitao_lunch is now known as jcapitao13:14
*** jamesmcarthur has quit IRC13:18
*** jamesmcarthur has joined #zuul13:21
*** jamesmcarthur has quit IRC13:36
*** jamesmcarthur has joined #zuul13:37
*** jpena|lunch is now known as jpena13:38
*** toabctl has quit IRC13:38
openstackgerritMerged zuul/zuul master: Support file comments via Github checks API  https://review.opendev.org/70861113:41
*** jamesmcarthur has quit IRC13:53
*** jamesmcarthur has joined #zuul13:55
openstackgerritJan Kubovy proposed zuul/zuul master: Scheduler test app manager  https://review.opendev.org/70881213:55
*** Goneri has joined #zuul14:00
*** saneax has quit IRC14:16
*** jfoufas1 has joined #zuul14:30
jfoufas1fungi i got thrown out of IRC...network porblems. We are still quite new to zuul, and the real devops like avass still do not understand what needs to be published in order to appear in console view.14:39
*** jamesmcarthur has quit IRC14:41
corvusjfoufas1: for log files to show up in the logs tab, basically, any file that's in the logs directory of the executor workdir at the end of the job will end up there; the easiest way to do that is to put log files in ~/logs on the worker nodes, then use this role, https://zuul-ci.org/docs/zuul-jobs/log-roles.html#role-fetch-output in the post playbook of your base job to pull them back at the end of the job.14:43
corvusjfoufas1: the console tab is built automatically from the ansible tasks that run in the job14:43
mordred~/zuul-output/logs14:44
corvusoh sorry, yes.  that's the directory to use on the worker node.14:44
*** avass has quit IRC14:46
jfoufas1corvus will have to look into it, for some reason we do not get the tabs, even though logs are in ~/zuul-output/logs14:46
corvusjfoufas1: ah -- if the tabs are missing, there might be something else missing, 1 sec14:47
*** jamesmcarthur has joined #zuul14:47
jfoufas1avass: says we use the role too..14:47
corvusjfoufas1: for the tabs to work, you'll need the https://zuul-ci.org/docs/zuul-jobs/log-roles.html#role-generate-zuul-manifest role in the base job post playbook too, right before the upload logs role.14:48
jfoufas1corvus: that's it!!!14:48
corvusjfoufas1: and whatever log storage system you're using will need to support CORS headers.  the swift and gcp log roles should automatically do that, but if you're running a static server, you'll need to configure the http server to set them14:49
*** jfoufas1 has quit IRC14:59
corvustristanC, fungi: does this look good for a release to get the security fix: commit 0684df0dd191427d000f0cee2e18ccdc07f5f3c8 (tag: 3.17.0, refs/changes/87/710287/2)15:00
corvusthat's one back from master; we could probably release master (it's one more github change which i assume tobiash has tested in prod)15:00
corvusbut since it's a security fix, i was tending toward being conservative15:00
mordredcorvus: d191427 is what we're running in opendev?15:01
mordredgah - 0684de0 I mean15:02
corvusmordred: no, i don't think we're running it15:02
tristanCcorvus: that sounds good, fwiw we are running with a cherry-pick of the fix on 3.13.0 and 3.10.215:04
tobiashcorvus: which github change?15:04
openstackgerritJan Kubovy proposed zuul/zuul master: Use scheduler manager consistently in tests  https://review.opendev.org/70954215:04
openstackgerritJan Kubovy proposed zuul/zuul master: Refactor executor_client in tests  https://review.opendev.org/70967215:04
corvustobiash: file comments15:04
tobiashthat's one we don't have yet in prod15:04
tobiashbut the other checks api changes are in and working :)15:04
corvusoh good, then let's stick with what i proposed :)15:05
corvusmordred: i think with the feedback from tristanC i'm pretty comfortable releasing that commit before opendev restarts15:05
mordredcorvus: ++15:05
corvusokay, i'll make it so15:05
fungiyep, sgtm15:07
fungisorry, spending my morning down an openstack vulnerability management spring cleaning hole15:07
corvusit's that season15:08
corvusgerrit folks: you may be interested to know that numeric change ids (indeed, all formats of change ids) are no longer deprecated (ie, they will continue to be supported): https://gerrit-review.googlesource.com/c/gerrit/+/25679215:09
fungiyay! that's great news15:12
mordredthat IS great news!15:13
* mordred has been dreading that future removal15:13
toskyoooh, people realized that compatibility is not a bad thing15:15
*** felixedel has joined #zuul15:23
*** felixedel has quit IRC15:23
*** jamesmcarthur has quit IRC15:41
*** jcapitao is now known as jcapitao_afk15:47
*** jamesmcarthur has joined #zuul15:52
*** jamesmcarthur has quit IRC15:57
openstackgerritJan Kubovy proposed zuul/zuul master: Refactor merge_client in tests  https://review.opendev.org/70967616:00
*** bertu has quit IRC16:04
*** jcapitao_afk is now known as jcapitao16:05
*** y2kenny has joined #zuul16:09
openstackgerritJan Kubovy proposed zuul/zuul master: Refactor nodepool in tests  https://review.opendev.org/70970316:10
y2kennyHi, I just started looking into Zuul.  If I connect Zuul to Gerrit, what happens to Gerrit changes if the connection between Zuul and Gerrit is disrupted?  (for example, if stream events are dropped/lost?)  How does Zuul recover?16:12
clarkby2kenny: you'll have a gap in time where events are not received16:13
clarkbZuul also has experimental support for Gerrit's new checks api plugin (which polls and would notice things were missed)16:13
clarkbin general though stream events has been pretty solid for us (opendev). We miss events due to outages in Zuul (upgrades etc) and not due to network connectivity or gerrit ssh problems16:14
y2kennyok.  Are there ways to tell Zuul to bulk check things manually?  (or for me to "inject" potentially missed events?)  I think Gerrit and Zuul are great.  I am only asking because the network environment I am in can be flicky sometimes.16:17
clarkby2kenny: yes, the way we do that is we add a magic comment string that triggers zuul pipelines (in our case 'recheck'). This allows anyone with comment ability in gerrit to trigger those pipelines. You can also use the zuul-enqueue utility (and maybe the api now?) to enqueue those as an admin16:18
clarkbwe tend to use a mixture of both. Let anyone leave comments in gerrit for rerunning premerge tests, then rely on admins for post merge enqueues. The reason for that is post merge tends to have side effects you may need to think about before running them (though that is possibly specific to our use of those pipelines)16:20
*** mattw4 has joined #zuul16:20
y2kennycool.  I saw the recheck bit in the zuul quick start tutorial but did not know about the zuul-enqueue utility.  I will check that out.16:21
y2kennythanks for the tips!16:21
corvusy2kenny, clarkb: actually it's "zuul enqueue"  (ie, the command is zuul, with enqueue as the subcommand)16:22
y2kennycorvus: ok, thanks!16:22
corvusy2kenny: https://zuul-ci.org/docs/zuul/reference/client.html#enqueue16:23
*** jamesmcarthur has joined #zuul16:26
*** harrymichal has quit IRC16:34
*** y2kenny has left #zuul16:34
clarkbcorvus: mordred I think we can restart opendev zuul to pick up that change16:36
corvusyep, i'll do that16:37
openstackgerritJan Kubovy proposed zuul/zuul master: Refactor zookeeper in tests  https://review.opendev.org/70970916:39
openstackgerritJan Kubovy proposed zuul/zuul master: Consolidate scheduler pause/exit as hibernation  https://review.opendev.org/70972316:51
*** tosky has quit IRC17:09
*** michael-beaver has joined #zuul17:11
openstackgerritJan Kubovy proposed zuul/zuul master: Refactor `self.event_queues` in tests  https://review.opendev.org/70999017:12
*** jcapitao has quit IRC17:14
openstackgerritJan Kubovy proposed zuul/zuul master: Scheduler's pause/resume functionality  https://review.opendev.org/70973517:34
*** evrardjp has quit IRC17:35
*** evrardjp has joined #zuul17:35
zenkurohi, is there anything necessary to make a commit on zuul repo besedes ubuntu one account?17:41
clarkbzenkuro: you need to create a gerrit account (via ubuntu on login) and add an ssh key to push the code (or use http auth, but ssh will be simpler if it works for you)17:42
clarkbthat should be it17:43
*** jpena is now known as jpena|off17:50
openstackgerritJan Kubovy proposed zuul/zuul master: WIP: Store unparsed branch config in Zookeeper  https://review.opendev.org/70571617:50
fungiwas there any story on storyboard related to https://review.opendev.org/710287 ?17:52
fungijust want to make sure we switch it to public if so17:52
tristanCfungi: i just made it public https://storyboard.openstack.org/#!/story/200732717:53
fungithanks!17:54
fungii've added the zuul-security story tag, since that's what we usually rely on to query for them17:55
fungiprobably easiest workflow is to ass the zuul-security when triaging a private security story, make it public shortly before pushing a patch to gerrit, and reference the task id in the commit message17:56
fungithat way we get the relevant updates17:56
fungis/ass/add/ obviously. it's friday17:57
fungii'll eventually get something written up about a vulnerability workflow for our maintainer docs17:57
funginow that we've mostly got it figured out17:58
*** jamesmcarthur has quit IRC18:06
paladoxcorvus https://gerrit-review.googlesource.com/c/gerrit/+/257077 awesome!18:08
zenkuroclarkb: git clone ssh://zenkuro@review.opendev.org/zuul/zuul is it correct? It says I have no access writes or repo do not exists18:08
fungizenkuro: git clone https://opendev.org/zuul/zuul18:10
clarkbzenkuro: gerrit uses port 29418 (not default of 22) for ssh. Typically though you'll clone from https://opendev.org/zuul/zuul then run `git review -s` to configure the gerrit remote18:10
clarkbthen you can use gerrit just for pushing proposed changes using the git review tool18:10
fungiuse the https://pypi.org/project/git-review tool to submit changes18:10
fungiit will interpret the correct gerrit remote from the .gitreview file stored in the repository18:11
corvuspaladox: thanks!  https://gerrit-review.googlesource.com/c/zuul/jobs/+/257078  found a bug, so i'm fixing that now; i think i should be able to remove WIP on those and send an update email soon18:20
paladoxoh, heh18:21
clarkbit would be really neat if the "relationship chain" was a graph.18:23
clarkb(I filed a bug about that like 4 yaers ago and am sad it never happened with all of the other UI work)18:23
clarkbalso I guess the checks api doesn't incorporate voting and that still happens as regular comments so you get them in the comments list?18:25
paladoxnope18:25
paladoxcheckers is not a comment :)18:25
paladoxyou click on the checks tab18:25
clarkbpaladox: ya I'm more concerned that we've gone out of our way to remove the vote comments from the ui and sumarrize them in the table instead18:26
clarkb(for some reason I thought the checks api sort of approximated that with its table and voting, but it doesn't)18:26
clarkbmordred: ^ something to think about when upgrading. We may still need js to clean that up18:26
fungior does the checks api allow you to set a status which can be used to signal/block?18:27
mordredwhat fungi said18:27
mordredthe subchecks spec that corvus has been working on is the key part there18:28
fungiyeah, so basically "votes" is oldthink anyway18:28
clarkbmordred: subchecks in order to represent check and gate?18:28
fungiso people "vote" on changes, bots set a status of some sort18:28
mordredclarkb, fungi: https://gerrit-review.googlesource.com/c/homepage/+/235692 and https://gerrit-review.googlesource.com/c/homepage/+/23569318:28
mordredit won't be usable by opendev until subchecks exists18:29
mordred(I'd try to summarize in irc real quick - but honestly it's one of those topics where the details are the important part)18:30
clarkbmordred: that splits jobs out so you can see them seprate from the top level yay or nay right? but how do you express that there are two levels of pre merge testing?18:30
clarkbmordred: maybe thats just two different top level checkers and you need both to merge?18:30
openstackgerritZen Kurosaky proposed zuul/zuul master: This patch extends zuul deployment from scratch documentation.     it adds guide on MySQL setup     it extends zuul-from-scratch setup by adding mysql connection to zuul.conf file     it extends gerrit setup by adding Verified label to gerrit     it exten  https://review.opendev.org/71050418:31
mordredclarkb: yeah - for opendev we'd have a "Zuul Check" checker and a "Zuul Gate" checker - and those would be required. then Zuul would define one or more subchecks corresponding to each job, and should mark them as either required or not required based on non-voting flag18:31
mordredwe would also be able to define Checkers for 3pci systems (obviously marked as not required)18:32
clarkbok so you'll have a "Gate missing" or whatever message until it runs and reports back. Thats actually nice if it renders that way as it will help people understand what they need next in order to merge18:32
mordredyeah - I thnk it's going to be VERY nice once it's all in place18:32
zenkuromany thanks fugi, clarkb, and corvus! I havent specified account on gerrit  >_<18:33
clarkbmordred: what that doesn't do though is force third party ci to use the checker api (and i'm not sure we can turn off stream events because we need the post merge stuff)18:33
corvusmordred, clarkb: re gate -- i think we can actually add a gate to the zuul/* repos on gerrit's gerrit and see that in action.18:33
clarkbcorvus: ooh that would be cool18:33
corvusi don't think we've sold the gerrit community on that in general, but i doubt they would object to seeing that on those repos, and i think it would help exercise checks18:34
clarkb++18:34
mordred++18:34
mordredclarkb: luca tells me the webhooks plugin should be sufficient for post-merge things ... but I agree, I think we'll have stream-events for the forseeable future18:35
corvuspaladox, clarkb, mordred: and re voting -- i think there's some rough consensus that at the moment, it's helpful to have checkers vote as well.  so i think i will propose that for gerrit's zuul.  (note that the existing gerritforge ci system does use checkers and votes)18:35
corvuseg https://gerrit-review.googlesource.com/c/gerrit/+/25707318:36
clarkbcorvus: ya gerritforge is how I noticed that. I my concern is that I had thought we were going to get awy from that noise and could delete some js18:36
paladoxyeh, i think someone on the gerrit groups, there's something they wrote that needs to be addressed before they switch off using v+1 for gerrit-forge18:36
clarkbbut I guess we don't have to run our CI systems against our gerrit that way18:36
corvusyes i think that is the goal18:36
mordredclarkb: that said - once it's there and in place, we can incentivize 3pci to use checks instead of comments - since we won't have a hideci.js to create a table of results for 3pci leaving results in comments18:36
corvusi think it's just "not quite there yet"18:36
corvusclarkb, paladox, mordred: see this message i wrote (which started being about gertty, but is relevant in general): https://groups.google.com/forum/#!topic/repo-discuss/mubpTaKHUZ418:37
mordredclarkb: it's not even so much that we *can* delete some js - it's more that we're going to delete that js when we upgrade to polygerrit and checks is the path to things being ina . table of results :)18:37
paladoxmordred seems that i think Thomas has added a plugin entry point to make hideci possible in PG *i think*.18:37
mordredpaladox: right - but we're looking towards checks and don't want hideci :)18:38
paladoxcorvus ohh, reading!18:38
paladoxmordred :D18:38
paladoxWe made progress on our upgrade: https://gerrit.wikimedia.org/r/#/c/operations/software/gerrit/+/574092/ :)18:39
paladoxJust need to roll that out to a test instance, run the schema upgrade and if it passes we can roll it out to prod at a specified date.18:40
mordredpaladox: nice!18:40
corvuspaladox: exciting!  mordred has been busy working on opendev's as well18:40
mordredyah. we're getting close as well18:41
corvusthe work to set up zuul jobs in gerrit is feeding back into opendev, and vice-versa.  so our build jobs have been changing and are starting to converge18:41
paladoxyup! I would like for us to upgrade this month...18:42
corvushttps://gerrit-review.googlesource.com/c/zuul/jobs/+/257080 is the 4th interation of the code to prepare gerrit submodule in zuul jobs -- the first was in opendev, the second in gerrit, the third in opendev again, and that's the 4th back in gerrit... when we're done, we'll only have one copy and use it in both places18:43
paladoxonly because i want to give our users time to get use to the new ui.18:43
corvushttps://review.opendev.org/710489 is prep work to start using that directly18:43
clarkbzenkuro: left a few notes on that change.18:44
corvuswhen we have that working, i'll write that up for the repo-discuss list too, so folks can see it.  cross-community sharing of ci implementation is pretty novel.  :)18:44
zenkuroclarkb: write it here or add to gerrit?18:45
clarkbzenkuro: not sure if you are familiar with updating gerrit changes but typically you will udpate the existing change (either git commit --amend or git rebase -i and squash back) then rerun git review and it will update the existing change as long as you keep the same change-id in the commit message18:45
clarkbzenkuro: in gerrit on the change (you might have to refresh the page in your brwoser to see them)18:46
paladoxcorvus should "- jgit" that be "- modules/jgit"?18:46
clarkbzenkuro: overall it looks good. Suggestions are mostly minor edits18:47
paladoxoh, i see i've misread it, it's cloning that. Sorry :)18:47
corvuspaladox: that's the name of the repo in gerrit (it's just "jgit"); the role has a mapping table that tells where to put projects that go into places other than their name: https://gerrit.googlesource.com/zuul/jobs/+/refs/heads/master/roles/prepare-gerrit-repos/defaults/main.yaml18:48
corvuspaladox: (and zuul would have failed the change with an error if the project name were wrong)18:48
paladoxah18:48
corvuspaladox: you can see what a zuul syntax error looks like on PS6 of this change: https://gerrit-review.googlesource.com/c/zuul/jobs/+/25565218:49
*** jamesmcarthur has joined #zuul18:49
*** jamesmcarthur_ has joined #zuul18:50
paladoxHmm, seems to https://ci.gerritcodereview.com/t/gerrit/buildset/f852104e0abc4a7cba30e84a412c2aee stay stuck loading.18:50
corvusneat18:50
paladoxin the console i see "Unhandled Promise Rejection: TypeError: undefined is not an object (evaluating 'e.request.responseURL')"18:51
corvusi see an "e.request is undefined"18:52
*** jamesmcarthur has quit IRC18:54
*** jamesmcarthur_ has quit IRC18:54
*** mattw4 has quit IRC18:54
*** jamesmcarthur has joined #zuul18:56
*** jamesmcarthur_ has joined #zuul18:56
zenkuroclarkb: gerrit do only supports rsa keys?18:57
paladoxcorvus https://opendev.org/zuul/zuul/src/branch/master/web/src/actions/errors.js#L2718:59
paladoxi think that can be "url: error && error.request && error.request.responseURL || error.url"18:59
*** jamesmcarthur has quit IRC19:00
clarkbzenkuro: older gerrit does, newer gerrit supports more. But your examples use rsa filenames. I think you should set -t foo and the filenames to match just to avoid any changing of keygen defaults19:00
corvuspaladox: ah thanks, yep!  and that gets me to the real error, which is that the builds value is not returned in the json response if there are no builds19:01
paladox:)19:01
corvusso we either need to handle that being absent, or update the server to return the empty list19:01
corvustristanC: ^ do you have a preference?19:02
mordredcorvus, paladox: https://review.opendev.org/709602 Use prepare-gerrit-repo role for gerrit submodules ... there's the stab at using prepare-gerrit-repos from opendev ... although now that I'm looking at it I realize I removed one too many things so that's not going to do what we want19:06
openstackgerritJames E. Blair proposed zuul/zuul master: web ui: fix buildset display when no builds  https://review.opendev.org/71050819:07
corvuspaladox: ^ that fixes it for me locally; thanks for catching that!19:08
mordredcorvus: the current thign in tree has a "gerrit_additional_plugins" which tells the job which repos should also be copied into the gerrit tree ... we still need that. BUT - I think I could rewrite it to look for things in the projects list that don't already exist in the plugins dir19:08
corvusmordred: ack; i'll take a look after lunch; gotta run, biab19:08
mordredcorvus: have good lunch19:08
paladoxcorvus thanks!19:09
paladoxmordred nice!19:10
openstackgerritZen Kurosaky proposed zuul/zuul master: This patch extends zuul deployment from scratch documentation.  https://review.opendev.org/71050419:17
*** jamesmcarthur_ has quit IRC19:19
tristanCcorvus: i have no preference, it seems like there are a few edge case the webui doesn't handle well19:20
mordredtristanC: corvus pushed up a "fix it in the ui" patch :)19:21
*** mattw4 has joined #zuul19:22
openstackgerritZen Kurosaky proposed zuul/zuul master: This patch extends zuul deployment from scratch documentation.  https://review.opendev.org/71050419:22
*** sgw has quit IRC19:22
zenkuroclarkb: I will think on how to get rid of rsa... thanks for advises. I think I fixed most of them19:23
*** felixedel has joined #zuul19:25
*** jamesmcarthur has joined #zuul19:26
*** jamesmcarthur_ has joined #zuul19:26
*** jamesmcarthur has quit IRC19:30
*** EmilienM is now known as EvilienM19:30
*** jamesmcarthur_ has quit IRC19:33
*** sgw has joined #zuul19:41
mordredcorvus: when you get back ... I've produced an Unknown configuation error!19:41
fungithat sounds glorious19:41
mordredyeah19:42
mordredI think it's related to system-config being in opendev and openstack again ... but still, it's pretty glorious19:42
*** dpawlik has quit IRC19:43
*** dpawlik has joined #zuul19:43
mordredhttp://paste.openstack.org/show/790132/19:43
*** mattw4 has quit IRC19:44
*** mattw4 has joined #zuul19:46
fungiso the parent_layout came through as None?19:52
mordredyeah19:54
pabelangerWe've upgraded zuul to 3.17.0, thanks! About to try new check API integration for github19:55
mordredpabelanger: woot!19:55
mordredpabelanger: oh - wait19:55
mordredpabelanger: I don't think check api is in 3.1719:55
pabelangeroh, relnotes says it is19:56
mordredoh - yes19:56
mordredit's the inline comments that just missed 3.1719:56
mordredyou're probably fine without that :)19:56
pabelangerack19:56
*** jamesmcarthur has joined #zuul19:58
*** jamesmcarthur_ has joined #zuul19:59
mordredcorvus, fungi: yup - the issue is just on the opendev tenant - the openstack tenant job is running fine20:03
mordredalthough there is an error I'd liek to ponder what the best way to deal with is20:03
*** jamesmcarthur has quit IRC20:03
mordredoh - I think I've got it20:03
*** jamesmcarthur_ has quit IRC20:18
pabelangeryay20:19
pabelangerhttps://github.com/ansible-collections/openvswitch/pull/4/checks20:19
*** jamesmcarthur has joined #zuul20:19
*** jamesmcarthur_ has joined #zuul20:20
pabelangerwith checks now, i guess that could be broken out into jobs vs buildset20:22
*** jamesmcarthur has quit IRC20:24
mordredpabelanger: woot!20:47
pabelangerneat, summary of results looks good too: https://github.com/ansible-collections/openvswitch/pull/4/checks?check_run_id=47568554820:56
pabelangerwaiting to get failure results, but if they also work, I think we could stop commenting directly on the PR20:56
pabelangerwhich some folks do not like and consider spam20:56
*** jamesmcarthur_ has quit IRC21:03
mordredpabelanger: yay improvements!21:03
pabelangerand failure21:04
pabelangerhttps://github.com/ansible/project-config/pull/371/checks?check_run_id=47574591621:04
pabelangerI wonder if that 'recheck' button can be disabled21:04
pabelangeror if that is an event that zuul sees21:04
pabelangeroh, maybe that is check_run21:04
mordredpabelanger: I don't see recheck - so prolly only a committer visible thing?21:05
pabelangeroh, maybe21:05
pabelangerneed to read up21:05
mordredcorvus: interesting. I just got "Change in gerrit/jobs[master]: Copy release.war into zuul artifact location" in email for the change I pushed up to zuul/jobs ... I'm guessing there's something that rename-project may not have updated21:29
corvuswas that project renamed?  i thought it was created that way21:32
*** armstrongs has joined #zuul21:35
mordredcorvus: dunno - not sure why it's saying gerrit/jobs in the email then21:36
*** mattw4 has quit IRC21:46
pabelangerregarding https://zuul-ci.org/docs/zuul/reference/drivers/github.html#attr-pipeline.require.%3Cgithub%20source%3E.status that should also work for checks API too?21:47
pabelangerthat might be a tobiash question21:48
clarkbpabelanger: is the checks api used to trigger or just to report?22:00
pabelangerwe use it to trigger, so we know the check jobs first all passed22:02
pabelangerfrom what I see, the checks api does not show up as a statuses now22:02
pabelangerhttps://api.github.com/repos/ansible/project-config/statuses/9d6cec08710162593ddf3e63731168c5f337751822:07
pabelangerthose are the results for status, we set22:07
pabelangerbut you can see https://github.com/ansible/project-config/pull/375 there are 2 ansible/check now22:07
*** bolg has quit IRC22:07
pabelangersorry, internet died22:07
*** rlandy has quit IRC22:21
*** tosky has joined #zuul22:24
*** mattw4 has joined #zuul22:54
*** EvilienM is now known as EmilienM22:56
openstackgerritMerged zuul/zuul master: Stream output from kubectl pods  https://review.opendev.org/70926123:07
*** dpawlik has quit IRC23:13
*** mattw4 has quit IRC23:29

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