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 section through the UI.
I thought it was the same, though the UI added a bunch of extra sections to
the xml unrelated to my specific change.

Thanks again for the help.

Chris

On Thu, 8 Aug 2019 at 08:12, Reinhold Füreder <[email protected]> wrote:

> Hi Chris,
>
>
>
> after re-reading also your initial email I have the feeling my pipeline
> focused/related answer is not helpful at all, as you are not using pipeline
> jobs, but presumably freestyle jobs?
>
>
>
> Another very naïve guess:
>
>    - Could it be that using the JobDSL configure { } block changes the
>    “config.xml” as you think is expected (because you “just” look at the
>    “config.xml”), but in fact it is invalid and during opening the job
>    configuration via Jenkins UI (via “Configure” button) it reads in the
>    invalid “config.xml” and then detects and removes the invalid elements
>    (that were added via JobDSL configure { } block)?
>
>
>
> Please note that I have no idea about JobDSL implementation, so this 2nd
> naïve guess could be even less helpful than the first one :-o
>
>
>
> Reinhold
>
>
>
>
>
> *From:* [email protected] <[email protected]>
> *On Behalf Of *Chris McIntosh
> *Sent:* Donnerstag, 8. August 2019 14:59
> *To:* [email protected]
> *Subject:* Re: Jenkins Overwriting JobDSL Configured Job
>
>
>
> Thanks Reinhold,
>
>
>
> Any way you could think of to get the job to load first before it
> executes?
> I tried reloading all the config from disk which didn't work.  I didn't
> have a chance to try restarting it yet.
>
>
>
> Thanks,
>
>
>
> Chris
>
>
>
> On Wed, 7 Aug 2019 at 23:54, Reinhold Füreder <[email protected]>
> wrote:
>
> Hi Chris,
>
>
>
> just a very naive guess:
>
>    - there are certain pipeline options or also called pipeline job
>    properties (e.g. build discarder policy or pipeline triggers or pipeline
>    parameters) that lead to updates of the pipeline job config once the
>    corresponding “properties” step (of scripted) pipeline is executed
>
>
>
> HTH Reinhold
>
>
>
>
>
> *From:* [email protected] <[email protected]>
> *On Behalf Of *Chris McIntosh
> *Sent:* Mittwoch, 7. August 2019 22:25
> *To:* [email protected]
> *Subject:* Jenkins Overwriting JobDSL Configured Job
>
>
>
> 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 config.xml file for the job is updated as
> expected with the plugin configuration.
>
> When i go to open the job in the Jenkins UI the plugin is not configured.
> When I open the config.xml file for the job on the Jenkins Master
> filesystem, the config has been reverted somehow to remove the config block
> my jobDsl job has defined.
>
> I configured auditd to watch the config file and I see two log entries
> done by the jenkins user within a few seconds of each other indicating to
> me that something in Jenkins is causing the job config to get overwritten
> after my seed job has defined the job.
>
> Anybody have any clue how I can go about debugging this?
>
> Jenkins master is running on Ubuntu 18.04.  I can provide any other info
> needed.
>
> Thanks,
>
>
>
> Chris
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAJq9cAoMLWof5Y9nrQ5Ee0WxDVVqs8QP8NfKQ5r5c1WiuM2pdA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAJq9cAoMLWof5Y9nrQ5Ee0WxDVVqs8QP8NfKQ5r5c1WiuM2pdA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/AM0PR01MB61478359E40DF5C9521DE825F7D70%40AM0PR01MB6147.eurprd01.prod.exchangelabs.com
> <https://groups.google.com/d/msgid/jenkinsci-users/AM0PR01MB61478359E40DF5C9521DE825F7D70%40AM0PR01MB6147.eurprd01.prod.exchangelabs.com?utm_medium=email&utm_source=footer>
> .
>
>
>
>
> --
>
> Touch not the Cat bot a Glove
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAJq9cApTn-zJbWKPEd3AzPjVR5Poh6FetjwQpng7GE--jAX6_Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAJq9cApTn-zJbWKPEd3AzPjVR5Poh6FetjwQpng7GE--jAX6_Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/AM0PR01MB6147A33CFD24AF8C37413FB6F7D70%40AM0PR01MB6147.eurprd01.prod.exchangelabs.com
> <https://groups.google.com/d/msgid/jenkinsci-users/AM0PR01MB6147A33CFD24AF8C37413FB6F7D70%40AM0PR01MB6147.eurprd01.prod.exchangelabs.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Touch not the Cat bot a Glove

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAJq9cAqtzzW-a%3DCkf023MzddDMr7S6DWpNhA-OBN_o3RwS40mQ%40mail.gmail.com.

Reply via email to