Docker compose in pipelines in Jenkins - Time & Space Complexity

Time Complexity: Docker compose in pipelines

O(n)

Understanding Time Complexity

We want to understand how running Docker Compose commands inside Jenkins pipelines scales as the number of services grows.

How does the time to start or stop containers change when we add more services?

Scenario Under Consideration

Analyze the time complexity of the following Jenkins pipeline snippet using Docker Compose.

pipeline {
  agent any
  stages {
    stage('Start Services') {
      steps {
        sh 'docker-compose up -d'
      }
    }
    stage('Run Tests') {
      steps {
        sh './run-tests.sh'
      }
    }
    stage('Stop Services') {
      steps {
        sh 'docker-compose down'
      }
    }
  }
}

This pipeline starts multiple Docker services in the background, runs tests, then stops the services.

Identify Repeating Operations

Look for repeated or costly operations inside the pipeline.

• Primary operation: Starting and stopping each Docker service with docker-compose up -d and docker-compose down.
• How many times: Each service is started and stopped once per pipeline run, but internally Docker Compose handles multiple services sequentially or in parallel.

How Execution Grows With Input

As the number of services (n) increases, the time to start and stop all services grows roughly in proportion.

Input Size (n)	Approx. Operations
10	Starting and stopping 10 services once each
100	Starting and stopping 100 services once each
1000	Starting and stopping 1000 services once each

Pattern observation: The total time grows roughly linearly as you add more services.

Final Time Complexity

Time Complexity: O(n)

This means the time to start and stop services grows in a straight line as the number of services increases.

Common Mistake

[X] Wrong: "Starting multiple services with Docker Compose happens instantly regardless of how many services there are."

[OK] Correct: Each service needs time to start and stop, so more services mean more total time.

Interview Connect

Understanding how pipeline steps scale with workload helps you design efficient CI/CD processes and explain your reasoning clearly in discussions.

Self-Check

What if we changed the pipeline to start services in parallel using multiple Docker Compose files? How would the time complexity change?