Repository Backup Based On Rules
Sometimes it happens that you don’t need to back up all the repositories you have in your DevOps ecosystem in bulk. It can be due to different reasons, for example, you have an old repository that you keep only for Compliance purposes, the Shared Responsibility Model of your cloud service provider, SLA, or your organization requires you to back up some repositories more frequently than others. Sounds familiar?
GitProtect.io allows you to specify which git repositories you want to include in the copy while setting up your backup plan. You are free to select all the repositories you have in your GitHub, Bitbucket, or GitLab infrastructure, indicate only those repositories that you need, or define a rule for the repository name.
Depending on the service you use, rule settings can slightly vary:
- If you use GitHub, you can set a rule for the repository names, topics, and groups (SaaS and Enterprise Server).
- When it comes to Bitbucket DC, you are free to set a rule for labels, and for your Bitbucket, it’s possible to define the rule for projects.
- If you use GitLab, you can set a rule for the repository topics and groups (SaaS and Self-managed).
In this case, all the repositories that meet the criteria defined in the rule will be automatically included in the backup task.