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

Parameterized Remote Trigger Plugin is not triggering job in remote jenkins

    Details

    • Type: Bug
    • Status: In Progress (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Labels:
      None
    • Environment:
      Parameterized Remote Trigger Plugin version - 3.0.3
      My Jenkins version - 2.121.2
      Remote Jenkins version - 2.73.3
    • Similar Issues:

      Description

      While triggering remote jenkins job from my local jenkins it was working with the version 2.2.2. But since few weeks it was not triggering, so we have updated the Parameterized Remote Trigger Plugin version from 2.2.2 to 3.0.3. But still the remote jenkins job and was showing the below issue:

      Run condition [Execute Windows Batch commands] enabling perform for step [BuilderChain]
      ERROR: Build step failed with exception
      java.lang.NullPointerException
      at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.evaluateEffectiveRemoteHost(RemoteBuildConfiguration.java:385)
      at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:533)
      at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:514)
      at org.jenkinsci.plugins.conditionalbuildstep.BuilderChain.perform(BuilderChain.java:71)
      at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110)
      at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154)
      at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105)
      at org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder.perform(ConditionalBuilder.java:134)
      at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
      at hudson.model.Build$BuildExecution.build(Build.java:206)
      at hudson.model.Build$BuildExecution.doRun(Build.java:163)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
      at hudson.model.Run.execute(Run.java:1798)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:97)
      at hudson.model.Executor.run(Executor.java:429)
      Build step 'Conditional steps (multiple)' marked build as failure

      In the remote jenkins i have given a folder path, in that particular folder it has around 5 jobs and I wanted to trigger all of them. But it triggers 1st job alone and fails with the above issue.

       

        Attachments

          Activity

          Hide
          roberthencke Robert Hencke added a comment -

          This is a bug not around the URL being null, but around the hostLocks and hostPermits fields being null when deserializing older configurations.

          I have submitted a pull request to fix here:

          https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/47

          Show
          roberthencke Robert Hencke added a comment - This is a bug not around the URL being null, but around the hostLocks and hostPermits fields being null when deserializing older configurations. I have submitted a pull request to fix here: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/47
          Hide
          cashlalala KaiHsiang Chang added a comment -

          PR 47 resolved 

          Show
          cashlalala KaiHsiang Chang added a comment - PR 47  resolved 
          Hide
          totoroliu Rick Liu added a comment - - edited

          Job Jenkins server:
          Jenkins core. v.2.121.3
          Parameterized Remote Trigger Plugin v.3.0.6

          Remote Jenkins server:
          Jenkins core. v.2.121.3

          I still see this error from the job console:

          [Pipeline] triggerRemoteJob
          ################################################################################################################
          Parameterized Remote Trigger Configuration:

          Pipeline code:
          triggerRemoteJob auth: CredentialsAuth(credentials: 'xxxxxxxxxxxxx'),
          blockBuildUntilComplete: false,
          job: 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test',
          parameters: """BUILD=${build}\nLABEL=ECO_${ECO_ID}\nENV=SMOKE_PRODUCTION""", pollInterval: 300

          Show
          totoroliu Rick Liu added a comment - - edited Job Jenkins server: Jenkins core. v.2.121.3 Parameterized Remote Trigger Plugin v.3.0.6 Remote Jenkins server: Jenkins core. v.2.121.3 I still see this error from the job console: [Pipeline] triggerRemoteJob ################################################################################################################ Parameterized Remote Trigger Configuration: job: https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test auth: 'Credentials Authentication' as user 'xxxxxx' (Credentials ID 'xxxxxxxxxxxxx') parameters: [BUILD=5098, LABEL=ECO_130206, ENV=SMOKE_PRODUCTION] blockBuildUntilComplete: false connectionRetryLimit: 5 ################################################################################################################ fail to accquire lock because of timeout, skip locking... Triggering parameterized remote job 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test' Using job-level defined 'Credentials Authentication' as user 'xxxxxx' (Credentials ID 'xxxxxxxxxxxxx') Triggering remote job now. fail to accquire lock because of timeout, skip locking... CSRF protection is disabled on the remote server. fail to accquire lock because of timeout, skip locking... Connection to remote server failed [404] , waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/ , parameters: Retry attempt #1 out of 5 Connection to remote server failed [404] , waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/ , parameters: Retry attempt #2 out of 5 Connection to remote server failed [404] , waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/ , parameters: Retry attempt #3 out of 5 Connection to remote server failed [404] , waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/ , parameters: Retry attempt #4 out of 5 Connection to remote server failed [404] , waiting for to retry - 300 seconds until next attempt. URL: https://jenkins-robot.corp.fortinet.com/queue/item/114603/api/json/ , parameters: Retry attempt #5 out of 5 ERROR: Remote build failed with 'ExceedRetryLimitException' for the following reason: 'Max number of connection retries have been exeeded.'. Pipeline code: triggerRemoteJob auth: CredentialsAuth(credentials: 'xxxxxxxxxxxxx'), blockBuildUntilComplete: false, job: 'https://jenkins-robot.corp.fortinet.com/job/FortiOS_Automated_Test_6.0/job/FOS_Distributed_Smoke_Test', parameters: """BUILD=${build}\nLABEL=ECO_${ECO_ID}\nENV=SMOKE_PRODUCTION""", pollInterval: 300
          Hide
          totoroliu Rick Liu added a comment -

          I'm sorry.
          I was trying to re-open the issue,
          but clicked the wrong butto to resolve the issue.

          Could anyone help me to revert my action?

          Show
          totoroliu Rick Liu added a comment - I'm sorry. I was trying to re-open the issue, but clicked the wrong butto to resolve the issue. Could anyone help me to revert my action?
          Hide
          ukphilj Philip Johnson added a comment -

          Rick Liu - I've run into this issue recently and it seems to occur when I up the polling time from 30 seconds to 300. If I use 30, it works again.

          Show
          ukphilj Philip Johnson added a comment - Rick Liu - I've run into this issue recently and it seems to occur when I up the polling time from 30 seconds to 300. If I use 30, it works again.

            People

            • Assignee:
              cashlalala KaiHsiang Chang
              Reporter:
              dineshkumar_n Dinesh
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: