Answers to your questions.. > When a repo needs testing, does it always go through the job generator > before going through the generated jobs every single time? >
You can set it up to update jobs only when there are changes to the JJB definition files. For example we use puppet to monitor changes to the JJB definition files then have puppet run JJB to regenerate the jobs. JJB also has a local cache of existing jobs so the updates are idempotent. > Does the job generator clean up any jobs that are no longer used when the > yaml file changes? > JJB includes a '--delete-old' option to remove old jobs. http://docs.openstack.org/infra/jenkins-job-builder/execution.html#deleting-jobs > Are the jobs generated unique per repository or shared? > Jobs are typically independent of a repo. So for example, from one definition file, you can create multiple jobs that clones from multiple repositories and do similar things. JJB was pretty much designed to support this use case. > Can you create nice views, folders, pipeline views as well? > View support should land on the next release: https://review.openstack.org/#/c/206178/ Folders support is in development: https://review.openstack.org/#/c/180185/ In terms of pipelines, i assume you mean something provided by the pipeline plugin and that seems like it's supported: http://docs.openstack.org/infra/jenkins-job-builder/publishers.html?highlight=pipeline#publishers.pipeline JJB also supports many other Jenkins plugins. -- 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/fe813205-4dbd-44f7-b0cd-22ab1d4e3f2f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
