SCM Backup

SCM Backup 1.7.0 is available. One new feature: New configuration setting includeRepos: lets you specify a list of repos, only these repos will be backed up, all others will be ignored ⇒ Documentation

SCM Backup 1.6.0 is available. Changes: SCM Backup can detect (and optional delete) repos that were deleted from the hoster, but still are in the local backup dir ⇒ Documentation Backing up repos whose name ends with . is now possible

SCM Backup 1.5.3 is available to download. Changes: Logging improved under the hood. Loggers can now: backup their configuration files execute code when SCM Backup exits (which simplifies the code for the Emailing output feature)

SCM Backup 1.5.2 is available to download. Changes: Fix Bitbucket errors caused by Mercurial repos (2 months after Bitbucket’s Mercurial deprecation, their API still returns Mercurial repos but cloning/pulling them fails -> ignore them) Show operating system on startup

SCM Backup 1.5.1 is available to download. One bugfix: Detecting if Mercurial is installed and determining the version number now works on non-English systems as well

SCM Backup 1.5.0 is available to download. Changes: Backing up Bitbucket workspaces is now fully supported ⇒ Documentation Note: Bitbucket will make breaking API changes on October 14, which unfortunately means that backing up from ... [More] Bitbucket with all SCM Backup versions < 1.5 won’t work anymore! Process exit code is set to 0 on success and 1 on failure (thanks to nzbart for contributing this) The subject of the generated email now contains “Success” or “Failure” [Less]

SCM Backup 1.4.1 is available to download. There is only one change: Backing up repositories owned by a user from Bitbucket is working again (repositories owned by teams were not affected). What happened? Last year, Bitbucket made some ... [More] breaking changes in their API because of GDPR, and I had to release a bugfix version where I changed the API calls for getting a list of a user’s repos. The solution worked fine until a few days ago, when the API call I added last year started returning 404s. I contacted Bitbucket support, and according to their answer, that API call should have been deprecated last year as well, but accidentally was left working. Now they noticed it and removed it, and advised me to use a different call. [Less]

SCM Backup 1.4.0 is available to download. Changes: Passwords can now be taken from environment variables instead of saving in clear text in the config file (docs / issue)

SCM Backup 1.3 is available to download. Changes: New: GitLab support Updated to .NET Core 3.1 Updated all dependencies

SCM Backup 1.2.2 is available to download. Changes: Bugfix: Emails can now be sent to multiple recipients Fixed an integration test