Verificando autenticación…

Skip to main content

Framework 2

Based on Framework 1 built on groovy and used in Cloudbees, it maintains backward compatibility with the jobs and stages defined in Jenkins.

Core Gitlab Standard Definitions

  • CI/CD: Gitlab CI
  • Runners
    • Runners GKE Deployed on LATAM infra.
    • Independent Resource Allocation for each deployed runner.
  • Container images exclusive for pipelines
    • gcloud-sdk
    • shopify-krane

framework-2 Development Process

  1. Create Branch from develop
    • Formula Ex: PLAING-1234-ticket-name
  2. Make changes to the code and commit.
  3. Create an MR1 (Merge Request) adding task description and Ticket.
  4. Validate that MR has at least 1 approver.
  5. Confirm that PoP2 passes tests
    • In case of error create a ticket in the ANDES jira project, to determine cause
  6. Once the change is merged, it will be pending release and will be done after validating changes in package.
  • Iterm2 / Warp
  • OH My Zsh
  • Docker
  • HomeBrew
  • rbenv (MAC comes with ruby 2.6 and Krane uses 3.3.8)
  • Krane
  • yq
  • jq
brew install rbenv
rbenv init; source ~/.zprofile
rbenv install 3.3.8; rbenv global 3.3.8
gem install krane

framework-2 Repositories

  1. https://gitlab.com/latamairlines/config/devops/pipelines
  1. https://gitlab.com/latamairlines/config/devops/utils-components
  1. https://gitlab.com/latamairlines/config/devops/core-jobs
  2. https://gitlab.com/latamairlines/config/devops/security

Migration from CloudBees

More information about migration from framework-1

Footnotes

  1. Merge Request: Request to merge code between GitLab branches.

  2. Pipeline of Pipelines: Pipeline that validates changes made to components and templates of framework-2.