Liquibase Pipeline for eCargo in GitLab

Common Problems or Queries

• I need to configure Liquibase pipeline in GitLab for eCargo
• Migration from Jenkins to GitLab for repositories with Liquibase
• Required validations for repositories using Jenkins towards GitLab

Solution

Configuring Liquibase pipeline in GitLab requires specific validations when migrating from Jenkins, especially in development environment.

Steps to configure Liquibase pipeline:

1. Current repository analysis

   • Review existing Jenkins configuration
   • Identify dependencies and specific configurations
   • Document current Liquibase scripts and processes

2. Pre-migration validations

   • Verify that all changesets are correctly versioned
   • Confirm that target databases are accessible
   • Validate database credentials and permissions

3. GitLab configuration

   • Create .gitlab-ci.yml file with Liquibase stages
   • Configure environment variables for DB connections
   • Establish execution rules per environment (DEV/INTG/PROD)

4. DEV environment testing

   • Execute pipeline in development environment
   • Validate that changesets are applied correctly
   • Verify rollback and Liquibase functionalities

5. Documentation and training

   • Create documentation for new process
   • Train team on GitLab pipeline usage
   • Establish troubleshooting procedures

Important considerations:

• Validations required with repositories using Jenkins towards GitLab in DEV
• Verify Liquibase version compatibility
• Ensure database connections work correctly

Case information:

• Type: New ANDES Feature Request
• Environment: DEV
• Responsible: ANDES Developer
• Reference ticket: ANDES-309