In devOps world, pipelines are the key! All the devOps developers love working with pipelines as this functionality has taken the automation of deployment, build and testing to the level we all were eyeing on from so many years. Pipelines are basically a workflow or scheduling system that goes on in the RAM all the time. You can have parallel or concurrent runners, which means that parallel ones are going on at the same time where as concurrent one would move to the next only if the first one succeeds! Almost all of you ask that whether a devOps engineer require to code? So, here is where devOps engineer would do the coding bit!! So, lets get started.
4 Stages of Pipeline:
build, with a job called compile.
test, with two jobs called test and test2.
staging, with a job called deploy-to-stage.
production, with a job called deploy-to-prod
Let’s understand them briefly here, as in example things would be more clear. So, these are four stages your pipeline can go through. Just like in any project to set up after development for deployment, you got to build it so that it has no compilation error, test it with automated parameters, set it up to a staging are before deployment for quality analysis mostly and then it is set for production!
A basic Pipeline Example:
1.create a .gitlab-ci.yml file
2. define pipeline:
SO, this is a basic pipeline with two stages defined. When you would save the file and commit the changes , a cmd would open and show the output as:
This is the primary basic introduction to pipelines. Here you can use do multiple operations, but the purpose of the blog was to just get you hungry to explore and introduce you to the pipeline. Because as easy it looks, it has a vast ocean underneath it ready for you to explore.
Hope, it would have brought lot more clarity from where you started. If you still have an any doubt, leave it in the comment section below. Our team would revert back within 24 hours.
Do Follow our Facebook page https://www.facebook.com/lovebeingengineer/.