Details

    • Similar Issues:

      Description

      Parameters are not passed onto newly started Naginator jobs.

      Started by Naginator
      [EnvInject] - Loading node environment variables.
      Building in workspace /root/.jenkins/jobs/test/workspace
      Checkout:workspace / /root/.jenkins/jobs/test/workspace - hudson.remoting.LocalChannel@2a2bfd5
      Using strategy: Default
      [workspace] $ /bin/sh -xe /tmp/hudson3453253707221002170.sh
      + python test.py --hostname

      There should be a value after "--hostname" as it is in the original build before failure.

        Attachments

          Activity

          outspoken Ken Garland created issue -
          outspoken Ken Garland made changes -
          Field Original Value New Value
          Labels naginator plugin naginator plugin trigger
          Hide
          outspoken Ken Garland added a comment - - edited

          I've also just tried to setup a build that uses file based parameters with "Set environment variables through a file" and the parameters are not sent to the job at run time.

          Build > Execute shell > Command echo $temp_name

          [envfile] temp_name=test
          [workspace] $ /bin/sh -xe /tmp/hudson2757699259452188104.sh
          + echo

          As you can see, echo has nothing afterwards.

          Show
          outspoken Ken Garland added a comment - - edited I've also just tried to setup a build that uses file based parameters with "Set environment variables through a file" and the parameters are not sent to the job at run time. Build > Execute shell > Command echo $temp_name [envfile] temp_name=test [workspace] $ /bin/sh -xe /tmp/hudson2757699259452188104.sh + echo As you can see, echo has nothing afterwards.
          nhajratw Nayan Hajratwala made changes -
          Assignee Nayan Hajratwala [ nhajratw ]
          Hide
          boinst Ben Ernst added a comment -

          From the looks of the change log, this seems to be fixed in version 1.8

          Version 1.8 - June 12, 2012
          new extension point to configure schedule delay
          fixed delay implementation
          parameter for build are reused on schedule
          limit for number of build attempts after failure

          Show
          boinst Ben Ernst added a comment - From the looks of the change log, this seems to be fixed in version 1.8 Version 1.8 - June 12, 2012 new extension point to configure schedule delay fixed delay implementation parameter for build are reused on schedule limit for number of build attempts after failure
          Hide
          galunto Tomer Galun added a comment -

          Already fixed

          Show
          galunto Tomer Galun added a comment - Already fixed
          galunto Tomer Galun made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 144168 ] JNJira + In-Review [ 190943 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              outspoken Ken Garland
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: