| *** wuchunyang has quit IRC | 00:00 | |
| *** tosky has quit IRC | 00:02 | |
| *** rlandy has quit IRC | 00:57 | |
| *** ikhan has joined #zuul | 01:27 | |
| *** Goneri has quit IRC | 01:30 | |
| *** zenkuro has quit IRC | 01:30 | |
| *** armstrongs has joined #zuul | 01:40 | |
| *** armstrongs has quit IRC | 01:50 | |
| *** smyers_ has joined #zuul | 01:55 | |
| *** smyers has quit IRC | 01:55 | |
| *** smyers_ is now known as smyers | 01:55 | |
| dmsimard | o/ long time no see | 02:09 |
|---|---|---|
| *** rfolco has joined #zuul | 02:27 | |
| *** wuchunyang has joined #zuul | 02:29 | |
| *** rfolco has quit IRC | 02:32 | |
| *** bhavikdbavishi has joined #zuul | 02:49 | |
| *** bhavikdbavishi1 has joined #zuul | 02:52 | |
| *** bhavikdbavishi has quit IRC | 02:53 | |
| *** bhavikdbavishi1 is now known as bhavikdbavishi | 02:53 | |
| *** bhavikdbavishi has quit IRC | 03:05 | |
| *** ajitha has joined #zuul | 03:28 | |
| *** bhavikdbavishi has joined #zuul | 03:37 | |
| *** bhavikdbavishi1 has joined #zuul | 03:40 | |
| *** bhavikdbavishi has quit IRC | 03:42 | |
| *** bhavikdbavishi1 is now known as bhavikdbavishi | 03:42 | |
| *** wuchunyang has quit IRC | 04:00 | |
| *** ikhan has quit IRC | 04:16 | |
| *** ikhan has joined #zuul | 04:17 | |
| *** ikhan has quit IRC | 04:21 | |
| *** bhavikdbavishi has quit IRC | 04:25 | |
| *** bhavikdbavishi has joined #zuul | 04:26 | |
| *** vishalmanchanda has joined #zuul | 04:27 | |
| *** sanjayu__ has joined #zuul | 04:55 | |
| *** sanjayu_ has quit IRC | 04:57 | |
| *** evrardjp has quit IRC | 05:33 | |
| *** evrardjp has joined #zuul | 05:33 | |
| *** wuchunyang has joined #zuul | 05:36 | |
| *** jfoufas1 has joined #zuul | 06:09 | |
| *** bhavikdbavishi1 has joined #zuul | 06:10 | |
| *** bhavikdbavishi has quit IRC | 06:12 | |
| *** bhavikdbavishi1 is now known as bhavikdbavishi | 06:12 | |
| *** ikhan has joined #zuul | 06:16 | |
| *** ikhan has quit IRC | 06:21 | |
| *** hamalq has quit IRC | 06:21 | |
| *** hamalq has joined #zuul | 06:22 | |
| *** zbr has quit IRC | 06:52 | |
| *** zbr has joined #zuul | 06:52 | |
| *** mach1na has joined #zuul | 07:19 | |
| *** mach1na has joined #zuul | 07:19 | |
| *** bhavikdbavishi has quit IRC | 07:27 | |
| *** mach1na has quit IRC | 07:45 | |
| *** mach1na has joined #zuul | 07:54 | |
| *** bhavikdbavishi has joined #zuul | 07:57 | |
| *** rpittau|afk is now known as rpittau | 07:59 | |
| *** bhavikdbavishi1 has joined #zuul | 08:00 | |
| *** jcapitao has joined #zuul | 08:00 | |
| *** bhavikdbavishi has quit IRC | 08:01 | |
| *** bhavikdbavishi1 is now known as bhavikdbavishi | 08:01 | |
| *** mach1na has quit IRC | 08:05 | |
| *** mach1na has joined #zuul | 08:08 | |
| *** hashar has joined #zuul | 08:10 | |
| *** ikhan has joined #zuul | 08:16 | |
| *** jpena|off is now known as jpena | 08:17 | |
| *** ikhan has quit IRC | 08:21 | |
| *** bhavikdbavishi has quit IRC | 08:33 | |
| *** bhavikdbavishi has joined #zuul | 08:35 | |
| *** tosky has joined #zuul | 08:40 | |
| *** bhavikdbavishi has quit IRC | 08:45 | |
| *** bhavikdbavishi has joined #zuul | 08:59 | |
| *** ikhan has joined #zuul | 09:16 | |
| *** ikhan has quit IRC | 09:21 | |
| openstackgerrit | Jonas Sticha proposed zuul/nodepool master: WIP: aws: add support for uploading diskimages https://review.opendev.org/c/zuul/nodepool/+/735217 | 09:42 |
| *** zbr has quit IRC | 09:51 | |
| *** zbr has joined #zuul | 09:56 | |
| *** wuchunyang has quit IRC | 10:05 | |
| *** zenkuro has joined #zuul | 10:14 | |
| *** bhavikdbavishi has quit IRC | 10:27 | |
| *** wuchunyang has joined #zuul | 10:55 | |
| *** wuchunyang has quit IRC | 10:57 | |
| *** wuchunyang has joined #zuul | 10:57 | |
| *** zbr has quit IRC | 10:58 | |
| *** wuchunyang has quit IRC | 10:58 | |
| *** wuchunyang has joined #zuul | 10:58 | |
| *** zbr has joined #zuul | 10:58 | |
| *** zbr has quit IRC | 11:00 | |
| *** zbr has joined #zuul | 11:00 | |
| *** wuchunyang has quit IRC | 11:03 | |
| *** zbr has quit IRC | 11:03 | |
| *** zbr has joined #zuul | 11:04 | |
| *** zbr has quit IRC | 11:07 | |
| *** ikhan has joined #zuul | 11:16 | |
| *** zbr has joined #zuul | 11:17 | |
| *** ikhan has quit IRC | 11:21 | |
| *** wuchunyang has joined #zuul | 11:37 | |
| *** jcapitao is now known as jcapitao_lunch | 11:39 | |
| *** wuchunyang has quit IRC | 11:42 | |
| *** wuchunyang has joined #zuul | 11:55 | |
| *** wuchunyang has quit IRC | 11:59 | |
| *** wuchunyang has joined #zuul | 12:00 | |
| *** wuchunyang has quit IRC | 12:03 | |
| *** mach1na has quit IRC | 12:05 | |
| *** rfolco has joined #zuul | 12:06 | |
| *** iurygregory|pto has joined #zuul | 12:08 | |
| *** wuchunyang has joined #zuul | 12:13 | |
| *** ikhan has joined #zuul | 12:16 | |
| *** wuchunyang has quit IRC | 12:19 | |
| *** zenkuro has quit IRC | 12:19 | |
| *** zenkuro has joined #zuul | 12:19 | |
| *** ikhan has quit IRC | 12:21 | |
| *** wuchunyang has joined #zuul | 12:23 | |
| *** wuchunyang has quit IRC | 12:28 | |
| *** wuchunyang has joined #zuul | 12:32 | |
| *** jpena is now known as jpena|lunch | 12:32 | |
| *** wuchunyang has quit IRC | 12:36 | |
| *** jcapitao_lunch is now known as jcapitao | 12:52 | |
| *** mach1na has joined #zuul | 12:59 | |
| *** zenkuro has quit IRC | 13:02 | |
| *** zenkuro has joined #zuul | 13:02 | |
| *** rlandy has joined #zuul | 13:03 | |
| *** rlandy is now known as rlandy|PTO | 13:04 | |
| *** ikhan has joined #zuul | 13:05 | |
| *** ikhan has quit IRC | 13:06 | |
| *** ikhan has joined #zuul | 13:06 | |
| *** jpena|lunch is now known as jpena | 13:30 | |
| *** sshnaidm has quit IRC | 13:38 | |
| *** Goneri has joined #zuul | 13:43 | |
| *** sshnaidm has joined #zuul | 13:46 | |
| *** sshnaidm has quit IRC | 13:48 | |
| tristanC | dmsimard: welcome back o/ | 15:10 |
| *** mach1na has quit IRC | 15:13 | |
| *** hashar is now known as hasharAway | 15:20 | |
| *** mach1na has joined #zuul | 15:23 | |
| *** y2kenny has joined #zuul | 15:49 | |
| y2kenny | Are there any folks from Volvo around? | 15:50 |
| fungi | avass: ^ | 15:51 |
| y2kenny | (I am hoping to get their Open Infra summit slide deck on Zuul for some internal advocacy about Zuul.) | 15:52 |
| y2kenny | I found the youtube video but it's not so nice to include that into my presentation. | 15:52 |
| *** irclogbot_3 has quit IRC | 15:53 | |
| y2kenny | My presentation will be like "Volvo is using it too" type thing. | 15:53 |
| y2kenny | I think BMW folks also had some presentation but I think that was back in 2018 | 15:54 |
| corvus | y2kenny: yes, bmw had talks (and keynotes) as well. they're still using zuul (even more now than then), so may still be relevant for advocacy :) | 15:55 |
| corvus | y2kenny: https://www.openstack.org/summit/berlin-2018/summit-schedule/global-search?t=bmw | 15:55 |
| tobiash | and there are a lot of superuser articles from various users | 15:55 |
| corvus | https://zuul-ci.org/users.html | 15:56 |
| tobiash | corvus: was faster :D | 15:56 |
| y2kenny | tobiash: do you happen to still have your slide deck around some where? | 15:58 |
| *** irclogbot_2 has joined #zuul | 15:58 | |
| corvus | y2kenny: https://zuul-ci.org/media/zuul_solution_brief.pdf may also be useful | 15:59 |
| fungi | the foundation design/media folks have also agreed to help update that brochure as soon as we get v4/v5 under wraps | 16:00 |
| corvus | fungi: cool; we should also update it to say open infrastructure foundation :) | 16:00 |
| fungi | er, i mean wrapped up | 16:01 |
| fungi | corvus: yep, that's part of the plan as well | 16:01 |
| fungi | technically the oif doesn't replace the osf until early next year, pending a vote of the members | 16:01 |
| fungi | though stuff's been getting updated in advance on the assumption it will pass the vote | 16:04 |
| *** sshnaidm has joined #zuul | 16:05 | |
| avass | y2kenny: no clue where they are | 16:05 |
| avass | :) | 16:05 |
| avass | y2kenny: sure we could send you those | 16:05 |
| y2kenny | avass: thanks! | 16:06 |
| *** irclogbot_2 has quit IRC | 16:11 | |
| *** irclogbot_1 has joined #zuul | 16:13 | |
| jfoufas1 | y2kenny mail send in your direction | 16:16 |
| jfoufas1 | It would be cool if you joined | 16:17 |
| y2kenny | jfoufas1: mail received. Thanks! | 16:18 |
| *** jfoufas1 has quit IRC | 16:20 | |
| fungi | y2kenny: if you're able to talk about your use of zuul, i can get you in touch with someone who would love to interview you and put together an article around that, or if you write an article or blog post somewhere we can also link it on the users page | 16:21 |
| y2kenny | fungi: I am in touch with some of the folks from OIF/OSF already. I don't think I am ready to do a full blown talk/blog just yet but I planned to when the infrastructure stablizes. My ultimate goal is to have a public facing Zuul infra supporting our open source linux software stack (with GPUs and such.) Actually having a security model and | 16:25 |
| y2kenny | consideration was one of the key reason I picked Zuul. | 16:25 |
| fungi | y2kenny: that's awesome, and yes if you're already talking to foundation folks then they're almost certainly the same ones i would put you in touch with anyway. great to hear! | 16:27 |
| *** mach1na has quit IRC | 16:30 | |
| *** wuchunyang has joined #zuul | 16:34 | |
| *** wuchunyang has quit IRC | 16:39 | |
| pabelanger | So, I am looking at ZUUL_SIBLINGS and siblings logic in build-container-image roles. We have a need to know the type of sibling we are going to build, so far the logic is around python projects only. I wonder if people think it would be okay to rework siblings into a dict, having name and type | 16:57 |
| *** jcapitao has quit IRC | 16:57 | |
| pabelanger | we plan on using it in ansible, for building container images, and siblings could be python or ansible collection | 16:58 |
| fungi | that seems reasonable on its face, i assume the type key would identify some specific alternate behavior... could you elaborate on an example behavior difference? | 16:59 |
| pabelanger | yes, that is right. Rather then the assemble script being only wheels, it would allow for usuage of ansible-galaxy CLI tool, to install a collection | 16:59 |
| pabelanger | my other though, is just to introspect the folder and look for key files, and assume when found, call python setup.py or ansible-collection build | 17:00 |
| fungi | probably the hard part is figuring out which current behaviors need to be rolled into the "python" type, and which are general | 17:00 |
| pabelanger | yah | 17:01 |
| fungi | though maybe that could be done iteratively if python remains the default value | 17:01 |
| *** rpittau is now known as rpittau|afk | 17:01 | |
| fungi | you just move more tasks into python type conditionals as you find conflicts with each new type | 17:02 |
| pabelanger | corvus: do you mind adding https://review.opendev.org/c/zuul/zuul-jobs/+/763836 to your review pipeline, more changes to switch to container_images logic | 17:07 |
| *** jpena is now known as jpena|off | 17:11 | |
| avass | I was gonna review it but realized I'd already done that | 17:12 |
| corvus | avass, pabelanger: i don't think docker_images->container_images is necessarily simple. the data structures are different, and the docker build roles expect docker_ | 17:16 |
| pabelanger | corvus: yes, I don't plan on touching docker build images moving forward. I was under the assumption, those roles would be eventually removed in favor of generic container roles | 17:17 |
| corvus | pabelanger: i think you either need to contemplate a global migration across all the variable names, or have the intermediate registry handle both | 17:18 |
| corvus | pabelanger: i was not under the assumption that the docker roles were deprecated | 17:18 |
| pabelanger | oh, okay | 17:18 |
| pabelanger | then let me back up, and explain the issue I would like to fix | 17:19 |
| corvus | pabelanger: i would also expect the intermediate registry roles to do something with the 'registry' parameter.... | 17:19 |
| pabelanger | Today, we have to only supply https://github.com/ansible/ansible-runner/blob/devel/.zuul.d/jobs.yaml#L18 to publish images via push-to-intermediate-registry. I was hoping to remove that in jobs. | 17:19 |
| *** ashbullock has joined #zuul | 17:21 | |
| corvus | pabelanger: sounds good. my suggestion would be to resolve the ambiguity with the registry parameter (if any) and have the intermediate registry roles support both | 17:21 |
| pabelanger | is there a preference on which one gets priority? | 17:23 |
| corvus | pabelanger: and maybe we'll deprecate the docker roles eventually? i just don't think it's been an explicit plan (yet) since they're so different | 17:23 |
| corvus | pabelanger: how about both? :) | 17:23 |
| corvus | [a]+[b] | 17:23 |
| pabelanger | oh | 17:23 |
| pabelanger | yah, we can do that | 17:23 |
| pabelanger | I'll update my change to do that | 17:23 |
| pabelanger | and remove the 'deprecated' warning | 17:23 |
| corvus | ++ | 17:23 |
| pabelanger | thanks! | 17:24 |
| openstackgerrit | Albin Vass proposed zuul/zuul master: Throw a warning if the executors ssh-key can't be loaded https://review.opendev.org/c/zuul/zuul/+/764584 | 17:27 |
| avass | ^ that changes an error to a warning since ssh-keys are not needed for executors if you're not using ssh :) | 17:28 |
| avass | I had to install a dummy key just to let the executor start, but it works fine with that change | 17:29 |
| *** sanjayu__ has quit IRC | 18:04 | |
| ashbullock | hey, question regarding parent relationship for the github driver, we're trying to setup a parent relationship between jobs and are expecting to see a dictionary var passed through from the parent job to the child job, but when we print out the vars of the child job we can't see the parent's dictionary, is there something we are missing? | 18:09 |
| ashbullock | this is our zuul config http://paste.openstack.org/show/800595/ | 18:13 |
| pabelanger | any reason you are using extra-vars over vars? | 18:14 |
| avass | ashbullock: how are you passing the variabel? | 18:16 |
| ashbullock | the role we're using for the zuul return is here: http://paste.openstack.org/show/800596/ | 18:16 |
| avass | ah as I thought | 18:16 |
| avass | the documentation for zuul_return is a bit confusing since what it does is pass variables to a dependent job and npt what I'd call child job | 18:17 |
| avass | if you need to pass variables to an inheriting job you can use set_fact with cacheable: true | 18:17 |
| *** rlandy|PTO is now known as rlandy | 18:18 | |
| avass | ashbullock: https://docs.ansible.com/ansible/latest/collections/ansible/builtin/set_fact_module.html#parameter-cacheable | 18:18 |
| pabelanger | Oh, I didn't understand properly, I thought pipeline_test was missing | 18:18 |
| avass | we should probably go through the documentation and reword that to make it clearer it's for dependent jobs and not inheriting jobs | 18:19 |
| ashbullock | avass ah ok so we should use set fact with cacheable set to true? and not use the zuul return? | 18:21 |
| avass | ashbullock: yeah | 18:22 |
| ashbullock | just going to try that now, when would you use the zuul return? | 18:23 |
| avass | zuul_return is used for jobs that have uses: https://zuul-ci.org/docs/zuul/reference/job_def.html#attr-job.dependencies | 18:23 |
| pabelanger | you can use zuul_return, but you need to read the file manualy from executor | 18:24 |
| pabelanger | fact cache is likely easier | 18:24 |
| avass | but zuul_return also allows you to comment on changes, report artifacts to zuul that gets displayed on the build page and other things as well | 18:24 |
| avass | yeah or you could also just write a file and read in the inheriting job | 18:25 |
| avass | pabelanger: you should probably not use zuul_return for that thought unless you want a dependent job to be able to see those variables as well | 18:27 |
| pabelanger | ++ | 18:28 |
| *** sanjayu__ has joined #zuul | 18:36 | |
| openstackgerrit | Albin Vass proposed zuul/zuul master: Clarify zuul_return variables https://review.opendev.org/c/zuul/zuul/+/764992 | 18:44 |
| avass | ashbullock, corvus: how about we do something like that ^ ? | 18:44 |
| avass | fungi: I believe you commented on this recently as well | 18:44 |
| fungi | avass: ooh, thanks for the reminder. i summed up my concerns in a comment on ps3 for https://review.opendev.org/764499 | 18:45 |
| avass | I think we've had enough people that has been confused about zuul_return to make that a bit clearer, including me | 18:45 |
| *** vishalmanchanda has quit IRC | 18:46 | |
| openstackgerrit | Albin Vass proposed zuul/zuul master: Clarify zuul_return variables https://review.opendev.org/c/zuul/zuul/+/764992 | 18:47 |
| fungi | yeah, was wanting to bring up the larger topic with folks this week when more people are around | 18:48 |
| avass | also it looks like I'm bad at spelling dependent :) | 18:49 |
| openstackgerrit | Albin Vass proposed zuul/zuul master: Clarify zuul_return variables https://review.opendev.org/c/zuul/zuul/+/764992 | 18:49 |
| avass | I really think having a warning build state for jobs would make it a lot easier to deprecate things | 18:51 |
| fungi | as basically an alternate label for SUCCEESS? | 18:52 |
| avass | yeah | 18:52 |
| fungi | that's a compelling idea | 18:52 |
| avass | would make it easy to deprecate jobs in zuul-jobs if you could do zuul_return: warning: "This behaviour is deprecated...." | 18:53 |
| avass | and that could probably be used internally in zuul too | 18:53 |
| fungi | and be used to expose an admonition on the build result page | 18:54 |
| fungi | ideally with more detail | 18:54 |
| avass | yup, it would be more visible than sending a mail to zuul-announce | 18:54 |
| avass | and not as intrusive as commenting in github/gerrit | 18:55 |
| fungi | if there's a way to free-form explain why something is deprecated on the build result page, then it seems useful (and having a custom alternate for SUCCESS result could then make sense). obviously just saying "this behavior is deprecated" with no way to explain why and what you should use instead isn't as helpful | 18:55 |
| avass | yep :) | 18:56 |
| avass | that's what I mean | 18:56 |
| corvus | avass: good change; see discussion on https://review.opendev.org/764499 | 19:05 |
| corvus | avass: (that was re https://review.opendev.org/764992 ) | 19:06 |
| corvus | basically two users hit the same confusion at ~ the same time | 19:06 |
| avass | corvus: yeah I saw that the other day | 19:06 |
| corvus | if we do want to rename child_jobs, getting a deprecation warning into v4 would be good timing-wise | 19:07 |
| corvus | (i mean, we can do it at any point, but it seems like it shouldn't be a difficult change, and the timing is good right now) | 19:07 |
| corvus | avass: fungi left a suggestion on 992; let me know if you want me to +w or hold | 19:08 |
| avass | I'll fix it. But can you give a hint of how to create an anchor like that? I don't touch rst often enough to remember it :) | 19:09 |
| corvus | avass: i think it's the label syntax in https://www.sphinx-doc.org/en/1.7/markup/inline.html#cross-referencing-arbitrary-locations | 19:11 |
| fungi | oh, yep, sorry i was headed into a meeting or i would have dropped an example in there | 19:14 |
| avass | I'm a bit confused how to do that with titles containing spaces though | 19:14 |
| *** sshnaidm has quit IRC | 19:15 | |
| openstackgerrit | Albin Vass proposed zuul/zuul master: Clarify zuul_return variables https://review.opendev.org/c/zuul/zuul/+/764992 | 19:18 |
| *** sshnaidm has joined #zuul | 19:18 | |
| avass | left out the link for the heading. I gotta go make some food so if you want to you can fix that and merge it | 19:19 |
| fungi | if memory serves, you replace spaces with hyphen/minus | 19:29 |
| openstackgerrit | Albin Vass proposed zuul/zuul master: Clarify zuul_return variables https://review.opendev.org/c/zuul/zuul/+/764992 | 19:58 |
| avass | I think I just mesed something up, this seems to work | 19:58 |
| *** sanjayu__ has quit IRC | 20:00 | |
| fungi | should be able to use the draft build to test it | 20:00 |
| *** hasharAway is now known as hashar | 20:14 | |
| *** wuchunyang has joined #zuul | 20:35 | |
| *** wuchunyang has quit IRC | 20:39 | |
| *** ajitha has quit IRC | 21:00 | |
| *** rfolco is now known as rfolcOUT | 21:06 | |
| *** ashbullock has quit IRC | 21:21 | |
| Goneri | Is there any release of Zuul planned? The last minor release was 4 months ago. | 21:35 |
| *** rfolcOUT has quit IRC | 21:48 | |
| corvus | Goneri: yes; we just made a nodepool release (i'm working on the announcement), and we're going to prep for the v4 release soon. it's a minor potentially breaking change for operators so it's a bit special. | 21:49 |
| corvus | Goneri: see https://zuul-ci.org/docs/zuul/reference/releasenotes.html#relnotes-3-19-0 | 21:51 |
| corvus | also https://zuul-ci.org/docs/zuul/3.19.1/reference/releasenotes.html#relnotes-3-19-1 | 21:51 |
| corvus | and i note we still haven't figured out how to get the 3.19.1 release notes showing up in the development section :/ | 21:51 |
| corvus | fungi: ^ did we ever come up with a solution to that? | 21:52 |
| corvus | er not in the development section, sorry, i mean on the running master branch (that first url) | 21:52 |
| Goneri | thanks. | 22:03 |
| *** Goneri has quit IRC | 22:07 | |
| clarkb | corvus: one Idea I had was to generate release notes after scraping all the valid tags/branches for the little release note artifacts and generatign from that set, not sure if its acuatlly possible to do that with reno out of the box though | 22:10 |
| pabelanger | is it just me, or is the language on https://opendev.org/zuul/zuul not english | 22:12 |
| pabelanger | for commits, branch, etc | 22:12 |
| pabelanger | let me move into #opendev | 22:13 |
| corvus | clarkb, fungi: http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2020-07-21.log.html#t2020-07-21T23:17:09 it looks like we had a plan there, and we've done through step 3; we need to step 4-6 (except the branch is already gone so we'll merge the tag) | 22:14 |
| *** hashar has quit IRC | 22:16 | |
| *** Goneri has joined #zuul | 22:27 | |
| fungi | corvus: sorry, tonight was phat si-io/pad see-ew/ho fun, so had to disappear for a while | 22:33 |
| fungi | i worry that the plan from july resulted in some pain... we might want to briefly revisit and make sure we're okay with repeating that, but i think it boiled down to the fact that reno decides where release notes fall in a revision history based on whether it appears prior to a given tag *in the branch it's generating notes for* | 22:34 |
| fungi | so what we discovered is that in a multi-branch project reno will generate different sets of notes for each branch | 22:35 |
| corvus | fungi: oh i have no plan to repeat that :) i'm looking at finishing it | 22:35 |
| fungi | oh, okay | 22:35 |
| corvus | like i don't think we did steps 4-6 in july | 22:36 |
| *** wuchunyang has joined #zuul | 22:37 | |
| fungi | yep, i'm rereading | 22:37 |
| fungi | okay, so merge a change to remove all new release notes, merge the 3.x bugfix branch into master to get the note and tag from it, then merge a change to add all the 4.0 notes back in? | 22:38 |
| corvus | fungi: yep (though i note the notes have to have new unique ids) | 22:39 |
| fungi | oh, when we revert the removal we need to regen the ids for them? | 22:40 |
| *** wuchunyang has quit IRC | 22:41 | |
| corvus | fungi: yeah, though i was thinking of cheating and just manually incrementing them by 1 | 22:41 |
| corvus | you know, what are the odds? :) | 22:41 |
| corvus | okay, i've done this locally, and need forge committer permission to upload the merge change | 22:42 |
| corvus | "email address review@openstack.org is not registered in your account" | 22:42 |
| corvus | because zuul made merge commits in the 3.x branch | 22:42 |
| fungi | oh, right, pushing merge commits needs forge committer, yes | 22:43 |
| fungi | if you're pushing merges of commits from others not included on that branch | 22:44 |
| corvus | switching to #opendev | 22:46 |
| openstackgerrit | Merged zuul/zuul master: Clarify zuul_return variables https://review.opendev.org/c/zuul/zuul/+/764992 | 23:12 |
| *** aluria has quit IRC | 23:33 | |
| openstackgerrit | James E. Blair proposed zuul/zuul master: Temporarily remove pending release notes in order to merge 3.19.1 https://review.opendev.org/c/zuul/zuul/+/765023 | 23:33 |
| openstackgerrit | James E. Blair proposed zuul/zuul master: Merge tag '3.19.1' https://review.opendev.org/c/zuul/zuul/+/765024 | 23:33 |
| openstackgerrit | James E. Blair proposed zuul/zuul master: Re-add pending release notes https://review.opendev.org/c/zuul/zuul/+/765025 | 23:33 |
| corvus | fungi, clarkb: ^ success! | 23:34 |
| *** aluria has joined #zuul | 23:34 | |
| clarkb | cool so we need to ensure the commits are on a branch first | 23:34 |
| clarkb | that is good to know | 23:34 |
| clarkb | corvus: did you do that with or without extra perms? | 23:34 |
| corvus | yeah; put another way, basically "merge commits generated by gerrit need to be on a branch in gerrit to be ignored in a push" | 23:34 |
| corvus | clarkb: no extra perms for the push | 23:34 |
| clarkb | excellent and thank you for working through that | 23:35 |
| corvus | thanks for your and fungi's help | 23:35 |
| fungi | yeesh, sorry it took so long to arrive at that | 23:37 |
| corvus | zuul-maint: let's check out the doc build on 765025 and if it looks good then i think we can merge those 3 changes and delete the branch | 23:37 |
| fungi | but good to know for future reference | 23:37 |
| corvus | the 3.19.1 relase just keeps on giving | 23:38 |
| openstackgerrit | Merged zuul/zuul master: Don't enforce js whitespace https://review.opendev.org/c/zuul/zuul/+/763568 | 23:39 |
| fungi | also glad to know that's (probably) not related to last week's gerrit upgrade | 23:39 |
| corvus | yeah, we're still in that period where it's easy to get spooked; lots of changes | 23:52 |
| tristanC | corvus: what's the issue with keeping the branch? | 23:56 |
| fungi | branch doesn't need to be "kept" so long as we merge the tags back in *before* removing the branch | 23:57 |
| fungi | merging after the branch is removed causes headaches for gerrit apparently | 23:57 |
| *** tosky has quit IRC | 23:57 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!