3 posts tagged with "DevOps"

GitLab CI/CD​

GitLab CI/CD is a tool built into GitLab for software development through the continuous methodologies:

• Continuous Integration (CI)
• Continuous Delivery (CD)
• Continuous Deployment (CD)

Note: Out-of-the-box management systems can decrease hours spent on maintaining toolchains by 10% or more. Watch our “Mastering continuous software development” webcast to learn about continuous methods and how GitLab’s built-in CI can help you simplify and scale software development.

What is meant by CI/CD?​

This is a method of regularly delivering apps to customers and automating all phases of application development. The main concepts of CI/CD are Continuous Integration, Continuous Delivery and Continuous Deployment. CI/CD solves the problems that integrating new code can cause for DevOps teams (also known as "integration hell").

In particular, CI/CD ensures continuous automation and monitoring throughout the entire app lifecycle, from the integration and testing to the deployment and implementation phase. These interrelated practices are often referred to as the "CI/CD pipeline" and are supported by agile collaboration between DevOps teams.

I just want to build something useful​

Coming from a conservative country I was raised with a strong sensibility for the separation of concerns - put your inline CSS into a style sheet, let the computer scientist handle the shopping list for new office computers and never even think about putting the salt shaker into the spice rack! Salt belongs to MSG and sugar rack on the right.

So is DevOps really the monster it is made out to be? Is a backend developer able to design a usable user interface and will a frontend dev bring down the whole service by ignoring best practices of harding the server before uploading his application?

How does a Jack-of-all-Trades handle a specific task compared to a specialist?