GitLab

Des docs que je galère à retouver à chaque fois et/ou dont je me sers/parle souvent.

CI/CD :

• La configuration spécifique à l'instance SaaS GitLab.com.

• Webhooks

To infinite and beyond: GitLab's onw pipeline.

Also, GitLab CI/CD Examples right from the doc.

• The shiny pipeline.yml file from the pipeline-components project.
• https://about.gitlab.com/images/13_3/cartesian-matrix.png : Best Practices blog post, including a Drop-in simple Docker CI.

• The Debian salsa-ci-team/pipeline project

Long term goal: use https://github.com/egnyte/gitlabform !

Des trucs à faire, voir, explorer, penser:

• Un webhook sur project_create pour faire un coup de sed direct, pour changer les {{IMAGENAME}} et autres {{DEFAULT_COMMAND}}.

Docs and pointers:

• https://docs.gitlab.com/ee/development/cicd/templates.html Premium/Gold only :(
• https://docs.gitlab.com/ee/user/project/settings/import_export.html

• Multi-architecture Docker images builds
  • Pareil mais avec une image buildx pré-construite qu'on trouve sur jdrouet/docker-with-buildx

• https://docs.gitlab.com/ee/ci/multi_project_pipelines.html

(fr) https://blog.ippon.fr/2020/07/31/construire-la-ci-dun-monorepo-les-parent-child-pipelines-de-gitlab-ci/: monorepo pipelines:

• root CI triggers sub-folders' pipelines
  • android/ builds
  • iOS/ builds
  • backend/ builds
• what about a QA job that tests everything?

https://zerotoprod.com/posts/gitlab-ci-advanced/: back and forth multiple projects pipelines:

• project1 builds ⇒ triggers project2's test job.
• Project2 tests ⇒ triggers back project1's deploy job.
• Project1 deploys ⇒ triggers Project2's QA's job.
• Project2 does QA.
• 

• Blog announce
• documentation in the .gitlab-ci.yml Reference

deploystacks:
  stage: deploy
  script:
    - bin/deploy
  parallel:
    matrix:
      - PROVIDER: aws
        STACK:
          - monitoring
          - app1
          - app2
      - PROVIDER: ovh
        STACK: [monitoring, backup, app]
      - PROVIDER: [gcp, vultr]
        STACK: [data, processing]