Here at Puppet, we’re big fans of Atlassian. Our team in Sydney is quite fond of reminding us — frequently — of how much they appreciate the richness of Atlassian’s portfolio and the various ways we should be working together. And we have many proof points. Teams rely on Atlassian’s JIRA ticketing system to manage the development of Puppet code. Bamboo powers module tests, using Puppet’s Beaker framework.
But it’s not just our internal teams that are touting the attractiveness of integrated workflows with the Atlassian suite: we frequently hear from our customers about their wishes for connected workflows involving Puppet’s automation capabilities. These are the connections that underpin tooling and process requirements around sound DevOps practices. These are some of the reasons why we are excited about our relationship, and our integrations — both current and planned — with Atlassian.
You may have heard of the Puppet-HipChat integration announced earlier this year. Together, we and Atlassian rethought visibility, collaboration and policy, focused on optimizing how teams can push infrastructure changes while monitoring proposed changes in real time. Now you can go to the Atlassian Marketplace to get the HipChat plugin for Puppet Enterprise.
New: recommended workflow for Puppet and Bitbucket Pipelines
Building on the momentum of our partnership with Atlassian, we’ve created a new recommended workflow with Bitbucket Pipelines.
Some background on Bitbucket and Puppet: Puppet Enterprise works with Atlassian Bitbucket to know when changes to infrastructure code are ready to be staged on the Puppet servers. Bitbucket is an indispensable tool for many teams, enabling them to write and maintain Puppet modules, Hiera data, and Puppet environment content. After a proposed change to a Puppet environment has been peer reviewed and merged, Bitbucket uses a webhook and alerts Puppet Enterprise to distribute the updated code to the Puppet servers. This is just one of the many ways that Puppet uses integrated workflows into portfolios like Atlassian’s ensures that you have the shortest path to better software and the best path for managing your infrastructure.
Now, turning to today: With Atlassian, we've developed a new recommended workflow on Bitbucket Pipelines to provide continuous delivery (CD) in the cloud. We have transformed the approach from a simple Git repository tied to a continuous integration (CI) tool into a unified enterprise-level testing and version control solution.
Hosted within Bitbucket Cloud, Bitbucket Pipelines allows you to create a one-stop shop for handling the end-to-end process of receiving, testing and deploying Puppet code. With our latest integration, you can utilize Atlassian’s elegant and powerful all-in-one CI/CD machine, with Puppet automating deployment into production environments, as well as managing the configurations once deployed.
Check out our documentation, and let us know what you think!
Matt Girdharry is a senior manager for business development and global alliances at Puppet.
- To read more about continuous delivery, download the full ebook here.
- What's the difference between continuous delivery and continuous deployment? Find out this, plus a lot more, in this blog post.
- Make the business case for continuous delivery.
- The 2016 State of DevOps Report explains why DevOps is critical to continuous delivery, and other ways DevOps enables business growth.