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

Severe polling error when using script trigger

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • scripttrigger-plugin
    • None
    • Scientific Linux 5.5 and Ubuntu 10.10
      Arch: x86_64
      Jenkins 1.480.3 running in standalone with Winstone

    Description

      I find the following in the script trigger logs for the attached test job configuration:
      [ERROR] - SEVERE - Polling error null

      The error disappears when the following tags are removed from the file TestJob/builds/2013-04-10_12-34-47/build.xml:
      <org.jenkinsci.plugins.envinject.EnvInjectPluginAction>
      <build class="build" reference="../../.."/>
      </org.jenkinsci.plugins.envinject.EnvInjectPluginAction>

      Attachments

        Activity

          aszostak Artur Szostak added a comment -

          Script trigger 0.28 has been working fine for a while so closing this ticket.

          aszostak Artur Szostak added a comment - Script trigger 0.28 has been working fine for a while so closing this ticket.
          thetaphi Uwe Schindler added a comment -

          Hi,
          I built the release tag 0.27 from github locally and uploaded the hpi file to jenkins. It seems to work: The node was down and the trigger was able to start it. I will report back if anything else goes wrong.

          Thank you very much, Uwe

          P.S.: (I think next time you don't need to build a new release for every change, testing it with a local build from github is perfectly fine to me!)

          thetaphi Uwe Schindler added a comment - Hi, I built the release tag 0.27 from github locally and uploaded the hpi file to jenkins. It seems to work: The node was down and the trigger was able to start it. I will report back if anything else goes wrong. Thank you very much, Uwe P.S.: (I think next time you don't need to build a new release for every change, testing it with a local build from github is perfectly fine to me!)

          Please test from scripttrigger 0.27

          gbois Gregory Boissinot added a comment - Please test from scripttrigger 0.27

          Code changed in jenkins
          User: Gregory Boissinot
          Path:
          pom.xml
          http://jenkins-ci.org/commit/scripttrigger-plugin/304d50587c698f157438ae5d497875b17eb4c03e
          Log:
          Upgrade to xtrigger-lib 0.23 for JENKINS-17566

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: pom.xml http://jenkins-ci.org/commit/scripttrigger-plugin/304d50587c698f157438ae5d497875b17eb4c03e Log: Upgrade to xtrigger-lib 0.23 for JENKINS-17566

          Code changed in jenkins
          User: Gregory Boissinot
          Path:
          src/main/java/org/jenkinsci/lib/envinject/service/EnvVarsResolver.java
          http://jenkins-ci.org/commit/envinject-lib/c6ce1fe1d0f1d00eb55e9c349f591a2c4ef764f6
          Log:
          Fix JENKINS-17566

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/lib/envinject/service/EnvVarsResolver.java http://jenkins-ci.org/commit/envinject-lib/c6ce1fe1d0f1d00eb55e9c349f591a2c4ef764f6 Log: Fix JENKINS-17566

          People

            gbois Gregory Boissinot
            aszostak Artur Szostak
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: