DevOps

Announcing the Toolchains and Delivery Pipeline beta on Bluemix

Share this post:

In May 2016, toolchains became part of IBM Bluemix as an experimental feature. Teams that are striving to improve the velocity and quality of software delivery select many tools from disparate vendors for their toolchains. Teams at IBM are no different; you can read about their experiences on the Bluemix Garage Method site. Those teams needed a way to manage the complexity of provisioning, integrating, and working with toolchains. As a result, toolchains on Bluemix were designed with these goals in mind:

  • Give team members a central place to find tools and monitor significant events, such as failures in the delivery pipeline
  • Automate the integration of tools when a team adds a tool to its toolchain
  • Give enterprises the ability to capture successful toolchain patterns in templates that can be provisioned in a repeatable way

beta_create_toolchain_edited

During the experimental phase of the toolchains release, the toolchains squad learned a lot from users about the tools they use, the integrations they need, and how enterprises are challenged by the tension between standardization and flexibility. Today, the toolchains feature is being promoted to a beta release.

Tool integration available today and more on the way

You’ve requested many specific tool integrations, which the toolchains squad is prioritizing. New tools will be added incrementally. One new feature in the beta release is the ability to integrate any tool into your toolchain. While many teams are selecting newer tools for various DevOps functions, every team still uses established tools that are often on-premises, and those tools need to be part of the toolchain, too. You can add those tools to a toolchain by going to the tool integration list and clicking Other tool.

other_tool-edited

One central tool to a continuous delivery process is a delivery pipeline. You can use the Delivery Pipeline Next service to define and automate the sequence of build, deployment, and testing activities to deliver code changes from development to production. You can configure one or more stages and the triggers that move from one stage to the next. This beta release introduces a new, streamlined flow to create a simple pipeline that builds and deploys your code to Bluemix.

beta_pipeline_dashboard_edited

As other tools are added to the toolchain, they become available in the pipeline and aware of pipeline events, such as successful or failed deployments. The beta release also includes a more interactive dashboard to monitor pipelines, and several improvements to increase availability and throughput.

multistage_pipeline_edited

Try it now!

You can try the toolchain and Delivery Pipeline beta by clicking this button:

Create toolchain

Please share your feedback and suggestions!

—Peter Klenk, Product Manager, IBM Cloud DevOps

More stories
February 15, 2019

Liberty for Java Buildpack Now Contains Two Liberty Production Runtimes

The Liberty runtime is moving from a quarterly to a four-week release cycle. As a result, the buildpack will release new functions and fixes quicker. Users of the Liberty for Java buildpack will notice a few changes to the Liberty versions packaged with the buildpack.

Continue reading

February 13, 2019

IBM Cloudant Security Update: TLS 1.2+ and Service Endpoints

The IBM Cloudant team wants to share some very important updates that will bring enhanced security to the service. These updates will change the way you engage with Cloudant, so please review to ensure that your applications can take advantage and continue uninterrupted.

Continue reading

February 13, 2019

Introducing IBM Cloudant Partition Queries: Faster, Cheaper, and More Scalable

To meet our customer demands while improving the scalability and performance of Cloudant, we are excited to introduce partition queries—a scalable, faster, and cheaper way to query a Cloudant database.

Continue reading