There are three main categories of Continuous Integration (CI) Systems. Choosing the right CI system is important to the success of every product.
1. Open-source CI systems
2. Commercial vendors Offerings
3. SaaS Offerings
Let me start with the open-source. There are various open-source CI systems like;
· Travis CI,
· Integrity etc
But the de facto standard of open-source for CI is Jenkins. You download the software, host it yourself, either on-prem or in the cloud.
The second option is to use one of several commercial vendors that provide hosted CI…
Since Greek philosophers, the value of a mentor has always been underestimated. 2000 years later, the rules still apply.
A mentor, or at least emulating someone, who is now where you want to be at some point in the future, is the fastest way to success.
Before I jump into what container means and how containerization improves modern-day application deployment. The default way to deploy an application was on its own physical computer. To set one up, you would find some;
· Physical space,
· Network connectivity,
· Install an operating system,
· Any software dependencies, and
· The application itself.
If you need more processing power, redundancy, security, or scalability, what would you do?
Well, you would have to add more computers. It was very common for each computer to have a single purpose. …
In this article, I’ll explain the fundamental components of the Kubernetes operating philosophy. To understand how Kubernetes works, there are two related concepts you need to understand.
1. Kubernetes Object Model
2. Principle Of Declarative Management
The first, Kubernetes object model. Each thing Kubernetes manages is represented by an object, and you can view and change these objects’ attributes and states.
The second is the principle of declarative management. Kubernetes expects you to tell it what you want the state of the objects under its management to be. …
Besides living DevOps, I actually read a lot, and I think it helps me get some different perspectives and makes sure that I get outside of my own bubble and experience. So, there are a few books I thought I would recommend for you to take a look at.
Apparently, everyone who does DevOps needs to read at least once. It’s a great book. It’s a more story-based scenario by Gene Kim and co., that says look; let’s walk through an actual fictional example of an enterprise that has challenges and starts implementing these sorts of DevOps practices. …
Before we jump into using DevOps in our organization or team, it’s important to understand the values it could bring to the organization or team. I want to take a moment and talk about some of the core DevOps values, some of those things that you have in DevOps.
Trust is a huge one. This is trust in each other, trust that people and teams will do the right thing. You’ll also see trust, but verify as a principle in DevOps that of course, you trust people. …
In my posts on Top 4 Reasons behind Building a Team and Reasons Why Teams Fail. I discussed reasons why teams are put together and reasons why teams fail respectively. So, how do we build a Successful Team? Before we jump into tactics let’s talk about the definition of success.
These are the questions you can ask to get what success could mean to your team.
· How would you define a successful team? You might measure team success by the cohesiveness of the team.
· Was the team close?
· Are they a tight organization that from now on…
I think one of the biggest reasons teams fail is a misalignment of vision.
For example, you may have worked on a team where your customer or the people outside of the team had an idea for what team was going to produce. They may have thought, “We hope for an awesome product delivered in nine months.” OK, I like the nine months, but I don’t like the hope or the awesome.
How do you define awesome? What’s an awesome product? As a team member you know you want more than awesome — you want specifications. …
Understanding why teams are put together is of utmost importance to the upward movement of any organization.
Why teams are even put together in the first place. You’ve heard the saying “if you want something done right, do it yourself.” There are reasons why you might not want to do it yourself.
#1 The More Resources You Deploy The More Quality And Faster Results You Get
One of the most obvious reasons to have a team is because there’s an idea that the more resources that you throw at something, resources being;
· More people,
· More eyeballs,
Projects are similar in many ways but no two projects are the same. — John Babel
In project management, it’s important to understand what a project is? What counts as a project versus what else might be part of our normal course of business? Well, there are a few unique characteristics that set projects apart from other sorts of work.
Senior Cloud & DevOps Engineer @Panet, tweet: @saheed_olad