GitProtect v1.8.5

🆕 NEW FEATURES

Azure DevOps support

With the 1.8.5 launch, GitProtect allows to back up Azure DevOps data. This means our solution supports all leading git service providers. Similar to GitHub, GitLab, and Bitbucket backup, GitProtect enables cross-restore to and from Azure DevOps. Users can secure both Azure DevOps (SaaS) and Azure DevOps Server (On-Premise) organizations.

Azure DevOps backup

After choosing the Azure DevOps backup plan, user can secure both projects and repositories. During the plan configuration, a user can select one out of four resource types to protect:

• whole organization which is a recommended option,

• projects with possibility to also select individual repositories for each of indicated projects,

• repositories,

• there is also an option to set up rules to back up specific resources

• • name (slug) repository

  • name (slug) project

A user can define which metadata shall be included in the copy. Option to include/exclude individual metadata heavily depends on the selected resource type. The full list of supported metadata is available here.

Azure DevOps restore

Backed-up data can be restored to the same or a new Azure DevOps organization. GitProtect with the cross-over recovery between different git service providers allows for Azure DevOps data to be restored to GitHub, Bitbucket or GitLab organization account. This way you can ensure uninterrupted workflow for Azure DevOps operations even if your service provider (Microsoft) is down. Depending on the selected git service provider, the metadata available for restore may differ. When restoring projects, we restore both the project metadata (e.g. work items) and the repositories that are contained in the project.

During the cross-restore to another git hosting provider, only the repositories and their metadata will be restored. As there is no equivalent of Azure DevOps Project in any of these services, this type of data can not be cross-restored.

GitProtect Backup for Azure DevOps is licensed per number of repositories (sold in packages).

Excluding selected repositories from the backup plan

Responding to the needs of our customers, in version 1.8.5 we have introduced a new mode for selecting repositories to protect within the GitHub, GitLab, and Bitbucket backup plans. A user while selecting an organization to backup also will be able to exclude repositories from backup. After selecting the exclude option the repository table will be displayed. By default, all repositories will be selected, and the user can exclude the repositories that he/she needs. A backup plan configured in this way will protect all repositories from the organization (except the excluded ones). Repositories synced in the future will be also included in the plan.

New GitHub metadata supported

In GitProtect v1.8.5 we added support for:

• commit comments,

• additional repository settings elements: “Is template repository” and “Automatically delete head branches”.

🔨 IMPROVEMENTS

Organization dashboard with the new look - GitHub, Bitbucket, GitLab and Jira

Editable organization name

By default, GitProtect uses and displays the original organization name. From v1.8.5 users can edit this name according to their needs. The change works for all types of git organizations: GitHub, GitLab, Bitbucket, and Azure DevOps.

Unified view of repository names

Since version 1.8.5, the repository name field displays the actual name of the repository, not the slug (path). For those who have found this old feature useful, we have also added a new slug field to the repository table, which is also supported by the filtering/searching mechanism. To turn it on go to the table configuration icon.

Branch protection rules with extended support

Until now, it wasn't possible to secure branch protection rules with references to private GitHub App applications in their settings while using the GitHub authorization method. Version 1.8.5 introduces a mechanism that allows to detect such cases and use Personal Access Token to secure problematic settings instead.

Improved task package queuing

Running conflicting task types (e.g. deleting and restoring data from the same datastore) will be visible as queued tasks in the Tasks “In progress” tab. Now they are always run in descending order. In the past, some tasks were queued in the background and hence were invisible to the users. Now this problem is fixed.

Webhook URIs validation improved (in Management Console)

Parameters like single quote, brackets, exclamation mark, and asterisk are not supported as they result in incorrect validation of the webhook address. However, in the past, if a user used e.g an exclamation mark it didn’t result in displaying an appropriate error information. We have fixed it.

AWS S3 storage usage data

Version 1.8.5 offers improved data processing of used storage space for AWS S3 and S3-compatible data stores.

RAM usage optimization

In this release, we optimized processes that used a large amount of RAM resources.

🐛 BUGFIXES

Child-issues restore in team-managed projects

A bug that caused child-issues not to be granularly restored from team-managed projects (next-gen) is now fixed.

Incorrectly displayed number of tasks in progress

In the case of running tasks in the quantity 10+, we displayed an incorrect value in the panel (max 10), even though there were, in fact, more ongoing tasks run. Now this problem is fixed. The value displayed in the menu corresponds to the actual number of active tasks in the Task section.

No task statistics in the calendar of the resource dashboard

This bug is now fixed. Statistics on the calendar are displayed correctly regardless of the Xopero Management Service operation model.