Skip to main content

Pipelines

The deployment pipelines (accessible through Build -> Pipelines in Gitlab) will appear the moment you add the .gitlab-ci.yml file to the project. To do so, copy the one from the example projects (back and front) to your own.

The pipeline is split in three or four stages depending on the application:

  1. .pre: prepares configurations for the next stages.
  2. build: builds the application (if needed), compiling/transpiling any code.
  3. package: creates docker images based on the previouly build code (some applications might build their code in this stage too).
  4. deploy: marks the applications to be deployed in the respective environment. Once a job is completed in this stage, it doesn't mean that the application has been rolled-out properly but, instead, that it will be rolled-out eventually. It does this by modifying the files within the devops/environments/<env> projects (never modify these files manually).
Additional Notes​
  • You can analyze the example pipelines for: back and front.
  • To know if a server has been deployed or to trigger a redeploy (or perform any other type of server management), access the "Cluster" section in the BackOffice.
  • The frontend projects need to adapt their own multi-stage Dockerfile to their needs. The example one can be used as reference.