Tuesday, 2021-01-05

*** tosky has quit IRC00:05
*** prometheanfire has quit IRC02:24
*** prometheanfire has joined #openstack-release02:25
*** armax has quit IRC02:47
*** tbarron has quit IRC02:52
*** diablo_rojo has quit IRC03:28
*** ykarel has joined #openstack-release04:26
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-release05:33
*** whoami-rajat___ has joined #openstack-release05:36
*** ricolin has joined #openstack-release06:59
*** ricolin has quit IRC07:18
*** rpittau|afk is now known as rpittau07:33
*** slaweq has joined #openstack-release07:42
*** sboyron has joined #openstack-release07:53
*** tosky has joined #openstack-release08:39
hberaudfungi: o/ FYI finally I think we need some update on zuul's side, indeed some projects doesn't have docs but use reno but this rule isn't reflected by zuul, cf. this example => https://review.opendev.org/c/openstack/tripleo-heat-templates/+/76926308:53
hberaudfungi: so to match our need I voluntarily added a doc/requirements.txt even if this project doesn't contains doc, but this is not an elegant solution08:55
hberaudI think it would be preferable to properly handle this case in https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L3608:55
hberaudby adding "releasenotes/requirements.txt" before the default case08:56
*** sboyron_ has joined #openstack-release09:04
*** sboyron has quit IRC09:04
*** sboyron_ has quit IRC09:06
*** sboyron_ has joined #openstack-release09:07
hberaudfungi: the releasenotes playbook will call ensure-sphinx ^ so we will pull our requirements from there even with reno => https://opendev.org/zuul/zuul-jobs/src/branch/master/playbooks/releasenotes/pre.yaml#L609:14
hberaudfungi: I just proposed a related patch on zuul => https://review.opendev.org/c/zuul/zuul-jobs/+/76929209:28
*** jbadiapa has joined #openstack-release09:35
*** tkajinam has quit IRC09:42
*** e0ne has joined #openstack-release10:00
*** rpittau is now known as rpittau|bbl10:32
*** e0ne has quit IRC10:54
openstackgerritMark Goddard proposed openstack/releases master: Release kolla deliverables Victoria RC2  https://review.opendev.org/c/openstack/releases/+/76932211:17
openstackgerritMark Goddard proposed openstack/releases master: Release kolla deliverables for Ussuri  https://review.opendev.org/c/openstack/releases/+/76932411:32
openstackgerritMark Goddard proposed openstack/releases master: Release kolla deliverables for Train  https://review.opendev.org/c/openstack/releases/+/76932511:43
openstackgerritMark Goddard proposed openstack/releases master: Release kolla deliverables for Victora  https://review.opendev.org/c/openstack/releases/+/76932811:48
*** e0ne has joined #openstack-release11:57
*** sboyron_ has quit IRC12:07
*** sboyron_ has joined #openstack-release12:07
*** tbarron has joined #openstack-release12:32
*** rpittau|bbl is now known as rpittau12:44
*** sboyron_ has quit IRC13:08
*** sboyron_ has joined #openstack-release13:09
*** whoami-rajat___ is now known as whoami-rajat__13:16
yoctozeptorelease-core: dears, please kindly review our kolla releases, thank you! ^14:12
*** tosky has quit IRC14:15
*** tosky_ has joined #openstack-release14:16
*** tosky_ is now known as tosky14:16
ttxhberaud: see https://review.opendev.org/c/openstack/project-config/+/769353 following our discussion Monday14:30
hberaudttx: thanks14:31
fungihberaud: got it, so the release tools were trying to build release notes for projects with no docs?14:34
hberaudyoctozepto: ack, we will have a look, but we currently face some issues with doc/reno jobs, however kolla isn't in the list of impacted projects (c.f http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html). ttx: FYI I think we can go ahead with these projects, any opinions?14:35
hberaudfungi: it's depend... some projects yes some other not14:36
hberaudfungi: I found few projects that build release notes without any docs14:37
hberaudso I think this use case should be handled too14:37
fungiand also have broken test-requirements.txt files?14:37
fungiokay, so they're not affected by the current problem then?14:38
hberaudnormally yes14:38
hberaudbut I didn't tested all of them14:38
hberaudhowever I think it could be worth to allow to split reqs for reno like we already do for docs14:41
hberaudelse projects need to pull everything just to build release notes and that increase the likelihood to face a resolver issue14:42
yoctozeptohberaud: thanks :-)14:42
hberaudand with that we limit the chances to get simialr side effects on our release pipeline14:44
openstackgerritThierry Carrez proposed openstack/releases master: Website: Add link to the git repository  https://review.opendev.org/c/openstack/releases/+/76935514:44
fungihberaud: sure, i agree being able to override and specify releasenotes/requirements.txt might be helpful to projects who just build release notes14:44
fungiso it would be searched in this order: doc/requirements.txt releasenotes/requirements.txt test-requirements.txt14:44
hberaudyes, that what I proposed in my patch14:46
hberaudalso another option could be to override the "Get requirements files" only for the releasenotes playbook instead of inherit everything from the ensure-sphinx role14:49
fungiahh, cool, for some reason i didn't see gerritbot echo that one14:49
hberaudfollowing this way could allow us to limit the side effect on the doc side14:49
hberaudbut for now I think that these changes solve 98% of our problem14:50
hberaudmy main concern is what will happen if doc/requirements doesn't exist but if the project build doc anyway...14:52
*** armax has joined #openstack-release14:57
fungiwell, as you noted, 769292 isn't going to fix any of the failing release notes builds because you say the projects building release notes with no doc/requirements.txt files don't have broken test-requirements.txt files14:57
fungiif the project builds docs then doc/requirements.txt *should* exist because the pti says so14:57
hberaudyes good point14:57
fungii don't think the release team needs to worry about alternatives to that case, if projects don't follow the pti then the release jobs can't support them14:58
fungiand the release jobs shouldn't get unnecessarily complicated in order to support projects not following guidelines14:58
hberaudI was not sure to cover 100% of the case so I prefered to think about this particular use case14:59
*** yoctozepto has quit IRC15:43
*** yoctozepto has joined #openstack-release15:44
*** sboyron_ has quit IRC15:51
openstackgerritMark Goddard proposed openstack/releases master: Release kolla deliverables for Victoria  https://review.opendev.org/c/openstack/releases/+/76932815:52
*** e0ne has quit IRC15:56
*** e0ne has joined #openstack-release15:57
*** sboyron has joined #openstack-release16:02
*** dave-mccowan has quit IRC16:03
*** dave-mccowan has joined #openstack-release16:07
*** sboyron has quit IRC16:17
*** sboyron has joined #openstack-release16:17
*** e0ne has quit IRC16:28
*** e0ne has joined #openstack-release17:00
*** rpittau is now known as rpittau|afk17:08
*** sboyron has quit IRC17:22
*** sboyron has joined #openstack-release17:24
*** ykarel has quit IRC17:36
ttxhttps://review.opendev.org/c/openstack/project-config/+/769353 was merged, so keep an eye open in the very unlikely case it creates a regression.18:01
*** e0ne has quit IRC18:30
*** whoami-rajat__ has quit IRC18:39
*** mgoddard has quit IRC18:45
*** sboyron has quit IRC20:06
*** slaweq has quit IRC20:33
*** dave-mccowan has quit IRC20:37
*** tosky_ has joined #openstack-release22:12
*** tosky has quit IRC22:13
openstackgerritPierre Riteau proposed openstack/releases master: [Tempest Plugins] Tag stein EM  https://review.opendev.org/c/openstack/releases/+/76853822:16
*** tosky_ is now known as tosky22:17
*** tkajinam has joined #openstack-release23:01
*** dave-mccowan has joined #openstack-release23:15

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