Patching systems is not a new problem; this is something that organizations are very familiar with. Organizations have tried solving this issue in various ways by cobbling together multiple tools, processes, different teams, and more. Organizations are constantly trying to stay secure and keep their systems up to date, but patch management isn’t a simple process. In fact, applying the patch itself is just one part of the overall workflow, which involves multiple teams and various steps.

There’s next to nothing in the world that hasn’t been impacted by COVID-19. We’ve now reached the stage of the pandemic where we’re evaluating the effect on every part of our lives. Over the last few weeks, I’ve spent a lot of time speaking with IT leaders and reflecting on how the business technology landscape has been shifting.

In classic Puppet deployment architecture, compile masters are widely used when the number of managed nodes goes up. Multiple compile masters sit behind a load balancer to take care of the additional workloads. It is not rare to see Puppet adopters launching the compile masters in the public cloud, such as Amazon Web Service (AWS) and Google Cloud Platform.

Many attempts to simplify programming lead to visual interfaces that provide approachable settings for common tasks. These simplifications may appeal to non-developers, but they send experienced coders running for the command line. Yet, no code tools are rapidly expanding. Zapier, Integromat, and Workato are becoming more popular options and some believe developers won’t be needed for most integrations in the future.

It’s no secret that COVID-19 is negatively impacting businesses of all sizes in a number of ways. Some more obvious than others. Unless you are in IT, you’re probably not thinking of how COVID-19 can affect the infrastructure security of your organization, but the truth is that as businesses make the tough decision to layoff employees in order to stay in business, basic security hygiene can easily be overlooked.

Today’s monitoring investments align more often with automation than any other technology. Automation is one of the principal objectives of DevOps to reduce toil, i.e. manual work. This helps keep engineers happy and engaged, allowing for better scale in building and operating applications. Automation typically spans infrastructure and application technologies. The challenge is that many organizations just have too many automation tools.

I am making a digital transformation during this novel work-from-home (WFH) era due to a COVID-19 quarantine. Many of you are going through the same and distractions abound while sharing a workspace with housemates, children, and pets. Moreover, we have to contend with an increased risk to cybersecurity, given recent attacks on work-related software such as Slack and Zoom.

Test automation helps increase development speed while reducing cost and effort. In this article, we will share how to automate testing to help keep a test automation initiative on the right track with key tips for test execution, design and maintenance for large enterprise applications.

Platform operators, you continue to amaze us. You’ve embraced DevOps and site reliability engineering. You’ve applied these philosophies to your daily work. And you’ve used Concourse CI (the “continuous thing-doer”) to address all manner of operational workflows. When we created the project in 2016, we couldn’t have imagined all the ways you’d use Concourse to deliver fantastic stability and scalability outcomes to your stakeholders.