We once had solely the simpleton, paper fold-out map to navigate long car trip. Then we moved onto Maps.com, where our path could be map out for us. Next, Google Maps came along which let us customize your trip - avoid highways, toll, or traffic. And now we ’ re approaching the age where self-driving motorcar are in reach, capable to make on-the-fly conclusion for avert obstacles and map flexible routes to the destination. What did we action with each loop of pilotage? & nbsp;

Crucial decisions were automated. & nbsp;

Our world is filled with automation where we ’ re continuously seeking ways to decimate “toil” - work that incline to be manual, repetitious, automatable, tactical, devoid of endure value, and that scale linearly as a service grows.

One topic we ’ ve been talking a lot about this week is CI/CD and its impact on software development team. In this era of speedy development, team are using tools like Jira, Bamboo, Bitbucket Pipelines and of course, mabl to help enable their teams to continuously deliver software. & nbsp;

In many ways, we ’ re still in the Google Maps era of shipping package. There are yet many manual processes affect with advancing codification through development pipelines. Quality subject are still being track down and logged manually. Determining whether or not to boost a soma is still manual at times, particularly when it comes to last-minute manual testing. As teams drive to optimise their pipelines, we dare to ask the question: what if our pipeline be more intelligent?

Build with Intelligent Pipelines using mabl and Bitbucket

Intelligent CI/CD workflows can automatically makeinformed decisions(such as promoting or demoting a build) based on case-by-case test output - decisions that once could merely be make manually. This levelheaded pipeline automates decisions establish on data, rather of alone relying on your ontogeny squad to manually evaluate that test data. & nbsp;

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Integrating automated testing into your development workflow earlier aid your team:

• Repair bugs and test failures in a fraction of the time it would otherwise
• Reduce the cost of repairing bugs and test failure belatedly in the dev lifecycle
• Avoid the gist of accumulated change

You may have seen the exciting news yesterday, Atlassian announced, which will be useable for Bitbucket customers in April-May of 2020. We are lofty to have been include in the proclamation for our aboriginal integration that alerts developers to possible number before they ’ re liberate into production, and allows our joint users to create an intelligent pipeline - the self-driving car of CI/CD.

Currently, you can set up Bitbucket to need that mabl tests pass before a PR can be merged. Its newCode insightsfeature will help you assemble an intelligent pipeline by let you to run end-to-end tests as part of your PR (pull request) and commit chit within Bitbucket Pipelines. Test result data is incorporated forthwith back into the workflow, enabling quicker, more efficient pipeline management. & nbsp;

Insights into test results are quickly pipe to where you need them - directly inside the PR. This enables your team to receive feedback earlier in the development process to ensure code changes don ’ t introduce issues. & nbsp;

Want to hear about Intelligent Pipelines and more tips for integrating mabl into Jira, Bitbucket, and Bamboo? Come learn more at ourwith the engineers that progress the integration. Watch