automated-scanning
Closed, ResolvedPublic
Actions

Assigned To

None

Authored By

	sbassett
	Mar 11 2020, 9:43 PM

Description

Hello Releng-

Would it be possible to delete this repository/project from gerrit? This is the config for some old automated scanning run by former members of the Security-Team. It has not been used in a long time with the last commit being 4+ years ago. The Security-Team has a backup of the repository and would prefer it be deleted to avoid confusion, etc. as part of the work in T246392. Thanks.

Details

	Subject	Repo	Branch	Lines +/-
	Adding README for now-obsolete automated-scanning project	wikimedia/security/automated-scanning	master	+1 -0
	Obsoleting automated-scanning project	wikimedia/security/automated-scanning	master	+0 -2 K

Customize query in gerrit

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Resolved		sbassett	T246392 Reconfigure wikimedia/security/tooling git repository
		Resolved		None	T247468 Delete gerrit repository wikimedia/security/automated-scanning

Event Timeline

sbassett created this task.Mar 11 2020, 9:43 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMar 11 2020, 9:43 PM

sbassett updated the task description. (Show Details)Mar 11 2020, 9:44 PM

sbassett added a parent task: T246392: Reconfigure wikimedia/security/tooling git repository.

sbassett mentioned this in T246392: Reconfigure wikimedia/security/tooling git repository.

sbassett updated the task description. (Show Details)

Yes this can be deleted, though i rather we waited to do that till we upgrade to 2.16. Only because there's a bug which causes spam (fixed with https://github.com/GerritCodeReview/plugins_delete-project/commit/a4dc24fb5c2550ee5f3c0d150cc3c66b3b02b8f0).

Don't we normally empty the repo and put a OBSOLETE or ARCHIVE file compared to deleting in these situations

Yes. I do not understand why to completely "delete" open source code.

In T247468#5962021, @Paladox wrote:

Yes this can be deleted, though i rather we waited to do that till we upgrade to 2.16. Only because there's a bug which causes spam (fixed with https://github.com/GerritCodeReview/plugins_delete-project/commit/a4dc24fb5c2550ee5f3c0d150cc3c66b3b02b8f0).

That is mostly harmless. As far as I know, it just causes some spam in the Gerrit logs :]

+ Projects-Cleanup which we use to archive repositories

@sbassett we usually simply archive the git repositories. Usually done roughly as:

emptying the repo and just leaving README file that would point to this task
mark the repository inactive in Gerrit to prevent further changes.
delete the github mirror

This way the code is archived in Gerrit. Saving your team from having to maintain a backup :]

Dropping Gerrit , those tasks are handled via Projects-Cleanup

Change 579375 had a related patch set uploaded (by SBassett; owner: SBassett):
[wikimedia/security/automated-scanning@master] Obsoleting automated-scanning project

https://gerrit.wikimedia.org/r/579375

gerritbot added a project: Patch-For-Review.Mar 12 2020, 7:19 PM

Change 579375 merged by SBassett:
[wikimedia/security/automated-scanning@master] Obsoleting automated-scanning project

https://gerrit.wikimedia.org/r/579375

Change 579377 had a related patch set uploaded (by SBassett; owner: SBassett):
[wikimedia/security/automated-scanning@master] Adding README for now-obsolete automated-scanning project

https://gerrit.wikimedia.org/r/579377

Change 579377 merged by SBassett:
[wikimedia/security/automated-scanning@master] Adding README for now-obsolete automated-scanning project

https://gerrit.wikimedia.org/r/579377

In T247468#5963266, @hashar wrote:

emptying the repo and just leaving README file that would point to this task

mark the repository inactive in Gerrit to prevent further changes.

delete the github mirror

Thanks for the info. The first item is completed and I've set the repo to read-only via the gerrit UI. Is that different from making it "inactive"? I guess I can also ping @Reedy to remove the github mirror.