How to migrate from Bamboo to GitLab CI/CD

Migrating from Bamboo to GitLab CI/CD

• GitLab CI/CD offers an alternative to Bamboo for implementing continuous integration and continuous deployment processes.
• GitLab CI/CD uses a YAML configuration file to define the stages and jobs of a pipeline. This allows for version control and easy replication.
• Code repositories need to be added to a GitLab project for access by CI/CD jobs.
• Triggers can be set in GitLab for automatic job execution based on changes in the repository.
• Bamboo plans can be exported as YAML files and converted to GitLab CI/CD configuration.
• Compliance and security policies can be enforced in GitLab CI/CD pipelines.
• GitLab has a Dependency Proxy feature to maintain a local cache of public images or packages.

Differences between GitLab CI/CD and Bamboo

• Bamboo organizes CI/CD jobs into plans, which are further divided into build and deployment plans. GitLab CI/CD uses a pipeline structure with stages and jobs.
• Bamboo jobs consist of tasks that are specific to technologies or scripts. GitLab CI/CD jobs are composed of script commands.
• GitLab CI/CD allows packaging of required binaries in a custom container image for use in CI/CD processes.
• To deploy to an environment, GitLab uses the "deploy" keyword, while Bamboo relies on artifacts to be picked up and deployed in a separate task.
• Artifacts in GitLab CI/CD are downloaded by default from completed jobs in previous stages, while in Bamboo, artifacts need to be defined with specific names, locations, and patterns.

Example: Build Jobs

• Bamboo build jobs consist of tasks, while GitLab CI/CD jobs are composed of script commands.
• In GitLab CI/CD, the stage for a job is specified using the "stage" keyword, and the script commands to be executed are listed under "script".
• GitLab allows the use of custom container images that contain the necessary binaries for the job.
• Deployments or releases can be triggered using the appropriate keywords in GitLab CI/CD.

Artifacts

• Both GitLab CI/CD and Bamboo support the concept of job artifacts.
• Bamboo artifacts are defined with a name, location, pattern, and optionally the ability to share them with other jobs or plans.
• GitLab CI/CD automatically downloads artifacts from completed jobs in previous stages.

Note: The provided summary is a condensed version and may not cover all the details and nuances of the topic.