Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-75065

Job delaying an arbitrary time period between cause and starting

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None

      Job A, triggered via a webhook, experiences significant delays between logging the trigger cause and processing the parameter payload. Delays range from 20 seconds to 10 minutes during peak usage times, while cloned versions of the job exhibit minimal delays (~1 second).

      Job Details:

      • Type: Pipeline
      • Log Rotation: Keep last 100 builds
      • Trigger: Webhook
      • Payload Size:  Typically ~2kb, tested with empty payload.

      Steps Taken to Debug:

      1. Cloned the job (Create new pipeline --> Copy from --> Job A).
      2. Triggered both the cloned job and the original job with an empty payload 5 times each.
      3. Monitored delays between trigger cause logging and payload processing.

      Job A- 

      Cloned job:

      Observed Behavior:

      • Cloned job: ~1-second delay on average.
      • Job A: Delay ranges from 20 seconds to 1 minute 20 seconds.
      • During peak Jenkins usage, Job A delay can reach up to 10 minutes.

      Diagnostics Performed:

      • Reviewed Jenkins logs for Severe/Warning-level messages: None found.
      • Monitored memory and CPU usage during the delay: No significant peaks or signs of resource exhaustion.
      • Compared configurations of Job A and its clone: No notable differences.

       

            Unassigned Unassigned
            tmuster Tomer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: