Bitbucket Server
Waydev connects to your Bitbucket Server and automatically analyzes your codebase to help you identify issues, improve velocity, and drive productivity up.
The Bitbucket Server integration enables Waydev to provide reports that help you in:
For daily stand-ups, Waydev integrates with Bitbucket Server to provide you with:
For one-on-ones, Waydev integrates with Bitbucket Server to help you with:
For code review, Waydev integrates with Bitbucket Server to provide you with:
For monthly and quarterly reports, Waydev integrates with Bitbucket Server to help you with:
Step 1: On any page of your Bitbucket Server, click the settings icon in the top right.
Step 2: Next, click Users in the left-hand menu.
Step 3: Then, click the Create User button.
Step 4: Fill in the form, taking note of the username and password you use. Then, click Create user.
Step 5: Click Change Permissions.
Step 6: Under Global Permissions, search for your new Waydev user. Once you see your new user in the results select it and click Add.
Step 7: Click the Admin checkbox for the user you just added.
Step 8: On your Waydev homepage, navigate to Project -> Integrations.
Step 9: Select Bitbucket Server.
Step 10: Select the authentication method you want to proceed with:
A.) Username/Password – You can connect to your Bitbucket Server using your Bitbucket credentials under the Username and Password tabs. Insert your credentials, your base URL, and click Test connection.
If the connection was successful you will see the following message:
Success! Please refresh the page.
If you receive an error when trying to connect your Bitbucket Server account verify the following and try again:
If you connected behind a firewall verify the following:
B.) Access Tokens – You can connect to Bitbucket Server via an access token. On the Personal Access Token field insert your access token and click Test connection. For more information on how to create an access token in BitBucket Server see Bitbucket’s support document Personal Access Tokens.
If the connection was successful you will see the following message:
Success! Please refresh the page.
If you receive an error when trying to connect your Bitbucket Server account using an access token verify the access token, the base URL, and try again.
Step 11: Once you have successfully connected to your Bitbucket Server account, click Next.
Step 12: You will be directed to the Repositories page, where you will need to select the repos you wish to import. After you select the repos, click Save Project. You have connected your Bitbucket Server account successfully!
Bitbucket Server is a Git repository management solution hosted on-premise, in your environment. It provides a central place to manage git repositories, collaborate on your source code, and guide you through the development flow. Bitbucket Server does not come with a built-in testing and deployment tool, but it has strong integrations with Bamboo, Atlassian’s continuous integration, and continuous delivery tool. It allows you to automate your build processes.
Here are some important words and terms to know so you can find your way around Bitbucket. Some of these are terms borrowed from Git, others are specific to Bitbucket.
A branch represents an independent line of development. Branches serve as an abstraction for the edit/stage/commit process. You can think of them as a way to request a brand new working directory, staging area, and project history. New commits are recorded in the history for the current branch, which results in a fork in the history of the project.
Instead of using a single server-side repository to act as the “central” codebase, forking gives every developer a server-side repository. This means that each contributor has not one, but two Git repositories: a private local one and a public server-side one.
Git’s way of referring to the current snapshot. Internally, the git checkout command simply updates the HEAD to point to either the specified branch or commit. When it points to a branch, Git doesn’t complain, but when you check out a commit, it switches into a “detached HEAD” state.
The default development branch. Whenever you create a git repository, a branch named “master” is created, and becomes the active branch.
Bitbucket Pipelines is an integrated CI/CD service, built into Bitbucket. It allows you to automatically build, test and even deploy your code, based on a configuration file in your repository.
Bitbucket Pipes are short code chunks that you can drop into your pipeline to perform powerful actions. Pipes make it easier to build powerful, automated CI/CD workflows and get up and running quickly.
A project is a container for repositories. Projects make it easier for teams to focus on a goal, product, or process by organizing your repositories into projects. Projects can be either visible or hidden from public view.
Pull requests are a feature that makes it easier for developers to collaborate using Bitbucket. They provide a user-friendly web interface for discussing proposed changes before integrating them into the official project.
The tree of actual checked out files, normally containing the contents of the HEAD commit’s tree and any local changes you’ve made but haven’t yet committed.
Ready to improve your SDLC performance?