-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
Hi.
Now, the trigger triggerRemoteJob step in pipelines requires to be executed in some "node" block. It would be better to remove this dependency, like the regular build job step.
[JENKINS-54201] Allow the tigger to work without any "node" wrappers
Description |
Original:
Hi. Now, the trigger triggerRemoteJob step in pipelines requires to be executed in some "node" block. It would be better to remove this dependency, like the reggular build job step. |
New:
Hi. Now, the trigger triggerRemoteJob step in pipelines requires to be executed in some "node" block. It would be better to remove this dependency, like the regular build job step. |
Hi, any news on this issue? I'm hitting the same problem. Is there a reason that the plugin has to be executed from inside a node block?
I suspect not, as the Javadoc here explains:
In the BuildContext constructor, the workspace FilePath is Nullable, but when I try to execute a call outside of a node block, I get the following error: