[OpenStack-Infra] [infra] Request to remove remote branches
Elizabeth K. Joseph
lyz at princessleia.com
Wed Jul 29 19:38:52 UTC 2015
On Wed, Jul 29, 2015 at 2:48 AM, Yanis Guenane <yguenane at redhat.com> wrote:
> Hello,
>
> This morning due to a mis-configuration in one of my tool a branch has been pushed to 4 projects it shouldn't have.
>
> Branch name:
>
> * msync_automatic_update
No problem. I'll also include the sha tip of each below in case there
are any issues and we need to work to revert any deletions.
> Projects Impacted :
>
> * openstack/puppet-ceilometer
Done.
5c66f6b4cd148af397755e353d0d7811a37d7eed
> * openstack/puppet-cinder
Done.
84141dfab6643d6362167833a778bed49c95cee7
> * openstack/puppet-designate
Done.
af714071d293ac450b22f4deeb2443a25d997ada
> * openstack/puppet-glance
Done.
953ae932167f709b9dfb126f1cc1acf7adb6eaf4
And I'd echo Andreas' recommendation that a puppet-manager-release
team be added to the openstack-infra/project-config repo in the
gerrit/acls/openstack/puppet-modules.config file (see other ACLs for
examples) if the team wishes to reduce the risk of this happening by
having a designated release team rather than all cores able to add
branches.
--
Elizabeth Krumbach Joseph || Lyz || pleia2
More information about the OpenStack-Infra
mailing list