GitProtect v. 1.4.5 is now available! The first big change is easy to spot right after logging in (of course, after updating the application first). Just a small spoiler in the intro: in addition to daily reports, e-mail, and Slack notifications, your daily work will now be improved by a completely new system dashboard.<\/p>\n\n\n\n\n\n\n\n
The system dashboard presents statistical data on performed tasks, recent backup tasks, and notifications. There is also a completely new element – the SLA section. This new view provides details about how secure all your resources, including GitHub, Bitbucket, GitLab, and Jira organizations, are. <\/p>\n\n\n\n
Now you can select a custom time range: the last 24 hours or over 7, 14, and 30 days. I know that such information is crucial for you \u2013 and there is more to come. But I will tell you more about it another time. <\/p>\n\n\n\n
Does your organization use Azure Active Directory, Okta, or CyberArk? If so, you will be pleased to hear that GitProtect now supports external identity providers using the SAML (Security Assertion Markup Language) standard. The new service is available from the System Administrator level – from here you can easily add, modify and remove external identity providers.<\/p>\n\n\n\n
The number of metadata which you can backup (and restore of course too) is constantly growing. We are happy to announce that GitProtect now supports also pipeline schedules, pipeline known hosts, branching model, branch restrictions, and pipeline settings. <\/p>\n\n\n\n
We made changes within the git restore process, which I\u2019m sure you will appreciate. From now on in the second restore step – when the repositories and backup versions to restore are selected \u2013 you can choose which type of organization to restore the data to (GitHub, GitLab, Bitbucket) or which device. <\/p>\n\n\n\n
From now on you can display a list of repositories in the organization while clicking the Explore button (previously Manage&Restore). We also provide you with a restore shortcut. The Recovery button gives you a new (super)power \u2013 you get a complete list of repositories in your organization and an additional restore aside, which is ready to put your critical resources there. How to do it? To choose a repository to restore, tick the checkbox. Your repo will be automatically added to the restore step (with the last available version already chosen). <\/p>\n\n\n\n
In the previous release, the functionality of the groups was expanded and they gained e.g. their own dashboards. Now we have powered up the mentioned dashboards with a new set of data presenting the storage usage by all devices within that specific group. <\/p>\n\n\n\n
The central theme of this release is the dashboard(s). In this case, the new section presents how backup task duration changes over time for the specific plan.<\/p>\n\n\n\n
With what kind of copy we are dealing with (full, differential, or incremental), during its execution, after it is finished, as well as in the logs.<\/p>\n\n\n\n
We have great news for all our Italian users. From this release, GitProtect is also available in Italian! So now, our app supports six languages: English, Polish, Spanish, Ukrainian, Mandarin (traditional and simplified), and, of course, Italian.<\/p>\n","protected":false},"excerpt":{"rendered":"
GitProtect v. 1.4.5 is now available! The first big change is easy to spot right after logging in (of course, after updating the application first). Just a small spoiler in the intro: in addition to daily reports, e-mail, and Slack notifications, your daily work will now be improved by a completely new system dashboard.<\/p>\n","protected":false},"author":3,"featured_media":3886,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,3,70,73,5],"tags":[],"class_list":["post-3885","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bitbucket","category-github","category-gitlab","category-jira","category-news","post--single"],"yoast_head":"\n