Sounds promising. I've never used Groovy. Does it allow socket connections
to it?

On Wed, Mar 27, 2013 at 5:25 AM, Mandeville, Rob <[email protected]>wrote:

>  I’m looking at tackling this sort of thing myself.  I don’t think that a
> POST would work unless you told Jenkins to reload from disk, which would
> abort any running jobs (I could be wrong…).  When I have the cycles to get
> into this, I’m going to use the Groovy and Scriptler plugins.  This will
> allow me to run code within the Jenkins server, so it should allow me to do
> anything I could do at the GUI level.  I’ve already done this to
> automatically disable and re-enable sets of slave nodes (so that I can
> rebuild their shared database server from scratch once a week).****
>
> ** **
>
> --Rob****
>
> ** **
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *J Arrizza
> *Sent:* Tuesday, March 26, 2013 4:24 PM
> *To:* [email protected]
> *Subject:* Re: main config changes programatically?****
>
> ** **
>
> Yes, the job configs are working great.****
>
> ** **
>
> But getting the root config.xml is not working. I've tried a bunch of
> things:****
>
>    xx/jenkins/api/xml****
>
>    xx/jenkins/api/xml?depth=1****
>
>    xx/jenkins/api/xml?depth=2****
>
>    xx/jenkins/api/xml?depth=999****
>
>    xx/jenkins/config.xml****
>
>    xx/jenkins/api/config.xml****
>
>    xx/jenkins/api/xml/config.xml****
>
> ** **
>
> Either I get partial contents of the config.xml or 404s.****
>
> ** **
>
> I haven't tried POSTing the config.xml but I strongly suspect that it
> won't work because the GET doesn't.****
>
> ** **
>
> Does anyone know if the REST interface supports these changes?****
>
> ** **
>
> John****
>
> ** **
>
> On Tue, Mar 26, 2013 at 5:45 AM, Nathan Overbey <[email protected]>
> wrote:****
>
> Have you tried posting it to /config.xml ?  I know that works for
> /job/xyz/config.xml****
>
> ** **
>
> --
> 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].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>  ****
>
>  The information in this message is for the intended recipient(s) only
> and may be the proprietary and/or confidential property of Litle & Co.,
> LLC, and thus protected from disclosure. If you are not the intended
> recipient(s), or an employee or agent responsible for delivering this
> message to the intended recipient, you are hereby notified that any use,
> dissemination, distribution or copying of this communication is prohibited.
> If you have received this communication in error, please notify Litle & Co.
> immediately by replying to this message and then promptly deleting it and
> your reply permanently from your computer.
>
> --
> 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].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to