With only 49 days before this very long year comes to an end, we’re thrilled to announce the 2020 State of DevOps Report is finally here. We’re in our ninth year producing the State of DevOps Report; at this point, more than 35,000 technical professionals from around the world have contributed to this body of research, the longest-running and most widely referenced DevOps research in the industry.
I’m excited to announce the release of Puppet Enterprise 2019.8.3. This release builds on a number of important product enhancements based on customer feedback and delivers on the second phase of our highly requested Value Dashboard.
The 2019.8.2 release of Puppet Enterprise has added a significant improvement to code deployment by enabling Puppet modules to be downloaded in parallel instead of serially. This functionality was added to the upstream r10k project almost a year ago and has now been added to Puppet Enterprise Code Manager.
Puppet Plans were added in the 2019.2 release of Puppet Enterprise and Puppet Enterprise 2019.8.2 extends that functionality by adding support for scheduling Puppet Plans. This enables plans to be run at some point in the future or on a recurring schedule. Plans can be scheduled using the Puppet Enterprise console, Puppet Enterprise command line, or the Puppet Enterprise REST API. In this blog post we’ll walk through how to schedule a Puppet Plan in the Puppet Enterprise console.
We’ve had an exciting year here at Puppet, and although it’s not the year we could have expected, I’m encouraged and inspired every day by the resilience of our team, our commitment to each other, and our drive to help customers navigate through so much uncertainty and change.
In this blog we’ll share the journey we went on to solve a not-so-easy customer problem: a critical Windows services restart during Puppet agent upgrades. As with most software fixes, it starts with a customer ticket: component DHCP Server service restarts after an upgrade. This troubleshooting journey goes from analyzing Windows installer logs, to using undocumented Windows API calls, and back to the Windows installer logs, until we eventually found a solution.
When Puppet shows up red, don't panic! You need to figure out what's causing the error, so you can understand whether it's something fixable, or an actual bug. Generally, the first error in a Puppet run is the one you need to concern yourself with. Once the first thing fails, others that run after it or require it to succeed will also fail and could produce a LOT of red text! So scroll to the first red error on your Puppet run.
