BitBucket is a web-based version control solution designed for software development teams. It supports Git repositories to help users manage and collaborate on their projects. Also, developers can track and revert changes, and work on different branches simultaneously. BitBucket offers a range of services, including code review, issue tracking, continuous integration and deployment, and integrations with other software development tools like Jira and Confluence.
Prerequisites
Make sure that you have:
The guide covers the following topics:
1. Sign in to your Bitbucket account.
2. At the top of the page, click Create > Repository. Alternatively, you can click Create repository either in the Recent repositories or Welcome sections.
3. On the Create a new repository page that opens, add the repository details:
4. Click Create repository to create the new repository on Bitbucket.
1. Create an empty folder on the disk of your computer to store the local repository. For example, a bitbucket folder stored on the drive D.
2. Sign in to your BitBucket account, navigate to Repositories on top of the page, and then select the repository you want to clone to your computer.
3. In the upper-right corner of the repository page, click Clone.
4. In the Clone this repository window that opens, select either HTTPS or SSH as the connection protocol, and copy the clone command with the repository URL. HTTPS, which is a default option, supports user/password authentication, and SSH - public key authentication. In our example, we use HTTPS.
Note
When cloning over SSH from a Bitbucket repository, the user’s public key needs to be added to the Bitbucket account and saved on the local computer they are using to clone the repository. This allows for secure authentication between the local computer and the Bitbucket server.
5. Start Windows Command Prompt (CMD). If you need to change the disk drive and navigate to the empty folder you created, in the Command Prompt, use the cd
command.
6. In the Command Prompt, paste the clone command with the repository URL to create a cloned copy of the repository in the local folder (bitbucket in our case). Since the HTTPS protocol has been selected, you will be prompted to enter the username and password to your BitBucket account.
Note
Place a dot at the end of the command to clone the repository to the folder you have created. Otherwise, another subfolder will be created.
If you didn’t add any files to the repository when you created it for the first time, execue the following commands:
git commit --allow-empty -m initial
git push
After you cloned the remote repository to the folder on your local computer, you can link the database to source control using the dbForge Source Control add-in for SSMS.
1. In SSMS Object Explorer, right-click the database you want to link to source control and select Source Control > Link Database to Source Control.
2. In the Link Database to Source Control dialog that opens, click + in the Source control repository field.
3. In the Source Control Repository Properties dialog that opens, do the following:
Note
The repository folder name represents a path to the local copy of the remote repository and must not contain the URL of the remote repository.
5. Optional: Click Test to verify that the database has successfully been connected to source control.
6. Click OK to apply the changes and close the Source Control Repository Properties dialog.
7. In the Link Database to Source Control dialog, select a database development model: dedicated or shared.
7. Click Link to establish the connection between the database and source control.
The Refresh progress window opens automatically, showing the stages of the refresh operation. The linked database gets the following icon in Object Explorer.
If you are the first person who links this database, you must make an initial commit. For this, in Source Control Manager, go to the Local changes section, select the database objects to commit, and then click Commit.
If you linked a database that is already in source control, you can update your database to the latest version. For this, in Source Control Manager, go to the Remote changes section, select the objects, and click Get Latest, which is available only in the dedicated model but not in the shared model.