• BitUp is an application to backup git repositories from Bitbucket.
• It is possible to store all repositories of specific Bitbucket Teams in Azure File Storage or to save them locally.

First you need to generate api keys for every team. To do that navigate to the team page and click on the button in the upper right corner "Manage team". The keys are needed to configure the application.

The next step is to create an Azure Storage Account. Go to the Azure Portal and sign in. Now you can navigate to "Storage accounts (classic)".

Here click "Add" to add an storage account.

Give it a unique name, change settings and click "Create".

Now you can add a storage container clicking on the created storage account then "Overview" --> "Files" --> "+ File share". Choose a name for the storage container, set a sufficient quota (to limit max size) then click "Create".

You find the key needed for the config file at "Keys" --> "Primary Access Key".

Edit the DataOne.BitUp.exe.config file.

0. BitbucketTeams: A collection of strings with all names of teams to backup the repositories of. A string consists of the team's ID and the API-Key of it, separated by a semicolon.

1. AzureStorageContainer: The name of an Azure Storage Container. It has not to exist but has to fit the naming rules: Azure Storage Naming Rules

2. AzureAccountName: The name of an already existing Azure Storage Account.

3. AzureAccountKey: The primary Key of the specified Azure Storage Account.

4. StoreInAzure: A boolean value on which it depends if the backups will be saved locally or in Azure. Possible values are: True or False.

5. SmtpHost: The smpt host of the mail server you want to use to send the log mail after each run.

6. EmailAccount: An email account with which the log mail will be sent.

7. EmailPassword: The corresponding password of the stated email account.

8. SendMailTo: The email account to receive the log mail.

9. SmptPort: The used port of the smtp host. Default values are 25 or 587, but which one will work depends on the host.

10. MailFrom: The sender of the log mail. It is not needed to change this value.

To run the application locally just execute the DataOne.BitUp.exe.

If you want to use Azure to run it use the following steps to create a Web Job.

0. Create a zip file containing all files from the original DataOne.BitUp.zip but where you changed the settings in the config file as you need them.

1. Navigate to "App Services" in the Azure Portal.

   • 

2. Add a new Web App (or use an existing one).

   • 

3. Choose an unique name for your App and click "Create".

   • 

4. Navigate to "WebJobs" and click "Add".

   • 

5. Give it a name and upload the DataOne.BitUp.zip file containing the updated config file.

   • Choose type "Triggered" and decide when you want the application to run.
   • To run it manually set "Triggers" to "Manual".
   • To run it at a specific time set "Triggers" to "Scheduled" and specify a valid CRON expression.
   • 

6. If you set "Triggers" to "Manual" you can run the Web Job with a click on "Run" as shown in the next picture.

   • 

After a run you find your repository backups in the Azure Storage Container or in a local directory ./DataOne.BitUp.RepositoryBackups if you ran the application locally.

Note that only repositories that changed since the last run (assumed that it was 24 hours ago) will get backed up!