[infra][release] delete old EOL'd stable branches
hberaud at redhat.com
Wed Jan 27 10:53:30 UTC 2021
Le mer. 27 janv. 2021 à 11:51, Előd Illés <elod.illes at est.tech> a écrit :
> Thanks Jeremy and Hervé!
> @Jeremy, @Hervé: I've checked and found two open patches, out of which I
> was able to abandon one, and asked the owner on the other patch to abandon
> it. So the listed branches can be deleted *except* one:
> So in my opinion there's no need for further coordination with the teams,
> as these branches are tagged ocata-eol already.
Yes indeed, I agree.
> And thanks Hervé for the script, it helped a lot so far, already :) +
> thanks Jeremy for the pointers!
> On 2021. 01. 27. 11:23, Herve Beraud wrote:
> Le mar. 26 janv. 2021 à 18:35, Jeremy Stanley <fungi at yuggoth.org> a
> écrit :
>> On 2021-01-26 17:52:07 +0100 (+0100), Előd Illés wrote:
>> > 1. I've used the list_eol_stale_branches.sh  script to get the list
>> > such not-yet-deleted branches for Ocata . They are all tagged with
>> > 'ocata-eol', but stable/ocata branch still exists for them. Could you
>> > delete these? 
>> I'm happy to, have you made sure any open reviews for those branches
>> are abandoned first? Gerrit won't allow deletion of a branch with
>> open reviews.
> I think we need a first round of inspection on these stale branches to see
> if opened patches exist and then if needed start discussion with teams to
> ask them to drop the patches those who have been found.
> I'll try to add this feature to check for opened patches within
>> > 2. On the Release Team meeting  we were hinted that with the newer
>> > version of gerrit (that was installed at the end of November) some
>> > automation is possible through gerrit API in the future. Can I get some
>> > about where should I start with the automation? Which repository should
>> > look, where can the deletion being triggered ("similarly like branch
>> > creation")?
>> The Gerrit REST API method for deleting branches is documented here:
>> I'm not immediately sure where branch creation happens in the forest
>> of our release automation, but I would expect deletion could be
>> implemented similarly. Hopefully someone more intimately familiar
>> with those jobs can chime in.
>> The access control we'll need to grant to automation so that it can
>> call that is documented here:
>> It'll need to be added manually as a permission for the Release
>> Managers group in our All-Projects global ACL which individual
>> projects inherit, and this documentation updated accordingly:
>> Happy to answer other questions as they arise.
>> Jeremy Stanley
> Hervé Beraud
> Senior Software Engineer at Red Hat
> irc: hberaud
> -----BEGIN PGP SIGNATURE-----
> -----END PGP SIGNATURE-----
Senior Software Engineer at Red Hat
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openstack-discuss