-
Bug
-
Resolution: Fixed
-
Critical
-
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
- is related to
-
JENKINS-15834 It's not possible to specify multiple property files in parametrised trigger
-
- Reopened
-
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?