Operations | Monitoring | ITSM | DevOps | Cloud

Many of the available configuration management tools, such as Ansible, Terraform, Puppet, Chef, and Saltstack provide automation for infrastructure, cloud, compliance and security management, and integration for deployment and continuous deployment (CI / CD). But what is the best tool to start automating your particular environment? The difficult task of evaluating Configuration Management Tools prevents DevOps from evolving technically and proposing improvements to the environment they manage.

In agile development, planning, coding, and builds are an ongoing loop. But when a circle is broken, you can’t travel it at full speed. For users of Atlassian Bitbucket Server and Jira, JFrog’s integrations can help Artifactory bridge the gaps for continuous velocity. In a previous blog post, we discussed how to provide Jira information as a critical “why” in your build information.

One of the challenges when you’re starting out with DevOps is getting the lay of the land. There are a lot of tools out there. And when one of the goals of DevOps is continually improving your processes, it’s important for you to understand how those tools might fit in your infrastructure. At the same time, you want to be efficient. You don’t want to add tools that overlap with one another. Or tools that cost more than other effective alternatives.

Service alarms are going off and you are on the hook to restore stability, but you need to prevent any more changes to production while you dig further. You could "freeze" production by announcing it in the office, sending a message on Slack, or sending an email to the affected teams, but that may not be enough or may require extra work that would distract you from debugging and fixing the problem.

COVID-19 has led businesses into extreme work challenges. To overcome these challenges, companies have shifted their working patterns and have embraced Remote Work to avoid any negative impact on employee’s health as well as the business. COVID-19 has made IT-sector office culture’s shift to remote work prominently. The tech teams, who already have DevOps processes in place, got huge benefits and did not get much impact while shifting their workplace from regular office to home.

At Cloudsmith, we are all about automation and we believe that the Cloudsmith CLI is an essential part of your DevOps toolkit.

This blog post will provide you with information on how to use JFrog CLI with JFrog Distribution workflows. JFrog Distribution manages your software releases in a centralized platform. It enables you to securely distribute release bundles to multiple remote locations and update them as new release versions are produced. For those of you who are not yet familiar with the JFrog CLI, it is an easy to use client that simplifies working with JFrog solutions using a simple interface.

One of the exciting things about being a Golang developer today is the strong community that supports the evolution of the language that was developed at Google. The founders of Golang were open to getting engineers involved early-on and the community-centric approach has now become an asset to Go itself.