Pushing images to registry in Jenkins - Time & Space Complexity

Time Complexity: Pushing images to registry

O(n)

Understanding Time Complexity

When pushing images to a registry using Jenkins, it is important to understand how the time taken grows as the image size or number of images increases.

We want to know how the work done by Jenkins changes when we push more or larger images.

Scenario Under Consideration

Analyze the time complexity of the following Jenkins pipeline snippet.

pipeline {
  agent any
  stages {
    stage('Build and Push') {
      steps {
        script {
          docker.build('my-image:latest')
          docker.withRegistry('https://registry.example.com', 'creds') {
            docker.image('my-image:latest').push()
          }
        }
      }
    }
  }
}

This code builds a Docker image and pushes it to a remote registry.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: Uploading image layers to the registry.
• How many times: Once per layer in the image, which depends on image size and complexity.

How Execution Grows With Input

The time to push grows roughly with the number of layers and their sizes.

Input Size (layers)	Approx. Operations (uploads)
10	10 uploads
100	100 uploads
1000	1000 uploads

Pattern observation: The work grows linearly as the number of layers increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to push grows directly in proportion to the number of image layers.

Common Mistake

[X] Wrong: "Pushing an image always takes the same time regardless of size or layers."

[OK] Correct: Larger images with more layers require more uploads, so pushing takes longer.

Interview Connect

Understanding how pushing images scales helps you explain pipeline performance and troubleshoot delays in real projects.

Self-Check

"What if we pushed multiple images in parallel? How would the time complexity change?"