Verificando autenticación…

Skip to main content

CloudBees to GitLab CI/CD Migration

To perform migrations from Cloudbees with framework-1 to Gitlab with framework-2, we recommend:

  • Start migrations with low-impact projects.
  • Keep a local backup of Jenkinsfile in case of incident for high-impact pipelines.
  • Request GCP account permissions before migrating

Introduction​

  • Pipelines run in stages and are graphed from left to right to show progress.
  • Each task is executed according to the stage it is in.
  • All tasks within the same stage run in parallel, unless an explicit dependency is defined between them.
  • By default Gitlab assumes that all tasks must finish successfully to advance to the next stage.
    • Gitlab allows marking task as optional (Warning).
LATAM email entry
important

More information about migration from framework-1 in: https://gitlab.com/latamairlines/config/devops/pipelines

Migration Scope​

Within Cloudbees there is a shared library that contains multiple functions and definitions that are used in the Jenkinsfile of the projects.

Migrablepipeline_type
ANDES DeliveryAbstraction
ANDES DeliveryBitriseDeployment
ANDES DeliveryBrowserStackDeployment
ANDES DeliveryBuildDeployment
ANDES DeliveryCloudBuildDeploy
ANDES DeliveryCloudDataflowDeploy
ANDES DeliveryCloudDataflowDeployMultiparams
ANDES DeliveryCloudFunctionDeploy
ANDES DeliveryCloudRunDeploy
ANDES DeliveryCloudRunDeployJava17
ANDES DeliveryComposerAirflowVars
ANDES DeliveryComposerDeployment
ANDES DeliveryComposerv1Deployment
ANDES DeliveryCypressE2E
ANDES DeliveryFrameworkIacDeployment
ANDES DeliveryGApiGatewayDeployment
ANDES DeliveryGEndpointsDeployment
ANDES DeliveryGkeRollBack
ANDES DeliveryHelmChartInstall
ANDES DeliveryHelmChartPublish
ANDES DeliveryJava17Publish
ANDES DeliveryJavaPublish
ANDES DeliveryK6Deployment
ANDES DeliveryKraneAngularDeployment
ANDES DeliveryKraneBuildDeployDeployment
ANDES DeliveryKraneDeployDeployment
ANDES DeliveryKraneJava11JavaDeployment
ANDES DeliveryKraneJava17JavaDeployment
ANDES DeliveryKraneJava8JavaDeployment
ANDES DeliveryKraneNestJSDeployment
ANDES DeliveryKranePythonDeployment
ANDES DeliveryKranePythonDeploymentV1
ANDES DeliveryKraneReactDeployment
ANDES DeliveryKubectlSecretsDeployment
ANDES DeliveryNpmMobilePublish
ANDES DeliveryNpmPublish
ANDES DeliverySecretDeployment
ANDES DeliveryShutdownNamespaceDeployment
ANDES DeliveryStartupNamespaceDeployment
ANDES DeliverySuperTest
ANDES DeliverySuperTestDeployment
ANDES DeliveryWebDriverDeployment
CROSSansible
CROSSAnsibleConfigurationManager
CROSSBashDeploy
CROSSWeblogicDataSourceDeploy
CROSSWeblogicDeployment
CROSSWeblogicNoFwkDeployment
PCICloudFunctionPCIDeploy
PCIKraneJava17JavaPCIDeployment
PCIKraneNodejsPCIDeployment
PCIKubectlJava17PCIDeployment
PCIRollbackPCI
RUNWAYComposerEMXDeployment
RUNWAYHelmAngularEMXDeployment
RUNWAYHelmJava17EMXDeployment
RUNWAYHelmLiquibaseEMXDeployment
RUNWAYHelmNestJSEMXDeployment
RUNWAYKraneAngularEMXDeployment
RUNWAYKraneDeployEMXDeployment
RUNWAYKraneJava11EMXDeployment
RUNWAYKraneJava17EMXDeployment
RUNWAYKraneNestJSEMXDeployment

Migration with ChatBot​

  1. In Google Chat, in the Apps section (bottom of the left bar) select Find apps.
  2. Search for the App called ANDES Bot and install it.
  3. Now you can interact with the ChatBot to request different actions related to the platform.
More information at

https://docsrepo.appslatam.com/spaces/PLAT/pages/205381803/Como+agregar+Chatbot+Delivery-Plataforma

LATAM email entry

To migrate a project from CloudBees to Gitlab CI/CD, you must request the pipeline creation using the ChatBot as follows:

Request pipeline migration
8.2 https://gitlab.com/latamairlines/path/sub-path/project
  • This process will create a Jira ticket to track the migration process.
  • Once the migration is finished, you will be notified through the same created ticket.
  • In the gitlab project, a .gitlab-ci.yml file will be created with the pipeline definition based on framework-2, in a dedicated branch for review and adjustments.
LATAM email entry
tip

In case of having a pipeline that experiences any error that does not allow its normal deployment, report it via ticket in option 8.4 of the Chatbot.