The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Working in a DevOps field, I often find myself needing to deliver a feature or an improvement (basically a piece of code) in a relatively short amount of time, or even working in parallel on different tasks. A rather universal software development stack is comprised of: Repository and branch management in Git has never been easier. Get more control over your Git workflow with the visualization offered by GitKraken.
Troubleshooting is the understanding of changes within the system and their impact on its health, behavior, and functionality. However, as dev environments grow exponentially more complex, the definition of “the system” itself also constantly expands. To keep pace, we constantly work to evolve Komodor’s platform and enrich it with new capabilities and integrational options.
Kubernetes allowed us to manage application deployments and infrastructure components using declarative configuration files (yes, those YAMLs that you may not be a fan of ). While dealing with a myriad of YAML files may be loved by some and hated by others, it enables us to host all these files into a Git repository, hook it up to a pipeline (Jenkins, GitLab, etc.), and have a tool apply those changes to a cluster—and voilà, you have GitOps.
Data center managers are increasingly looking for ways to automate tasks to save time and improve data accuracy. In our recent Automation Workshop webinar, data center experts from eBay, MacStadium, and the University of Chicago shared their real-world use cases and insights on how they use APIs and integration to drive automation in their data centers.
As a version control system, Git is delivered within Unix style command line methods, and these commands ultimately create the backbone of Git’s software. MacOS & Linux Operating Systems have a built-in terminal shell that supports Unix-based command line features whereas Microsoft Windows Operating System command line prompt is not a Unix-based terminal.
There’s an insidious disease increasingly afflicting DevOps teams. It begins innocuously. A team member suggests adding a new logging tool. The senior dev decides to upgrade the tooling. Then it bites. You’re spending more time navigating between windows than writing code. You’re scared to make an upgrade because it might break the toolchain. The disease is tool sprawl.