But jenkins job definitions are cached in memory. I have been fighting this forever since there are fields stored in this cache which are not generally available to the user.
In my case, what I want to do is direct the job to a particular slave, because there is pre-built workspace there that I want the build to run in + I have tested and that slave is not busy + that workspace is not currently in use by any other build. This works the FIRST time you generate a job with a particular name. But the second time, jenkins has cached the name of the server that it successfully ran on. And you can not change it. The jobs are all ci loop jobs, they run all the time, so I need to re-use names to avoid filling up the jobs directory with useless data. And of course I can not reload Jenkins Configuration every time I get a ci loop build. I tried to use a groovy script to force jenkins to reload the configuration for that job only and that did not work at all. On Wednesday, April 13, 2016 at 10:04:34 PM UTC-4, Richard Bywater wrote: > > There's also Jenkins Job Builder - > http://docs.openstack.org/infra/jenkins-job-builder/ - which isn't a > plugin to Jenkins but creates and uploads Jenkins config.xml based off of > YAML. > > Richard. > > On Thu, 14 Apr 2016 at 13:59 Slide <[email protected] <javascript:>> > wrote: > >> There are two options that you might be interested in: >> >> 1) Job DSL plugin - >> https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin >> 2) Pipeline Plugin - >> https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin >> >> Both use a groovy DSL to either generate jobs or run pipelined tasks. >> >> On Wed, Apr 13, 2016 at 6:55 PM Andy Billy <[email protected] >> <javascript:>> wrote: >> >>> hi:) >>> >>> For the more and more jobs needed to be configured ,Is there a better >>> way to configure them other than operating the ui workflow ? >>> if I can write job config script and load it to jenkins ,that is >>> pretty light work。 >>> thanks. >>> >>> -- >>> 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] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/2e60b9ae-ba5c-4feb-86e0-242e48ace19a%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-users/2e60b9ae-ba5c-4feb-86e0-242e48ace19a%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVco8VrTjhAvscf0z5jp5QWq6B9Vv4J5%2Bjp20COk0YDY2A%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVco8VrTjhAvscf0z5jp5QWq6B9Vv4J5%2Bjp20COk0YDY2A%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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/23978218-2595-4df6-a580-2019a1f38296%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
