Operations | Monitoring | ITSM | DevOps | Cloud

Developers understand the importance of keeping their team up to date on work and use many of the integrations between Bitbucket Cloud and Jira like smart commits and automation triggers to do so automatically. However there may be times where there are nuances or uncommon situations when merging a pull request that aren't covered by existing automation rules – sometimes there are multiple pull requests, or sometimes merging means you're now in 'Done' and other times you're in 'Releasing'.

Bitbucket Pipelines provides teams with a one-stop solution to build, test, deploy and track their code, without ever leaving Bitbucket. Developers and release managers can easily track and visualize deployments, while non-technical teams can have visibility into what features are coming down the pipeline.

While working from home is the new normal, communicating and collaborating virtually hasn't become any easier. And for developers, being productive while at home has its own set of challenges (we're thinking of things like figuring out how to pair program over Zoom or how to make do with only a single monitor). In times like this, our engineering team has been relying on one short-cut towards productivity: the Bitbucket Cloud bot for Slack.

We're happy to announce that on September 15th, 2020, we will begin gradually enabling a new traffic acceleration improvement for all Bitbucket Cloud users (Free, Standard, and Premium) when accessing Bitbucket.org for Web- or Git-based (ssh/https) operations. This new improvement leverages AWS Global Accelerator to route traffic to and from Bitbucket Cloud via 83 Points of Presence in 73 cities across 38 countries, potentially dramatically speeding up transaction times.

Today Bitbucket is releasing a new labs feature, "Pending Merges", which allows for automatic merging of pull requests when builds pass. This means no more continually checking back in on your pull request, just waiting and waiting for your builds to pass before you can finally merge it. You will no longer be forced to begrudgingly fix that one-character whitespace typo in your comment that you really should fix, but that means you're in for another 30-60 minutes of watching your builds.

High productivity. Low turnover. Satisfied workers. Less stress. A larger talent pool. Fewer office expenses. ADA compliance. And better work-life balance. When you list the benefits of remote work, there’s a lot to love – for both businesses and the people they employ – which is a huge reason why more and more companies are starting to embrace a remote workforce.

When the entire company is working from home, pair programming is not only possible but even more valuable. If you were practicing it face to face, why not continue remote? If you weren’t, why not try? My team did a series of remote pair programming sessions in during the last month or so, and I want to share a few tips from that experience. If you’ve never tried pair programming before, here’s a good primer.