Hey man, long time :) Hope things are good. I'll keep this in the back pocket but I think the groovy setup is probably more along the lines of what I should use, thanks.
On Tuesday, May 9, 2017 at 10:38:28 AM UTC-7, Kevin Burnett wrote: > > what is up morgan, man? :) > > i just tested this to update a job description (it gets an http 302 when > it works): > > curl -u user:pass -X POST > https://ci.example.com/job/my-hot-job/submitDescription --data-urlencode > "description=FROZEN by [fancy_business_here]" > > maybe someone else knows all about updating jobs from xml files. > > good luck, > kb > > On Monday, May 8, 2017 at 2:06:33 PM UTC-4, Morgan Blackthorne wrote: >> >> We're using Chef automation around configuring our Jenkins jobs. >> Basically chef clones a git repo with the job XML files, and then tells >> Jenkins to use them. >> >> What we want to have is: >> >> 1. One job to edit other jobs description to say "FROZEN by <user X> >> at <date:time>" or to remove the FROZEN line (basically a toggle) >> 2. Chef will then be updated to look at the job XML currently on the >> Jenkins server >> 1. If the description includes FROZEN, skip that job and leave it >> alone >> 2. If the description does not include FROZEN, update the job from >> the XML file >> >> I'm not really up to speed on Groovy, so what's the simplest way to >> approach this? (I already know how to do the XML check for step 2, we can >> just look at the XML over HTTP.) >> > -- 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/6f50c894-b247-4915-be28-f24420d71cb0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
