Build history and logs in Jenkins - Time & Space Complexity

Time Complexity: Build history and logs

O(n)

Understanding Time Complexity

We want to understand how the time to retrieve build history and logs changes as the number of builds grows.

How does Jenkins handle more builds when showing history and logs?

Scenario Under Consideration

Analyze the time complexity of this Jenkins pipeline snippet that archives build logs for each build.

pipeline {
  agent any
  stages {
    stage('Build') {
      steps {
        echo 'Building...'
      }
    }
    stage('Archive Logs') {
      steps {
        archiveArtifacts artifacts: 'logs/**'
      }
    }
  }
}
    

This pipeline runs a build and archives all logs generated during the build for later viewing.

Identify Repeating Operations

Look at what repeats when Jenkins stores and retrieves build logs.

• Primary operation: Archiving and storing logs for each build.
• How many times: Once per build, repeated as builds increase.

How Execution Grows With Input

As the number of builds grows, Jenkins stores more logs, so retrieving history takes longer.

Input Size (number of builds)	Approx. Operations
10	10 log archives stored and retrievable
100	100 log archives stored and retrievable
1000	1000 log archives stored and retrievable

Pattern observation: The work to access build history grows linearly with the number of builds.

Final Time Complexity

Time Complexity: O(n)

This means the time to retrieve build history and logs grows directly in proportion to the number of builds.

Common Mistake

[X] Wrong: "Retrieving build logs always takes the same time no matter how many builds exist."

[OK] Correct: Each build adds more logs to store and manage, so more builds mean more data to handle, increasing retrieval time.

Interview Connect

Understanding how build history scales helps you explain system behavior and troubleshoot performance in real Jenkins environments.

Self-Check

"What if Jenkins used a database index for logs? How would that change the time complexity of retrieving build history?"