Custom notification logic in Jenkins - Time & Space Complexity

Time Complexity: Custom notification logic

O(n)

Understanding Time Complexity

When Jenkins sends notifications based on build results, it runs some code to decide who to notify.

We want to know how the time it takes grows as the number of recipients or conditions increases.

Scenario Under Consideration

Analyze the time complexity of the following Jenkins pipeline snippet.

pipeline {
  agent any
  stages {
    stage('Notify') {
      steps {
        script {
          def users = ['alice', 'bob', 'carol', 'dave']
          users.each { user ->
            if (user.startsWith('a') || user.startsWith('b')) {
              echo "Notify ${user}"
            }
          }
        }
      }
    }
  }
}
    

This code loops through a list of users and sends notifications only to those whose names start with 'a' or 'b'.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through the list of users with each.
• How many times: Once for each user in the list.

How Execution Grows With Input

As the number of users grows, the code checks each user once.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The number of operations grows directly with the number of users.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the notification logic grows in a straight line as the user list gets bigger.

Common Mistake

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

[OK] Correct: Because the code checks each user one by one, more users mean more checks and more time.

Interview Connect

Understanding how loops affect time helps you explain how your code scales in real projects.

Self-Check

"What if we added nested loops to notify users based on multiple conditions? How would the time complexity change?"

Practice

1. What is the main purpose of using custom notification logic in Jenkins pipelines?

easy

A. To send notifications for every build regardless of status

B. To restart the Jenkins server automatically after each build

C. To disable all notifications permanently

D. To send notifications only when specific build conditions are met

Solution

1. Step 1: Understand notification goals

   Custom notification logic aims to reduce noise by sending alerts only when necessary.

2. Step 2: Identify correct behavior

   Sending notifications only on specific build results (like failure) keeps the team focused.

3. Final Answer:

   To send notifications only when specific build conditions are met -> Option D

4. Quick Check:

   Custom notifications = selective alerts [OK]

Hint: Think about reducing alert noise to stay focused [OK]

Common Mistakes:

• Assuming notifications should always be sent
• Confusing disabling notifications with custom logic
• Believing Jenkins restarts after every build

2. Which Jenkins pipeline syntax correctly checks if the build failed before sending a notification?

easy

A. if (currentBuild.result = 'FAILURE') { notify() }

B. if (build.status == 'SUCCESS') { notify() }

C. if (currentBuild.currentResult == 'FAILURE') { notify() }

D. if (currentBuild.currentResult === FAILURE) { notify() }

Solution

1. Step 1: Identify correct property and comparison

   Use currentBuild.currentResult to get build status and compare with string 'FAILURE'.

2. Step 2: Check syntax correctness

   if (currentBuild.currentResult == 'FAILURE') { notify() } uses correct equality operator (==) and string comparison.

3. Final Answer:

   if (currentBuild.currentResult == 'FAILURE') { notify() } -> Option C

4. Quick Check:

   Correct property and comparison = if (currentBuild.currentResult == 'FAILURE') { notify() } [OK]

Hint: Use currentBuild.currentResult with 'FAILURE' string and == [OK]

Common Mistakes:

• Using single equals (=) instead of double (==)
• Comparing to SUCCESS instead of FAILURE
• Missing quotes around 'FAILURE'
• Using undefined variable FAILURE without quotes

3. Given this Jenkins pipeline snippet:

post {
  failure {
    script {
      if (currentBuild.previousBuild?.result == 'SUCCESS') {
        notify('Build failed after success')
      }
    }
  }
}

What happens if the previous build was successful and the current build failed?

medium

A. Notification 'Build failed after success' is sent

B. No notification is sent

C. Notification is sent only if current build succeeded

D. Pipeline throws a syntax error

Solution

1. Step 1: Analyze condition in failure block

   The post.failure block runs only if current build failed. Inside, it checks if previous build result was 'SUCCESS'.

2. Step 2: Evaluate condition outcome

   If previous build was successful and current failed, condition is true, so notify is called with the message.

3. Final Answer:

   Notification 'Build failed after success' is sent -> Option A

4. Quick Check:

   Previous success + current failure triggers notification [OK]

Hint: Check previousBuild?.result and current failure block [OK]

Common Mistakes:

• Thinking notification sends on success builds
• Ignoring the safe navigation operator '?'
• Assuming syntax error due to optional chaining

4. You wrote this Jenkins pipeline snippet to notify only on failure after success:

post {
  failure {
    script {
      if (currentBuild.previousBuild.result == 'SUCCESS') {
        notify('Failed after success')
      }
    }
  }
}

But it sometimes throws a NullPointerException. What is the likely cause?

medium

A. notify function is undefined

B. previousBuild can be null, so accessing result causes error

C. failure block cannot contain if statements

D. currentBuild.previousBuild.result is always 'FAILURE'

Solution

1. Step 1: Identify potential null values

   currentBuild.previousBuild can be null if no previous build exists.

2. Step 2: Understand error cause

   Accessing result on null causes NullPointerException. Safe navigation operator ?. avoids this.

3. Final Answer:

   previousBuild can be null, so accessing result causes error -> Option B

4. Quick Check:

   Null previousBuild causes error without safe navigation [OK]

Hint: Use ?. to safely access previousBuild properties [OK]

Common Mistakes:

• Ignoring possibility of null previousBuild
• Assuming notify is always defined
• Thinking failure block disallows if statements

5. You want to send a notification only when the build status changes from SUCCESS to FAILURE or from FAILURE to SUCCESS. Which Jenkins pipeline snippet correctly implements this logic?

hard

A. post {
failure {
script {
if (currentBuild.previousBuild?.result == 'SUCCESS') {
notify('Failed after success')
}
}
}
success {
script {
if (currentBuild.previousBuild?.result == 'FAILURE') {
notify('Succeeded after failure')
}
}
}
}

B. post {
success {
notify('Build succeeded')
}
failure {
notify('Build failed')
}
}

C. post {
always {
script {
if (currentBuild.previousBuild?.result != currentBuild.currentResult) {
notify('Build status changed')
}
}
}
}

D. post {
always {
notify('Build finished')
}
}

Solution

1. Step 1: Understand the requirement

   Notify only when build status flips between SUCCESS and FAILURE, not on every build.

2. Step 2: Analyze each option

   post { failure { script { if (currentBuild.previousBuild?.result == 'SUCCESS') { notify('Failed after success') } } } success { script { if (currentBuild.previousBuild?.result == 'FAILURE') { notify('Succeeded after failure') } } } } checks previous build result and current build result in success and failure blocks separately, sending notifications only on status change.

3. Final Answer:

   post { failure { script { if (currentBuild.previousBuild?.result == 'SUCCESS') { notify('Failed after success') } } } success { script { if (currentBuild.previousBuild?.result == 'FAILURE') { notify('Succeeded after failure') } } } } -> Option A

4. Quick Check:

   Status change detection needs previousBuild checks in success and failure blocks [OK]

Hint: Check previousBuild result differs from current in success and failure blocks [OK]

Common Mistakes:

• Sending notifications on every build regardless of status change
• Not checking previous build result
• Using always block without condition