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

missing parameter file does not prevent downstream job from running even though it says it will

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • parameterized-trigger-plugin
    • None
    • Jenkins 1.463 and latest plugin

      We have a file imagename.txt with a simple key of:
      imagename=foo.tar

      The file imagename.txt does not exist as see in the log output below but it still runs anyway.

       
14:08:56  [parameterizedtrigger] Could not trigger downstream project, as properties fileimagename.txt did not exist.
14:08:56  Triggering a new build of foojob_nightly #1205

      Also, not sure why it displays fileimagename.txt over imagename.txt

          [JENKINS-14211] missing parameter file does not prevent downstream job from running even though it says it will

          Peter Kline created issue -

          cjo9900 added a comment -

          The output of "fileimagename.txt" instead of "file imagename.txt" was corrected in 2.15,
          commit: https://github.com/jenkinsci/parameterized-trigger-plugin/commit/5f243693cec9ceea46f085e58afac949e6cf9ac5

          Is the checkbox "Trigger build without parameters" checked?
          If this is checked the downstream project will always be started even if the file is missing so this is not an error
          Section of code providing behaviour

          If it still occurs please comment with more actual configuration you have.
          preferable job's config.xml file if possible.

          Which Version of the plugin 2.14? from the description bug mentioned above

          Is this in the Postbuild section or as a build step?

          How are you defining the "Parameters from a properties file" item,
          Is this a hard-coded string or is it a ENV variable that is being expanded?

          Is the checkbox "Trigger build without parameters" checked?

          cjo9900 added a comment - The output of "fileimagename.txt" instead of "file imagename.txt" was corrected in 2.15, commit: https://github.com/jenkinsci/parameterized-trigger-plugin/commit/5f243693cec9ceea46f085e58afac949e6cf9ac5 Is the checkbox "Trigger build without parameters" checked? If this is checked the downstream project will always be started even if the file is missing so this is not an error Section of code providing behaviour If it still occurs please comment with more actual configuration you have. preferable job's config.xml file if possible. Which Version of the plugin 2.14? from the description bug mentioned above Is this in the Postbuild section or as a build step? How are you defining the "Parameters from a properties file" item, Is this a hard-coded string or is it a ENV variable that is being expanded? Is the checkbox "Trigger build without parameters" checked?

          cjo9900 added a comment -

          Fixed as part of correction for JENKINS-15834

          cjo9900 added a comment - Fixed as part of correction for JENKINS-15834
          cjo9900 made changes -
          Link New: This issue is related to JENKINS-15834 [ JENKINS-15834 ]
          cjo9900 made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          cjo9900 made changes -
          Assignee Original: huybrechts [ huybrechts ] New: cjo9900 [ cjo9900 ]

          Martin Ba added a comment -

          I am running Jenkins 1.480.3 (LTS) and for me everything works.
          Specifically I tested with:

          • Trigger parameterized build on other projects
          • Trigger build withoput parameters [ ] (not checked)
          • Some predefined parameters
          • Some from a file (with Don't trigger if any files are missing [x] checked.)

          => If the file is missing, downstream build is correctly not triggered.

          Martin Ba added a comment - I am running Jenkins 1.480.3 (LTS) and for me everything works. Specifically I tested with: Trigger parameterized build on other projects Trigger build withoput parameters [ ] (not checked) Some predefined parameters Some from a file (with Don't trigger if any files are missing [x] checked.) => If the file is missing, downstream build is correctly not triggered.

          cjo9900 added a comment -

          @Martin
          I assume that you are using 2.17 version of the plugin which has the fix indicated in JENKINS-15834.

          cjo9900 added a comment - @Martin I assume that you are using 2.17 version of the plugin which has the fix indicated in JENKINS-15834 .

          cjo9900 added a comment -

          Fixed in 2.17

          cjo9900 added a comment - Fixed in 2.17
          cjo9900 made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

            cjo9900 cjo9900
            peter_kline Peter Kline
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: