GitProtect 1.8.0
🆕 NEW FEATURES
Welcome view
We have completely redesigned the onboarding process for new users. When logging in for the first time, the user is directed to a new screen that presents all available resources that can be secured with GitProtect. By default, a new user can connect a service with GitProtect using a simple three-step process. However, if a SaaS organization requires authorization via login, token, or GitHub App, the previous advanced mode is still available.
Context menu
The upper blue bar (which contains the context menu for the currently visible subpage) has also been updated. It now allows quick configuration of a new backup plan and adding new services to protect. The language setting has been moved to the User actions, and an easy option to upgrade or purchase licenses is now available.
Default backup plan
To enhance the security of user data, encryption is now enabled by default for every new backup plan. A default encryption key is generated for this purpose, which can be viewed only once at the time of creation.
Backup plan configuration
For each supported ecosystem and service, GitProtect offers a dedicated type of backup plan. Starting from version 1.8.0, users can choose between backup plans for physical devices, VMware, or Hyper-V, as well as SaaS services such as Microsoft 365, GitHub, Bitbucket, GitLab, and Jira. Each plan can then be configured according to the security policies of the organization.
GitHub Classic Projects to V2 Projects conversion tool
We have introduced a mechanism that converts classic GitHub projects to V2 projects. If a backup contains classic projects, they will be converted to the V2 format during the restore process.
🔨 IMPROVEMENTS
Optimized performance for Jira granular restore
Version 1.8.0 introduces additional optimizations to the Jira granular restore process. This release focuses on improving the performance of incremental backups when granular restore is enabled.
Improved configuration of additional accounts in the GitHub, Bitbucket, and GitLab organizations
We have noticed that some users only partially configure the throttling mechanism for Git organizations. In these cases, the process ends after adding an additional account or GitHub App. For this reason, we added information to the configuration process that reminds users to edit the backup plan afterward.
Performance improvements and SaaS service autoscaling
With this release, we address issues related to insufficient RAM allocation. When there is not enough RAM to perform an operation, the service will automatically request additional resources. In the initial phase, this mechanism operates in manual mode: the service sends the request automatically, but the resources are assigned only after user approval. Additionally, we have introduced optimizations that improve the release of used RAM, reducing overall consumption.
Time zone support in backup plans
GitProtect users can now set the time zone within the backup plan schedule, ensuring that all future tasks are launched according to the selected time zone. This improvement eliminates the need to manually adjust the time zone during winter or summer time changes.
Support for the GitHub merge settings
GitProtect now supports backing up and restoring merge settings in GitHub repositories, including commit merge settings, default commit merge messages, squash merge settings, and rebase options.
Restore of GitHub outside collaborators metadata from a backup copy
Users can now restore external collaborators added to GitHub repositories. Please note that this operation has certain limitations, as GitHub allows restoring a maximum of 50 external users.
Restore of Bitbucket repository details from a backup copy
We have expanded the range of supported metadata in Bitbucket repositories for selected programming languages, websites, and forking settings.
SLA reports available through Slack notifications
GitProtect now offers a new type of Slack notification: the SLA report is ready for download.
🐛 BUGFIXES
Possible Management Service freezes
The error occurred only when the Git organization sync and daily report generation were running at the same time. Starting from version 1.8.0, this issue has been resolved.
Problem with securing GitLab resources for 10k pull requests or issues
The issue was caused by incorrect behavior in the GitLab API when downloading pull requests and issues for repositories containing more than 10,000 items. This problem has been resolved, and GitProtect now correctly protects repositories with over 10,000 issues or pull requests.
Issue with securing a very large number of GitHub pull requests
The issue occurred only with pull requests and their comments when the data size exceeded 2 GB. This has been fixed.
Problem with restoring GitHub issue with long descriptions
The issue occurred only when restoring an issue with a description longer than 65,536 characters. Starting from version 1.8.0, descriptions exceeding this limit are truncated to the maximum allowed length.
Issues with securing GitLab groups with incorrectly configured push rules
The issue occurred only when a GitLab group had an unexpected null value in the Do not allow users to remove Git tags with git push rule. This has been fixed.
Jira granular restore of issues from an incremental backup copy not working
During testing, our team discovered that in certain scenarios, GitProtect could not granularly restore issues stored in an incremental backup when restored to an empty project and backed up again under a new backup plan. This issue has been fully resolved.
Last updated