It depends on how you want to configure jjb to update your jobs. Again we use puppet to execute jjb to update. I've seen others use the same jenkins instance to update the jobs. I mean they setup a jenkins job on the jjb project itself that triggers on every change to the jjb definitions which will update the other jobs.
I see a few solutions to your credentials question. you can maybe use the credentials plugin[1] or you can add a feature that reads the credentials from the JJB configuration file[2], look at the stash section. To add this feature you will need to propose a change[3] similar to the one for stash config. [1] http://docs.openstack.org/infra/jenkins-job-builder/wrappers.html?highlight=credential%20bind#wrappers.credentials-binding [2] http://docs.openstack.org/infra/jenkins-job-builder/execution.html [3] https://review.openstack.org/#/c/212004/ On Monday, August 31, 2015 at 10:50:59 AM UTC-7, milki milk wrote: > > On Monday, August 31, 2015 at 10:27:11 AM UTC-7, Khai Do wrote: >> >> Yes, your general assessment is correct. You can, but do NOT necessarily >> need to use the jenkins DSL plugin to generate jobs since JJB has it's own >> DSL. Not sure if 'out-of-band' mean separate executable, separate jenkins >> job definitions, or in repo vs out of repo. JJB does have an executable >> that you run and it does read it's own yaml based definition files. The >> JJB definition files will generate the actual jenkins xml files that define >> the jenkins job and deploy those to the jenkins master. JJB provides a >> path[1] option so the yml definitions can live anywhere, in your project's >> repo or out of it. I think the quick start guide[2] provides some good >> example of how all this works. >> > > By out of band, I meant it is not related to the jenkins.yml configuration > file in a project repo. A push to a project repository that triggers a job > does not trigger JJB. However, if JJB can reference the project repos, then > a project repo push could trigger JJB and create/delete jenkins jobs. Is > this, in fact, what you have - jenkins.yml to configure the job DSL of the > project job itself and another JJB yaml file to create/delete jobs? > > Another thing that plagues my use of JJB is the fact that Security > credentials, like those uses in the git scm configuration, must be > hardcoded the Credential ID string. This string is unique to each Jenkins > master instance though which means jobs with these strings must be uniquely > defined per instance. Do you use Credentials in your JJB definition files? > If so, how do you manage the hardcoded strings? > -- 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/91dda797-5a9c-47bc-b445-263f30f153e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
