Tagged: devops

In Jenkins you have the chance of running commands inside of seemingly random containers. You are able to execute commands in node, maven, or a bunch of other containers. Somehow the containers keep running even after executing a single shell command. How is this happening?

Ansible is an agent-less configuration management system. While agent-less it's true, it still needs two things for it to operate: SSH and python. But what if on the brand new instance we only have SSH access, but no python? Is there a way to install python with Ansible?

For the last three weeks I tried to get an eGPU, a Sapphire Radeon RX 580 to be exact, to work. Today’s the day when I’ll stop using anything Radeon, and Kdenlive for the next 10 years. In this quick article I’ll explore why.

This is the last article from the Vim Ultimate Editing series. We looked at what makes Vim (in my case neovim) the best editor out there. We’ve analyzed the console support, the awesome UltiSnips, and today we’re looking at having the configuration as a git repository.

As you might remember, we discussed a while back, that having automation for the mundane tasks would yield a great result in the long run. Let's go a bit more on the most mundane of them all: security.

What if instead of writing insanely long commands in the terminal to find out the namespace we're working on, there would be a command for it? Let's say kubens? With bash completion? Of course.

Let's assume that during the build, you need to archive some data on a specific node. Yes, you could just rsync to it and post data, but if you already have a Jenkins agent running there, maybe there's a simpler way.

In order to do that, we will start with creating a deployment for it. Fortunately there is already a docker image, so creating the deployment is quite straightforward:

Did you know that if at work you waste 10 minutes each day, for doing some mundane repetitive task, at the end of a working year you would have wasted roughly one full working week?

The 3rd part of our 3 part series in which we'll explore how to get started in using germanium. We'll assume the only thing you have is python and a browser, and we'll go from writing the first test, to integrating the test suite in a CI/CD system, in our case Jenkins.