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

IBM Cloud Container Service is now IBM Cloud Kubernetes Service

Effective immediately, IBM Cloud Container Service is renamed to IBM Cloud Kubernetes Service (IKS).

Continue reading

Flex harder, better, faster, stronger

A few months ago, we reimagined data warehousing in the IBM Cloud with Flex Performance, the flagship tier of our new Flex line of offerings. Flex brings new levels of elasticity, speed, and resiliency to data warehousing on the IBM Cloud, and forms the foundation for our strategy moving forward. We're working continuously to not only strengthen and enhance its capabilities, but to also make them more accessible to you so you can better leverage them and get the most out of your data warehouse. Today, we're proud to announce a significant update to our Flex family.

Continue reading

Announcing App ID integration to IBM Cloud Kubernetes Service

Today, we're excited to announce App ID integration with IBM Cloud Kubernetes Service. You can use this integration to enforce policy-driven security in a consistent way using declarative configuration of the Ingress Controller to add App ID protection for web applications, APIs, and back-ends. Using this approach, you don’t have to instrument each of your applications separately - all the authorization and authentication flows will be handled automatically for you. No code change is required!

Continue reading