I know of no reason why it would not work identically when wrapped inside a method. Can you reproduce this from scratch? If so, please provide details.

I dried to reproduce it, and it worked. I must have botched up while testing.

Currently you need to manually trim off unnecessary options which default to non-null values: JENKINS-25779

That's good, since it isn't always clear which options are unnecessary.

>> some way to declare a trigger, and another way to declare used repositories

Not sure I follow.

Please skip it. I just have a hard time understanding the role of 'node' for SCM triggers in a workflow (in a Freestyle build the semantics is easier to understand). I've found the time to browse the workflow plugin, and the Jenkins core code (e.g. SCMtrigger, WorkFlowRun), but I still don't understand how an SCM step definition in a node triggers a build. For the time being, I'll stick to the explanation in https://github.com/jenkinsci/workflow-plugin/blob/master/cps-global-lib/README.md

There are two distinct exceptions shown. Do you mean that a freestyle build shows only the first?

No, the freestyle also shows two exceptions (including the NPE). If you still need a trace, please let me know.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to