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

Parameterized Remote Trigger Plugin fails with 'FATAL: Invalid JSON String' after triggering the remote build

    Details

    • Similar Issues:

      Description

      I've a local jenkins server and provided a remote jenkins server.

      My local build is triggering the remote build, which is running and being built successfully, but the local job fails with the following exception:

      Triggering this remote job: <REMOTE_BUILD_JOB>
      Not checking if the remote job <REMOTE_BUILD_JOB> is building.
      This job is build #[12] on the remote server.
      Triggering remote job now.
      FATAL: Invalid JSON String
      net.sf.json.JSONException: Invalid JSON String
      	at net.sf.json.JSONSerializer.toJSON(JSONSerializer.java:143)
      	at net.sf.json.JSONSerializer.toJSON(JSONSerializer.java:103)
      	at net.sf.json.JSONSerializer.toJSON(JSONSerializer.java:84)
      	at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.sendHTTPCall(RemoteBuildConfiguration.java:698)
      	at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:529)
      	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784)
      	at hudson.model.Build$BuildExecution.build(Build.java:199)
      	at hudson.model.Build$BuildExecution.doRun(Build.java:160)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565)
      	at hudson.model.Run.execute(Run.java:1670)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      	at hudson.model.ResourceController.execute(ResourceController.java:88)
      	at hudson.model.Executor.run(Executor.java:231)
      

      Any suggestions what could be wrong?

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          Maurice W.: Looks like you hit a bug in maven release plugin when releasing (search the Jenkins mailing list for a fix). You uploaded a snapshot build instead of a proper release. There is no 2.1.2 release available for download.

          Release builds: http://repo.jenkins-ci.org/simple/releases/org/jenkins-ci/plugins/Parameterized-Remote-Trigger/
          Snapshot builds: http://repo.jenkins-ci.org/simple/snapshots/org/jenkins-ci/plugins/Parameterized-Remote-Trigger/

          Show
          danielbeck Daniel Beck added a comment - Maurice W. : Looks like you hit a bug in maven release plugin when releasing (search the Jenkins mailing list for a fix). You uploaded a snapshot build instead of a proper release. There is no 2.1.2 release available for download. Release builds: http://repo.jenkins-ci.org/simple/releases/org/jenkins-ci/plugins/Parameterized-Remote-Trigger/ Snapshot builds: http://repo.jenkins-ci.org/simple/snapshots/org/jenkins-ci/plugins/Parameterized-Remote-Trigger/
          Hide
          mskorna Maik Skorna added a comment -

          @Maurice W. please recheck your Release, we cannot find the 2.1.2 version under Releases.

          Show
          mskorna Maik Skorna added a comment - @Maurice W. please recheck your Release, we cannot find the 2.1.2 version under Releases.
          Hide
          morficus Maurice W. added a comment - - edited

          I was not aware of the maven-release-plugin bug - sorry for the inconvenience.

          Release 2.1.3 has been pushed, and I confirmed that it was correct this time (http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/Parameterized-Remote-Trigger)

          Show
          morficus Maurice W. added a comment - - edited I was not aware of the maven-release-plugin bug - sorry for the inconvenience. Release 2.1.3 has been pushed, and I confirmed that it was correct this time ( http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/Parameterized-Remote-Trigger )
          Hide
          morficus Maurice W. added a comment -

          Originally fixed back in April with version 2.1.2, but was never released because of a bug in the "maven release plugin" when using git 1.8.5.

          It should now be available in version 2.1.3

          Show
          morficus Maurice W. added a comment - Originally fixed back in April with version 2.1.2, but was never released because of a bug in the "maven release plugin" when using git 1.8.5. It should now be available in version 2.1.3
          Hide
          daniloichaves Danilo Ischiavolini Chaves added a comment -

          I have the same problem.

          Show
          daniloichaves Danilo Ischiavolini Chaves added a comment - I have the same problem.

            People

            • Assignee:
              morficus Maurice W.
              Reporter:
              mskorna Maik Skorna
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: