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

Upgrading Datadog plugin to 2.6.0 breaks Jenkins

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • None
    • jenkins-version - 2.263.1
      workflow-job - 2.40
      workflow-api - 2.40
      Datadog-plugin - 2.60.1

      Upgrading to Datadog-plugin version 2.60.1 requires the workflow-job plugin to be at least at 2.40 

      After this we witness Jenkins in a zombie state of not able to run builds i.e. via BuildNow, Time triggered, web-hooks. Also to note existing jobs after a graceful restart is stuck and do not continue.
      We see multiple of these in our logs, which is similar to JENKINS-52362 , however rolling back to Datadog-plugin version 1.1 and using workflow-job 2.37 does not create the issue anymore.

      //INFO: Running CpsFlowExecution[Owner[job/branch/build_number]] unresponsive for 3 min 30 sec
      org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0

       

          [JENKINS-64688] Upgrading Datadog plugin to 2.6.0 breaks Jenkins

          Ajay Kumar created issue -
          Ajay Kumar made changes -
          Description Original: Upgrading to *Datadog-plugin version 2.60.1* requires the *workflow-api plugin to be at least at 2.40* 

          After this we witness Jenkins in a zombie state of not able to run builds i.e. via *BuildNow*, *Time triggered, web-hooks*. Also to note existing jobs after a graceful restart is stuck and do not continue.
          We see multiple of these in our logs, which is similar to JENKINS-52362
          {code:java}
          //INFO: Running CpsFlowExecution[Owner[job/branch/build_number]] unresponsive for 3 min 30 sec
          org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0{code}




           
          New: Upgrading to *Datadog-plugin version 2.60.1* requires the *workflow-job plugin to be at least at 2.40* 

          After this we witness Jenkins in a zombie state of not able to run builds i.e. via *BuildNow*, *Time triggered, web-hooks*. Also to note existing jobs after a graceful restart is stuck and do not continue.
           We see multiple of these in our logs, which is similar to JENKINS-52362
          {code:java}
          //INFO: Running CpsFlowExecution[Owner[job/branch/build_number]] unresponsive for 3 min 30 sec
          org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0{code}
           
          Environment Original: jenkins-version - 2.263.1
          workflow-api - 2.40
          Datadog-plugin - 2.60.1
          New: jenkins-version - 2.263.1
          workflow-job - 2.40
          Datadog-plugin - 2.60.1
          Ajay Kumar made changes -
          Environment Original: jenkins-version - 2.263.1
          workflow-job - 2.40
          Datadog-plugin - 2.60.1
          New: jenkins-version - 2.263.1
          workflow-job - 2.40
          workflow-api - 2.40
          Datadog-plugin - 2.60.1
          Ajay Kumar made changes -
          Description Original: Upgrading to *Datadog-plugin version 2.60.1* requires the *workflow-job plugin to be at least at 2.40* 

          After this we witness Jenkins in a zombie state of not able to run builds i.e. via *BuildNow*, *Time triggered, web-hooks*. Also to note existing jobs after a graceful restart is stuck and do not continue.
           We see multiple of these in our logs, which is similar to JENKINS-52362
          {code:java}
          //INFO: Running CpsFlowExecution[Owner[job/branch/build_number]] unresponsive for 3 min 30 sec
          org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0{code}
           
          New: Upgrading to *Datadog-plugin version 2.60.1* requires the *workflow-job plugin to be at least at 2.40* 

          After this we witness Jenkins in a zombie state of not able to run builds i.e. via *BuildNow*, *Time triggered, web-hooks*. Also to note existing jobs after a graceful restart is stuck and do not continue.
           We see multiple of these in our logs, which is similar to JENKINS-52362 , however rolling back to *Datadog-plugin version 1.1* and using *workflow-job 2.37* does not create the issue anymore.
          {code:java}
          //INFO: Running CpsFlowExecution[Owner[job/branch/build_number]] unresponsive for 3 min 30 sec
          org.jenkinsci.plugins.workflow.support.concurrent.Timeout lambda$ping$0{code}
           
          Julia Simon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            datadog Datadog HQ
            akumarmandapati Ajay Kumar
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: