Build status badges in Jenkins - Time & Space Complexity

Time Complexity: Build status badges

O(n)

Understanding Time Complexity

We want to understand how the time to generate build status badges changes as the number of builds grows.

How does the system handle more builds when creating these badges?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        script {
          def status = currentBuild.currentResult
          echo "Build status is: ${status}"
        }
      }
    }
  }
}
    

This code gets the current build status and prints it, which is used to create a build status badge.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Accessing the current build status once per build.
• How many times: Exactly once per build execution.

How Execution Grows With Input

Each build fetches its status once, so the time to generate a badge grows directly with the number of builds.

Input Size (n)	Approx. Operations
10	10 status fetches
100	100 status fetches
1000	1000 status fetches

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

Final Time Complexity

Time Complexity: O(n)

This means the time to generate badges grows in direct proportion to the number of builds.

Common Mistake

[X] Wrong: "Generating a badge is instant and does not depend on the number of builds."

[OK] Correct: Each build requires checking its status, so more builds mean more work to generate badges.

Interview Connect

Understanding how tasks scale with input size is a key skill. It helps you design systems that stay fast even as they grow.

Self-Check

"What if we cached build statuses instead of fetching them every time? How would the time complexity change?"