-
Improvement
-
Resolution: Won't Fix
-
Major
-
None
[parameterizedtrigger] Could not trigger downstream project, as properties fileimagename.txt did not exist.
11:08:14 Waiting for the completion of run_full_smoke
11:20:48 run_full_smoke #709 completed. Result was ABORTED
11:20:48 Build step 'Trigger/call builds on other projects' marked build as failure
the file imagename.txt is missing because my build failed. I don't want this to get triggered in the case when the build fails.
[JENKINS-13362] triggered parameterized run even though a parameter is not set. first it complains that is isn't set and isn't able to trigger it, then it triggers it.
Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 143826 ] | New: JNJira + In-Review [ 190764 ] |
The problem here is that the builds are always triggered by the build step, regardless of if there are parameters for it.
The message is written to the log by the FileBuildParameter item which should just be indicating that the file does not exist.
and the build step should handle the case when there are no parameters to pass.