DevOps

Jenkins Cluster for Continuous Integration and Delivery (CI/CD) inside Jelastic PaaS

In this article, we’ll describe how to install Jenkins cluster with slave nodes auto-discovering and self-registering inside a master node.

Jelastic PaaS implemented this solution in Jenkins DevOps Pack that can be installed from the Marketplace or through environment setup wizard as a New Environment.

In this tutorial we’ll cover both. Also, you will find out how to build a simple Java project hosted on GitHub using Jelastic Maven plugin.

DevOps 101 Part III: Package Management

When you’re new to an industry, you encounter a lot of new concepts.

This can make it really difficult to get your feet underneath you on an unfamiliar landscape, especially for junior engineers.

What’s all this jargon? What does DevOps really mean?

Here, I’ll explain package managers!

DevOps 101 Part II: Container Registries

When you’re new to an industry, you encounter a lot of new concepts. This can make it really difficult to get your feet underneath you on an unfamiliar landscape, especially for junior engineers.

In this series, I’m covering tools and terminology common to the DevOps space, plus the occasional newbie-friendly tutorial for emerging or established technologies. If you have a request or suggestion, let me know!

Today, I’ll break down container registries.

DevOps 101 Part I: CI/CD

When you’re new to an industry, you encounter a lot of new concepts. This can make it really difficult to get your feet underneath you on an unfamiliar landscape, especially for junior engineers.

In this series, I’ll cover tools and terminology common to the DevOps space, plus the occasional newbie-friendly tutorial for emerging or established technologies. If you have a request or suggestion, let me know!

Today, I’ll break down CI/CD.

Getting Started with DevSecOps

Even as a software developer, you will often hear this phrase during meetings with the company’s management and sales part. The phrase is called “Make or Buy”. Typically, we have to decide if we want to do something ourselves or spend money to buy the requested functionality. It could be less or more functionality or different so that we have to adjust ourself to use it in our context.

But as a software developer, we have to deal with the same question every day. I am talking about dependencies. Should we write the source code by ourselves or just adding the next dependencies? Who will be responsible for removing bugs, and what is the total cost of this decision? But first, let’s take a look at the make-or-buy association inside the full tech-stack.