Market Leader in Development Analytics (G2 Crowd’s Winter, Summer & Spring 2022)
Backed by Y Combinator experience featured in TechCrunch
New Case Study: Learn how WOM leverage Waydev
Remote work? Learn how to gain visibility into your engineering teams and accelerate your product velocity.
The Bitbucket integration enables us to provide reports that help you in:
For daily stand-ups, Waydev integrates with Bitbucket to provide you with:
For one-on-ones, Waydev integrates with Bitbucket to help you with:
For code review, Waydev integrates with Bitbucket to provide you with:
For monthly and quarterly reports, Waydev integrates with Bitbucket to help you with:
You can integrate Bitbucket into Waydev via OAuth.
Step 1: After you create a Waydev account, navigate to Project -> Integrations and select Bitbucket.
Step 2: You will be redirected to Bitbucket where you will need to authorize access to your account.
Step 3: After the connection is done, you will be redirected to the ‘Repositories’ page, with a message of success. Now you’ll need to select relevant repositories for your project. You can select all or you can choose only the ones with data. We recommend selecting only the repos with recent work. After you select the repos, click the ‘Save Project’ button.
Step 4: You will be redirected to the app where you will need to wait until we process your data. We normally process the data in under 1 hour, but for the first time connections it can take up to 12 hours. Pull requests may take 24-48 hours to process completely.
Step 5: Now everything is set up, you just need to wait until we process the data.
Bitbucket is a Git repository management solution. It provides a central place to manage git repositories, collaborate on source code and guide you through the development flow. Bitbucket is hosted on Atlassian’s servers and accessed via a URL. Bitbucket has an exclusive built-in CI/CD tool, Pipelines, that enables you to build, test, and deploy directly from within Bitbucket. Bitbucket provides features that include:
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.