Eficode Praqma Blog

Helm charts lifecycle management is a manual task. Helmsman allows you to automate your Helm charts lifecycle management using declarative configuration files.

Job DSL or scripted/declarative pipelines are becoming the standard when it comes to defining jobs in Jenkins. Now we need a similar solution to maintain Jenkins itself.

Continuous Integration and Code Review are strongly correlated with success. Many use Pull Requests for code review, but for co-located teams this can be an obstacle for CI. Is there a better way?

A developer that pushes their changes and goes on a celebratory walk to the water cooler is done. But, they’re not done done, their changes have yet to be thoroughly tested, added to future release notes, properly peer reviewed and more. These are pains we want to rid the software industry of, and here’s how we do it.

We strive to continuously improve, so the 8th gathering in our Continuous Delivery Alliance will feature all the good things from the 7th meeting in a slightly evolved format.

We had our 7th gathering in the CoDe Alliance a few months ago and have worked to distill and evolve many of the good ideas that came out of our sessions. Our aim is to turn our interesting discussions into tangible projects and running code.

What do we need from a CI/CD system? How should we decide which one to use? In this blog we ask ourselves what a modern CI/CD system should look like and compare two commonly used build systems: Jenkins pipelines and Concourse CI.

Immutable infrastructure as code reduces inconsistency and makes deployments faster and easier. We can provision immutable infrastructure with Packer & Terraform. Let’s use them to provision Jenkins Windows build slaves.

You don’t always want Jenkins to start running jobs right after it starts. Sadly, starting up in a dormant state isn’t a built-in feature, unless you’re running CloudBees Jenkins Enterprise. However, there’s little a clever script can’t solve.

How to achieve high availability in a smart, easy to manage, reproducible manner? The solution is ASK (Atlassian Software in Kubernetes).

10 years ago, Eficode Praqma started, not in a garage, but in a posh apartment in the Copenhagen city center. Soon it became apparent that the dot-com bubble had already burst and it wasn’t going to be a walk in the park.

Albert Rigo shares his thoughts on the Atlassian Accelerator Day in Copenhagen, and how he learned to quickly and comfortably scale Atlassian Data Center, upgrade with zero downtime and stop spending his weekends upgrading JIRA.

Let’s talk about Eiffel - the traceability protocol, not the programming language. As we are attending the Eiffel Summit, we let you in on how the big companies work with traceability, and on the latest collaborative projects.

This November the Continuous Delivery Alliance gathers for the 7th time. Do you want to join forces with some of the best people in the world of Continuous Delivery and collaborate on the next generation of tools? Then join the Alliance!

Imagine a workflow so sophisticated
that you couldn’t break the integration branch even if you tried. And imagine being able to manage all of the issues, promotions, and deploys without leaving your terminal.

Installation and management of CI servers is a critical task for any IT team. Kubernetes and its package manager (Helm) provide an easy way to customize Jenkins installations. Let’s see how to do this and add Windows build slaves.

In the past we had all kinds of software specialists: requirements specialists, build specialists, configuration management specialists, and test specialists. Those days are over. We are now in the age of the Full Stack Developer.

DockerCon is rolling full steam ahead these days in Copenhagen, and Eficode Praqma is there with an awesome pack of consultants. Follow this post to get the latest update from this cool event.

It’s early morning on the day before the official opening of DockerCon ‘17. Pre-conference activities are buzzing, but one room is different; Outside this room a breakfast buffet is set up - and it’s good. Whoever is invited here is in for a treat.

Finding realistic data for testing is often a headache, and a good strategy is often to fabricate it. But what if your randomly generated data turns out to belong to a real person? What if they complain and you get fined 4% of global turnover?!

As of Kubernetes 1.5, Windows containers support was introduced in an alpha release. With the beta version just around the corner, we put the Windows support to the test. Is it mature enough for production environments?