GitLab - extends keyword

In the previous post I had written about the include keyword. Now, let's dive in the extends keyword.

What can you do with this? Here is the definition from GitLab documentation:

extends defines entry names that a job that uses extends inherits from.
It’s an alternative to using YAML anchors and is a little more flexible and readable.

So, when is it useful? It is useful when you want to be DRY and keep your setup cleanly. Let's assume that you want to build a docker image and give developers possibility to deploy the image on dev, staging and prod environments. We are going to do that without the extends keyword, and after that we will think how we can do it better.

Example without the extends keyword:

As you can see, there is a lot of code which repeats itself: stage, image, when and script. We can remove a lot of code! So, let's do that. We are going to create a hidden job .deploy (you will not see this job in a pipeline) and the rest of the jobs will inherit from it:

Looks much better. This way, when you want to change the logic of the deployment you just need to edit one job. Every other job which uses the extends keyword and use the .deploy job will inherit the rest.

One more thing.

What if you want to send info about deployments to Slack for example? But you only care about staging and prod? You can use the after_script section. We are going to add the logic for this to the .deploy job, but we also want to do that only for staging and prod. We can use one of predefined environment variable: $CI_ENVIRONMENT_NAME and check it.

Instead of this, we could have also added the after_script section to deploy staging and deploy prod jobs with removing IF which checks the environment.

I have also added a video:



Comments

Post a Comment

Popular posts from this blog

GitLab - trigger keyword

Image
 We are going to talk about the trigger keyword today. With this feature you can define a downstream pipeline trigger. So, you can trigger a pipeline in any project (you must have access to this project of course). There are two types of downstream pipelines: multi-project pipelines child pipelines  Let's omit child pipelines and have a look at multi-project pipelines. It is very easy to use. You just need to provide a path to the project and that's it. Remember that you only can trigger a pipeline, not a job ! You can also provide more information like environment variables. As always, I am going to provide some examples, so you will understand it better. The first example: you want to trigger a pipeline in another project after the deployment of your service/s. How to do that? Here we want to trigger this pipeline (project my/run-tests ). Let's say that we want to run some tests after each deployment: We need to add the job which will trigger this pipeline in my/run-
Read more

Managing Secrets in GitLab / Git

Image
Let's say that you have to log in via ssh into an instance, and you work with GitLab, so you want to keep the private key in GitLab somewhere. Is it secure? Let's see! Custom environment variables You can use custom environment variables. Here you can read more about them (Developers cannot change them, only Maintainers and Owners can). There are two types of variables: Variable (the runner creates an environment variable that uses the key for the name and the value for the value) File (the runner creates an environment variable that uses the key for the name. For the value, the runner writes the variable value to a temporary file and uses this path) It seems that we can use File type for our purpose. We can set up it via API or UI . So, let's do that! Go to project's Settings > CI/CD . There will be Variables section (btw, you can specify variables also per group and even for all projects (in admin panel)). Click Add Variable button and add a variable: Key:
Read more