Simplify Your Jira Change Management Processes Via Ansible Playbooks

A big way in which we typically measure success with DevOps has to do with integration. Your new solutions need to work with whatever products your organization has already made investments in. Because whether IT decision-makers were thinking in terms of infrastructure-as-code when they originally purchased those products or not, if the pieces of the

Express Your Team’s Infrastructure Code Standards Using Custom ansible-lint Rules

Coding style guides are becoming fairly common in larger organizations. (As examples at the deepest end of the pool, Google publishes guides for Python, Java, C++ and other languages.) Some coding style guides are more ambitious than others. Some are probably more reality-bound than others. We can debate the merits of enforcing code styles in modern software development, but we can’t

Give Your Organization Greater Visibility Into Ansible Playbook Runs Via Slack

As leaders, we are always striving to bring greater ownership/accountability to our organizations, and visibility to our internal customers. When it matters, the question of “Who did what and when?” matters more than ever. However, especially in larger microservices-based CI/CD environments, with anywhere from dozens to hundreds of app releases happening across many dev teams