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
- Structure creation based on templates and components.
- Available in Gitlab Catalogs.
- Runners
- Runners GKE Deployed on LATAM infra.
- Independent Resource Allocation for each deployed runner.
- Container images exclusive for pipelines
- gcloud-sdk
- shopify-krane
Pipelines Catalog
framework-2 Development Process
- Create Branch from
develop- Formula Ex:
PLAING-1234-ticket-name
- Formula Ex:
- Make changes to the code and commit.
- Create an MR1 (Merge Request) adding task description and Ticket.
- Validate that MR has at least 1 approver.
- Confirm that PoP2 passes tests
- In case of error create a ticket in the ANDES jira project, to determine cause
- Once the change is merged, it will be pending release and will be done after validating changes in package.
Recommended Tools
- 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
- ✨ The One-Line Rule
- 📦 Component Repositories
- 🌐 CI/CD Framework Ecosystem
- ⚙️ Requirements to Use Pipelines
- 🌿 Branching Strategy and Environments
- 🔧 Pipeline Configuration and Variables
- 🏢 Organizational Structure in GitLab
- https://gitlab.com/latamairlines/config/devops/core-jobs
- https://gitlab.com/latamairlines/config/devops/security
Migration from CloudBees
More information about migration from
framework-1