##// END OF EJS Templates
docs: added release notes for 4.22.0
docs: added release notes for 4.22.0

File last commit:

r4326:818f6cb9 default
r4521:a111f355 stable
Show More
103 lines | 3.4 KiB | text/x-rst | RstLexer

Common Admin Tasks for Repositories

Manually Force Delete Repository

In case of attached forks or pull-requests repositories should be archived. Here is how to force delete a repository and remove all dependent objects

Below is a fully automated example to force delete repositories reading from a file where each line is a repository name. This can be executed via simple CLI command without entering the interactive shell.

Save the below content as a file named repo_delete_task.py

The code above will read the names of repositories from a file called delete_repos.txt Each lines should represent a single name e.g repo_name_1 or repo_group/repo_name_2

Run this line from CLI to execute the code from the repo_delete_task.py file and exit the ishell after the execution:

echo "%run repo_delete_task.py" | rccontrol ishell enterprise-1

Bulk edit permissions for all repositories or groups

In case when a permissions should be applied in bulk here are two ways to apply the permissions onto all repositories and/or repository groups.

  1. Start by running the interactive ishell interface
2a) Add user called 'admin' into all repositories with write permission.
Permissions can be also repository.read, repository.admin, repository.none
2b) Add user called 'admin' into all repository groups with write permission.
Permissions can be also can be group.read, group.admin, group.none