Continuous delivery: The next evolution of software development - Valiantys - Atlassian Platinum Partner

Continuous delivery: The next evolution of software development

Software development has seen a lot of changes in the last decade. So what’s next? On the back of the agile transformation wave, we expect the next big evolution in development to be continuous delivery, which has become the leading initiative for IT organisations large and small.

As more companies embrace cloud services, product management has evolved to become more dynamic. This means organisations must adapt by becoming more agile, enabling them to respond to customer needs and deliver results faster than before.

Why opt for continuous delivery?

Continuous delivery is more that just a fad – similar to the way in which agile development has transformed the IT landscape, continuous delivery will help drive transformation in how software is developed and shipped. Continuous delivery allows organisations to ship software faster, with lower risk of failure, and helps bridge the collaborative gap between development and other teams.

Continuous delivery

A continuous delivery approach can also help teams to:

  • Innovate faster: understand through experimentation what features are most desired by customers, and as a result gain traction in the market.
  • Realise value more quickly: by shipping features faster and in small increments, businesses can increase the time-to-value from the investment in research and development.
  • Reduce costs and increase quality: shipping more often requires investing in quality development infrastructure, while writing automated tests to decrease testing time.

Implementing continuous delivery

Enter Bamboo!

Continuous delivery

All modern CI servers – including Bamboo and Jenkins – have evolved from the continuous integration phase to serve this growing customer need.

Bamboo uses stages and build pipelines to manage the entire build process, from Committing code -> Testing -> Staging builds -> Deploying to production.

Jenkins, on the other hand, supports continuous delivery mostly via build pipelines.

This blog will not cover how to set-up build pipelines for continuous delivery using either tools, as it’s a wider discussion topic, but you can refer to:

Bamboo vs. Jenkins

Picking the right tool is important. While both Bamboo and Jenkins can be used for continuous delivery, they have different strengths. Let’s take a closer look:

Bamboo     Jenkins  Comment
Ease of setup and configuration Setting up both Bamboo and Jenkins is fairly simple. Both applications are JAVA-based and thus platform agnostic. They can be deployed on any platforms with an Oracle JDK.
Usability  ✓ × Although not a critical factor in choosing a CI/CD tool, Bamboo wins due to its up-to-date UI. However, you can customise the Jenkins UI with external plugins.
Integration with build tools  ✓  ✓ Both Bamboo and Jenkins have a healthy eco-system of third party plugins, along with flexible public APIs to extend the tools.
Branch management (DVCS tools) × Bamboo comes with support for DVCS systems out of the box – the support extends to automatic branch detection and management.

· Bamboo can be configured to create plans on the fly, as new feature branches are configured.

· Bamboo can auto-merge once a build suceeds.

· Bamboo can clean-up unused branches.

· Jenkins can do branch management, but this needs to be configured via scripts and plugins.

Pipelines  ✓  ✓ Bamboo can be easily configured for build pipeline, with a build configuration paradigm catering for complex build workflows. Jenkins doesn’t support build pipelines out of the box, but there are third party plugins which provide this functionality.
Scaling with remote builds  ✓ Both Bamboo and Jenkins provide support for remote agents (known in Jenkins as slaves).
Integration with Atlassian suite × A key selling point for Bamboo is its integration with other Atlassian toolsets (JIRA, Bitbucket Server and more). This provides visibility into the branches in which a bug or JIRA task was fixed, along with the status of the build. Jenkins has some integration with JIRA, but the depth of information is fairly limited.


I like to think of continuous delivery as an evolution of agile philosophy – after all, what good are scrums and sprints if teams are not able to shift software effectively? Continuous delivery will transform the way that organisations interact with customers, building on the experience of agile processes and continuous integration.

Similar to the change management aspect of agile transformation, the major road block for organisations in shifting to a continuous delivery model will be a lack of commitment to cultural transformation as development and operational teams learn how to collaborate. That said, the benefits of continuous delivery can be vast.


Cutted Triangle

Subscribe to the Valiantys Newsletter

Registered request ! Subscribing... This is not an email An error occured

In accordance with our privacy policy, we are committed to respecting your personal data.

Contact us

Our Atlassian certified consultants will be happy to answer you.

Join us

We're building the next dream team - Are you in?

Follow us

We use cookies for the operation of our website. This is to improve its use, to personalize your experience, and to compile visitor statistics. By continuing to use this site, you consent to this policy. You can manage the settings and choose whether or not to accept certain cookies whilst browsing. For more information, see our privacy policy. Our privacy policy

Privacy settings

In order to facilitate your navigation and to provide you with the best possible service, we use cookies to improve the site to the needs of our visitors, particularly according to the number of visitors. For more information, please read our privacy policy. Our privacy policy


Google reCAPTCHA is a system designed to distinguish humans from computers, so that bots are unable to maliciously fill out forms on behalf of a human being.


Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. Used by the social sharing platform AddThis to store the user's usage history of the AddThis sharing widget. Registers a unique ID that is used to generate statistical data on how the visitor uses the website.


Targeting Cookies: Targeting cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant advertising on other sites. They are based on uniquely identifying your browser and internet device. You can turn off the use of cookies for targeted advertising here. When the button is green, targeted cookies are on. When the button is red, targeting cookies have been turned off.

Social Media Cookies: These cookies are set by a range of social media services that we have added to the site to enable you to share our content with your friends and networks. They are capable of tracking your browser across other sites and building up a profile of your interests. This may impact the content and messages you see on other websites you visit. If you do not allow these cookies you may not be able to use or see these sharing tools.