On Thu, Dec 12, 2013 at 4:54 AM, James Nord (jnord) <[email protected]> wrote:
> although the actual job that
> the trigger will be added to will eventually be some form of
> hudson.model.Job
Indeed a FreestyleProject, in the example given.
> when the configuration jelly is called it’s not actually
> the job that’s being configured but the template instance – which isn’t even
> a Hudson.model.Job.
Correct, using JobProperty.getJobOverrides the ./configure binding is replaced.
I think the problematic assumption is that ${it} is a job. You can use
StaplerRequest.findAncestorObject(AbstractProject.class) (checking the
result for null) to find the project being configured. That is, of
course, if you actually need this, though it seems ${trigger} is not
used anyway.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" 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/groups/opt_out.
