Pipeline on Jose Castrillo

Trigger pipelines by using the API

Sat, 15 Jul 2023 00:00:00 +0000

When you join a new project, company, customer, etc. (you’re still in the onboarding phase 😅), meanwhile you may find that you need to make a few changes to get your team’s production pipelines up and running. In this case, you can call an API trigger from one project to another (this is just a example).

I’ve been in the situation described above before, and it was how I discovered this amazing feature in GitLab.

Fixing tags on Azure invoices

Tue, 21 Feb 2023 00:00:00 +0000

Merging two CSV files using Pandas in Python 3 on Linux is a quick and easy process that can save you a lot of time and effort, however in my case I used other script to extract specific tag values from a CSV file, converts them into a JSON object, and writes them to a new CSV file, in that way I provided a workaround for those tags wanted.

Cloining a repo and setting up as artifact

Tue, 20 Dec 2022 00:00:00 +0000

On this post I will give you an example of how to clone a repo into your pipeline and use it for other jobs.

As you can read from Gitlab official documentation artifact can output an archive of files/directories. I set the following example:


  artifacts:
    paths:
      - <project_name>
    exclude:
      - <project_name>/.git/**/*
    expire_in: 60 seconds

We need to call the artifacts by using “artifacts” keyboard in the pipeline, in this example paths keyboard which files/directories add into artifacts.

Trigger pipelines in Gitlab

Thu, 10 Nov 2022 00:00:00 +0000

The following post is example of how to activate and use Trigger pipeline by API the official documentation over here as it mentioned is can be use “to trigger a pipeline for a specific branch or tag”; for our example I use it to activate a pipeline into specific branch.

Steps:

repoA will be the main one where the pipeline trigger it will be activate

From repoA go to Settings-CI/CD-Pipeline triggers
Click on “add trigger” copy your token
From repoB that will be our caller of the repoA pipeline create a variable where you can paste the token.
Finally into your pipeline on repoB you can add something like below:

The best part is that you can reference to specific branch ref="<branch_name>".