Backup and restore strategies in Jenkins - Time & Space Complexity

Time Complexity: Backup and restore strategies

O(n)

Understanding Time Complexity

When using Jenkins to automate backup and restore tasks, it's important to understand how the time needed grows as the amount of data increases.

We want to know how the backup or restore process scales when handling more files or larger data.

Scenario Under Consideration

Analyze the time complexity of the following Jenkins pipeline snippet.

pipeline {
  agent any
  stages {
    stage('Backup') {
      steps {
        script {
          def files = findFiles(glob: '**/*')
          for (file in files) {
            sh "cp ${file.path} /backup/location/"
          }
        }
      }
    }
  }
}

This code finds all files in the workspace and copies each one to a backup location.

Identify Repeating Operations

Look at what repeats as the input grows.

• Primary operation: Loop over all files found by findFiles.
• How many times: Once for each file in the workspace.

How Execution Grows With Input

As the number of files increases, the number of copy commands grows the same way.

Input Size (n)	Approx. Operations
10	10 copy commands
100	100 copy commands
1000	1000 copy commands

Pattern observation: The work grows directly with the number of files; doubling files doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the backup time increases in a straight line as the number of files grows.

Common Mistake

[X] Wrong: "The backup time stays the same no matter how many files there are."

[OK] Correct: Each file needs to be copied, so more files mean more work and more time.

Interview Connect

Understanding how backup tasks scale helps you design efficient pipelines and shows you can think about real-world automation challenges clearly.

Self-Check

"What if we changed the backup to copy only files modified in the last day? How would the time complexity change?"