Last modified: 2014-10-16 12:47:30 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T48982, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46982 - Announce all creations, deletions and renaming of gerrit repos (for e.g. translatewiki.net workflow)
Announce all creations, deletions and renaming of gerrit repos (for e.g. tran...
Status: NEW
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
wmf-deployment
All All
: Low major (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-07 09:39 UTC by Siebrand Mazeland
Modified: 2014-10-16 12:47 UTC (History)
10 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Siebrand Mazeland 2013-04-07 09:39:27 UTC
Creation, deletion and renaming of Gerrit repositories regularly has a very negative impact on the translatewiki.net workflow.

Recently the repo DonationEmailUnsubscribe appears to have been deleted. The repo FundraisingEmailUnsubscribe appears to have been moved from wikimedia to mediawiki, without updating the permissions on the repo, and without updating .gitreview.

Deleting repos causes errors in mass update scripts. They will exit with inexplicable errors, which then means that you have to start chasing ghosts in https://gerrit.wikimedia.org/r/#/admin/projects/
Comment 1 Chad H. 2013-04-08 12:17:28 UTC
(In reply to comment #0)
> Recently the repo DonationEmailUnsubscribe appears to have been deleted. The
> repo FundraisingEmailUnsubscribe appears to have been moved from wikimedia to
> mediawiki, without updating the permissions on the repo, and without updating
> .gitreview.
> 

Permissions didn't need updating, nor did the parent. It was copied incorrectly (mea culpa).

As to the actual bug: what sort of notification are you looking at having? We could probably pretty easily make some public log of repo creations and deletions.

The moving instance was a special case, and has happened like once, ever.

Once actual moving support goes in upstream, one would assume we could log that too.
Comment 2 Siebrand Mazeland 2013-04-08 12:31:32 UTC
(In reply to comment #1)

> what sort of notification are you looking at having? We
> could probably pretty easily make some public log of repo creations and
> deletions.

Anything but the current silence in a discoverable location.
Comment 3 Andre Klapper 2014-03-13 12:56:10 UTC
(In reply to Chad H. from comment #1)
> Once actual moving support goes in upstream, one would assume we could log
> that too.

So this is blocked on upstream? Any ticket URL to follow there?
Comment 4 Andre Klapper 2014-10-16 12:47:30 UTC
I assume upstream is https://code.google.com/p/gerrit/issues/detail?id=560

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links