Run GitLab CI/CD
NaC Introduction
  • Introduction
  • NaC Introduction
  • Manual Validation
  • CXTM Introduction
  • CXTM Projects
  • CXTM Test Cases
  • CXTM Test Automation
  • CXTM Git Integration
  • CXTM Batches
  • CXTM Notifications
  • Final Deployment
  • CXTM Reporting
  • CXTM References
  • Bonus Content

Review & Run GitLab CI/CD pipeline

With your infrastructure code and pipeline configuration committed to your branch, the next step is to create a merge request. This merge request triggers the Continuous Integration (CI) pipeline, which executes the validate, plan, and deploy stages to automate the Nexus fabric configuration deployment.


Step 1 - Review the GitLab Pipeline Execution

  1. Return to GitLab repo by clicking on the LTROPS-2711 project name on the left side menu.



Step 2 - Create a Merge Request

From your GitLab project page:

  1. Click Create merge request


Step 3 - Open Merge Request

In the New merge request window, perform the following:

  1. Insert a description: Initiate nexus fabric configuration on the spine S1,S2 and leaf L1,L2 switches with system, interface, and BGP configurations
  2. Click Create merge request


Step 4 - Navigate to Pipeline

Navigate to the pipeline that was launched when you opened your merge request:

  1. Click the number for the merge request pipeline number that comes after Merge request pipeline


Step 5 - Review Overall Pipeline

At this point, you should have successfully triggered the CI pipeline for your proposed initial deployment configuration. The screenshots below show a completed and Passed pipeline. If your own pipeline is still running, please wait until all your pipeline stages have completed before proceeding.


Alert

Notify your proctor if any stages of your pipeline have Failed before moving on.


Step 6 - Navigate to Validate Stage

The validate stage checks the syntax of your Terraform configuration and YAML files. Let's review the results.

  1. Click on the validate stage to view the validation job execution results.

  2. Review the pipeline execution to ensure the validation job completed successfully.
  3. Click the pipeline number on the right-side pane.


Step 7 - Navigate to Plan Stage

The plan stage generates an execution plan that identifies which resources will be created, modified, or destroyed on your Nexus fabric.

  1. Click on the plan stage to view the plan stage execution results.

  2. Review the pipeline execution to ensure the plan job completed successfully.
  3. Click the pipeline number on the right-side pane.


Step 8 - Navigate to Deploy Stage

The deploy stage applies the configuration changes to your Nexus fabric by executing the Terraform apply.

  1. Click on the deploy stage to view the deployment execution results.

  2. Review the pipeline execution to ensure the deploy job completed successfully.
  3. Click the pipeline number on the right-side pane.


Step 9 - Return to Merge Request to Complete the Merge

After reviewing the deployment results, return to your merge request to complete the merge and integrate your changes into the main branch.

  1. Click on the Merge requests on the left side menu to return to the merge request page.

  2. Click on the open merge request Fabric deployment to view the merge request details.

  3. Click the Merge button to complete the merge and integrate your fabric deployment changes into the main branch.

  4. Verify that the merge was successful. You should see a confirmation message indicating that the changes have been merged into the main branch.

  5. Return to the VS Code Server browser tab to synchronize your local workspace with the remote repository.
  6. Switch to the main branch by running the following command in the VS Code Server terminal: 

    
git checkout main
  7. Pull the latest changes from the remote main branch to update your local workspace: 

    
git pull

    Your local workspace is now synchronized with the remote repository. Continue to the next section to manually check the deployment.