been
fighting with each other somehow.
Thanks,
Chris
On Tue, 13 Aug 2019 at 08:29, Chris McIntosh
wrote:
> Hi Reinhold,
>
> We are using pipeline jobs via a jenkinsfile.
> I will double check my xml from the configure block vs the xml generated
> by jenkins when manually adding the se
plementation, so this 2nd
> naïve guess could be even less helpful than the first one :-o
>
>
>
> Reinhold
>
>
>
>
>
> *From:* jenkinsci-users@googlegroups.com
> *On Behalf Of *Chris McIntosh
> *Sent:* Donnerstag, 8. August 2019 14:59
> *To:* jenkins
esponding “properties” step (of scripted) pipeline is executed
>
>
>
> HTH Reinhold
>
>
>
>
>
> *From:* jenkinsci-users@googlegroups.com
> *On Behalf Of *Chris McIntosh
> *Sent:* Mittwoch, 7. August 2019 22:25
> *To:* jenkinsci-users@googlegroups.com
> *S
Hey All,
Hoping somebody can shed some light on this.
I am using the jobDsl plugin with a seed job to configure a job.
The job is using a configure {} block to configure some aspect of the job
for a plugin that doesn't have a jobDsl extension (Office365Connector).
When I run the seed job, the co
