Re: fetch the api key for the current user?
On Monday, February 1, 2016 at 7:38:49 AM UTC-8, Brian J. Murrell wrote: > > On Sun, 2016-01-31 at 23:45 +0100, Daniel Beck wrote: > > On 30.01.2016, at 19:10, Brian J. Murrell > c...@public.gmane.org > wrote: > > I think any answer to this would likely be a security issue and > > should be reported as such, rather than posted here. > > How do you figure? And what exactly are you proposing to report and to > whom? > The security part comes in when you fetch an arbitrary user's key which you generated as "the user running the job." Fetching the current user's api key doesn't seem to have a REST API equivalent. Right now, I just scrape the user's configure page - /user/USERNAME/configure - and look for the pattern -- name="\_\.apiToken"[^>]+value="(\w+?)". -milki -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d415bfef-d899-4c2f-876c-619b7d1900fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins unable to restart. Requires multiple attempts.
On Wednesday, January 13, 2016 at 4:41:45 AM UTC-8, Ashish Yadav wrote: > > Where in jenkins server are the slave configs defined? I don’t see them > anywhere in the config.xml on MASTER. > I see a slaves section in my config.xml for the master. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/db337eaa-9792-4e91-8938-50dac5acf079%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to take care of a large Jenkins installation and still keep your sanity
Damien in JENKINS-31152 mentioned the Seed Plugin (https://github.com/jenkinsci/seed-plugin/wiki). This sounds a lot like another formalized framework that is similar to Ebay's seed job. It takes a seed.groovy and/or a seed.properties as configuration. It has a concept of a "project seed" and a "branch seed". It uses groovy and Jenkins Job DSL under the hood to generate the rest of the jobs. It looks pretty good at first glance. In particular, I like the generation configuration illustration in an image: https://raw.githubusercontent.com/wiki/jenkinsci/seed-plugin/Overview_Pipeline.png -milki -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/977717f9-c41d-46a8-aaf6-332d2136c057%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: git credentials are missing after copying the jobs
With the SSH Credentials Plugin 1.11, you can now specify your own identifier for credentials - https://wiki.jenkins-ci.org/display/JENKINS/SSH+Credentials+Plugin (click Advanced when you create *new* credentials). If you use the same id across your jenkins instances, then the copied job definitions will still have valid configured credentials. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/308ebc44-b65d-4d17-95d5-ed4c418aa957%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Job DSL Extracting into Groovy Script
This is more appropriate for the job-dsl-plugin mailing list. readFileFromWorkspace is part of DslFactory. You can pass in a DslFactory through the call to addEmailTemplate or maybe import DslFactory and use it directly. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6a560ff3-6c14-4afb-b01a-14dbe5c5a8c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Git plugin unable to acces local repository
Yes, that should be it. Defined credentials and using that credential in the selection box for your scm. Are you sure the credentials work? I see you are also using localhost. The scm polling job doesn't havee a node restriction, but the job that does the checkout is done locally on the node it runs on. In general, you'll want the server to be accessible from all nodes. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/41c7b8f8-ad41-49b3-9fd7-a44d28aacfe8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: New stuff for Jenkins GUI
On Wednesday, October 7, 2015 at 8:04:01 AM UTC-7, Gus Reiber wrote: > > Awesome Maciej, > Yeah, a collapsible job config page is something I think is important > and attainable in a reasonable time window. It was my hope it could have > made the November LTS, but we didn't quite get there. I am excited to apply > your script and have a look. > I don't like collapsible job configs if it means hiding even more information. I already have issues with all the 'Advanced' tabs from all the plugins. We have a lot of non-Jenkins-experts and more seasoned admins that administer Jenkins jobs. And more often than not, jobs are misconfigured because they can't find options or don't realize there are default behaviours that were hidden under all these tabs. I find myself looking at the documentation in Jenkins Job Builder and Jenkins Job DSL to find job/plugin configuration rather than trying to find out by clicking all the buttons and tabs to expand all the hidden options. -milki -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d43d3479-5cb1-4191-a4cd-7f475da36b6e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Git plugin unable to acces local repository
Did you set the credentials to be used the scm section? You need to both define the credentials _and_ use the credentials. On Thursday, October 1, 2015 at 1:38:38 PM UTC-7, Henk van Voorthuijsen wrote: > > I did - there is a credential for user "git" in the global credentials. > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3390c11a-6b82-498c-b845-422b1a121658%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Merging git branches to master using Jenkins
Under Advanced Features in https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin, the docs talk about pre-build branch merging. You can specify the merge type as well - ff, or no-ff. By default, the plugin makes a new tag. As a post-build tag, you can then push the branch and tag back to the repository. You can provide the url as a parameter to the job and then use that variable as the repository url. A warning though, a non-ff merge is done as (git merge --no-ff $GIT_SHA) and you can't customize the tag name. This method might not be flexible enough for your needs. Typically, I do manually merging and tagging as build steps. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6c78aead-506a-435f-9aa6-488f266d6329%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Disabling the ping thread in Jenkins
Have you tried the suggestions here: https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/40008101-50d1-42c8-923e-b845e08853d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to take care of a large Jenkins installation and still keep your sanity
On Monday, August 31, 2015 at 1:25:41 PM UTC-7, Guenther, Marc(AWF) wrote: > > 2. The 'jenkins.yml' files I describe in the blog are purely our own > convention. Neither Jenkins Job Builder nor Job-DSL-Plugin use anything > like that. In particular, they have nothing to do with JJB's yaml files. > They also do not describe complete job definitions, but only choose and > configure existing definitions (what I wrongly called template). > So while waiting for the next blog post, I've tried implementing the same thing myself and I'm a fan of this method! My project repos contain a .jenkins.json file because there didn't seem to be a Yaml parser included with the jenkins groovy. This file specifies the type of job should be run, what kind of pipelines I want to it to trigger, and includes all the variables needed by the respective jobs that are created. I use jenkins-job-builder to define the "seed" job for the project that contains a checkout of both the project repo and a job-dsl repo placed at .jobdsl. This seed job can easily be replaced by another job-dsl job. In this job-dsl repo, I define a bunch of predefined pipelines and job templates which I can import into the groovy dsl script that gets run by the seed job. When the seed job runs, it examines the .jenkins.json, imports the classes from the job-dsl repo, and then generates all the jobs needed for this project inside a Jenkins Cloudbees Folder. Finally, it triggers the "main job" for the project that was generated. This appears to work well at the testing scale. We'll see how it handles everything at a larger scale. I look forward to the next blog post that has more implementation details. -milki -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/783554ed-2e50-417a-be57-3986e80a16ce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to take care of a large Jenkins installation and still keep your sanity
On Thursday, September 3, 2015 at 4:03:50 AM UTC-7, Guenther, Marc(AWF) wrote: > > > On 01 Sep 2015, at 05:02, milki milk > > wrote: > > > I'm not sure what you mean by "when a repo needs testing". So when there > has been a commit in the repo, which changes the 'jenkins.yml' file, and > that commit gets pushed, then that change will be applied to the existing > jobs before they run. So technically, yes, every push goes through the job > generator, but it very quickly figures out when there is no change and will > run the real job(s). > > > > Yup that answers my question. My "testing", I meant the project repo > triggers a Jenkins job. Since the jenkins.yml file configures a job, are > all project initial jobs essentially the same - read the yml, configure the > jobs, run the jobs? > > Yes, exactly. The generator runs in the time span, that we always had for > our Quiet Period anyway, which is 15sec. > I see that Jenkins Job DSL has a queue command. Is this how you trigger jobs or do you have a subsequent build step that triggers a job? Queue doesn't seem to have any explicit support for parameters. When you create a new repo, what do you use to create the initial Job DSL job for the repo? I'm thinking either have a single Job DSL that is responsible for all initial jobs or having JJB manage those initial jobs. > > > Additionally, do you see performance issues when all the jobs? I find > that jenkins slows down with lots of jobs because it likes to parse job > history and artifacts all the time and stuff everything into memory. > > I don't really like to say this, but we do a daily restart of Jenkins > master. Otherwise it wouldn't survive the week. Otoh, this was on the old > legacy instance, and we never re-evaluated this, so maybe situation has > improved with newer Jenkins versions. But given your statement, I guess > not? ;( > We haven't been able to evaluate this effectively because we are so afraid to do restarts which means its hard to do plugin updates or jenkins version updates. We also didn't like to do daily restarts because we pretty much have long and short jobs running all the time all day and all night long. Restarts of the master are disruptive and we can't do safe restarts because of the long running jobs. Thanks for answering all my questions! This is the first time I've seen this much detail about successfully managing Jenkins and it sounds great. -milki -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/969e4351-dafc-4709-969c-8e37f996cd8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to take care of a large Jenkins installation and still keep your sanity
On Friday, August 28, 2015 at 6:55:09 AM UTC-7, Patrick Hund wrote: > > Thanks, here's part II: > http://www.technology-ebay.de/the-teams/mobile-de/blog/taming-the-hydra-part-2.html > So the article only mentions 2 methods - Cloudbees Template Plugin and Jenkins Job DSL. There are at least two other alternatives I know about - Jenkins Job Builder and Workflow. Were these and possibly other alternatives explored as well? -milki -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a691fb64-e09b-41ec-9089-c15115deb92e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to take care of a large Jenkins installation and still keep your sanity
On Monday, August 31, 2015 at 1:25:41 PM UTC-7, Guenther, Marc(AWF) wrote: > > On Monday, August 31, 2015 at 10:50:59 AM UTC-7, milki milk wrote: > > 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? > > Recent version 1.21 of Credentials Plugin allows to specify meaningful IDs > for your credentials, so you can reuse them over several Jenkins masters, > which is very convenient. You could also use EnvInject-Plugin to inject > credentials as build variables, but Credentials Plugin is more secure. > ! This is awesome. meaningful ids is exactly solves my issue. Nice find. -milki -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/241a8ffa-7b1f-4eb0-849d-9f26befba207%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to take care of a large Jenkins installation and still keep your sanity
On Monday, August 31, 2015 at 1:25:41 PM UTC-7, Guenther, Marc(AWF) wrote: > > Hi all, > > I think there has been a little bit of confusion here. > > 1. As described in my blog article, we are using Job-DSL-Plugin, not > Jenkins Job Builder (JJB). Both try to solve similar problems > (automatically generate jobs based on external descriptions) but there are > two very important differences: > - JJB is an external process communicating with Jenkins via REST-API, > whereas Job-DSL-Plugin runs inside of Jenkins itself. > - Job-DSL-Plugin uses Groovy DSL to describe their jobs, whereas JJB uses > plain Yaml files. The huge advantage of having a complete programming > language instead of just some templating engine was the main point of my > last blog. > > 2. The 'jenkins.yml' files I describe in the blog are purely our own > convention. Neither Jenkins Job Builder nor Job-DSL-Plugin use anything > like that. In particular, they have nothing to do with JJB's yaml files. > They also do not describe complete job definitions, but only choose and > configure existing definitions (what I wrongly called template). > > Those confusions being hopefully resolved, I would like to answer your > questions. > Oh. So Khai Do isn't responding as someone who knows how Ebay's workflow works. Yes, this was the disconnect I was feeling because there was no mention of JJB, only a "job generator." Thanks for clearing that up. > On 28 Aug 2015, at 18:18, milki milk > > wrote: > > > Now this is more interesting. Using the .jenkins.yml file from the > repository to inform the job generator what jobs to create is similar to > travis. > > Yes, exactly. Only in this case it is more flexible, as the job definition > you choose through the 'jenkins.yml' file has the full power of > Job-DSL-Plugin available, which means it can do everything you can possibly > do in Jenkins. Travis afaik is not that flexible in what the jobs can do > (on purpose, at least that's what I understood from my last chat with one > of their developers). > > > Of course, the details are in the implementation in the next post. > > Oh, yes, reminds me that I still have to write that ;) > Yes! Very interested. JJB is limited by Jenkins and its plugins and the fact that is is essentially just POSTing XML to configuration pages. > > > I'm curious. > > > > When a repo needs testing, does it always go through the job generator > before going through the generated jobs every single time? > > I'm not sure what you mean by "when a repo needs testing". So when there > has been a commit in the repo, which changes the 'jenkins.yml' file, and > that commit gets pushed, then that change will be applied to the existing > jobs before they run. So technically, yes, every push goes through the job > generator, but it very quickly figures out when there is no change and will > run the real job(s). > Yup that answers my question. My "testing", I meant the project repo triggers a Jenkins job. Since the jenkins.yml file configures a job, are all project initial jobs essentially the same - read the yml, configure the jobs, run the jobs? > > Can you create nice views, folders, pipeline views as well? > > Yes, all of them. We heavily use Views and Folders, as each repository > gets it's own Folder in Jenkins, and inside there are Views for branches > and forks, for example. We also generate Delivery Pipeline Views. > This sounds great for users! So, while you have a handle on job management, do you find yourself with any performance issues for creating/deleting jobs? Additionally, do you see performance issues when all the jobs? I find that jenkins slows down with lots of jobs because it likes to parse job history and artifacts all the time and stuff everything into memory. How do you deal with the job history? When a job is deleted, all history is loss and links go stale. Do you archive history? -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9ad5c99e-815c-4e69-91ff-f21e4830e945%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to take care of a large Jenkins installation and still keep your sanity
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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ad57306c-df4d-4294-836e-a9040d07ec0f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to take care of a large Jenkins installation and still keep your sanity
On Monday, August 31, 2015 at 9:11:54 AM UTC-7, Khai Do wrote: > > 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. > Ah. So this is how I'm understanding this then: * all jobs are generated out-of-band via jenkins-job-builder (presumably via http://docs.openstack.org/infra/jenkins-job-builder/builders.html#builders.dsl) * each individual repo's jenkins.yml file are referenced by the DSL for configured values. Going off of the summary of the article, it states: "developers to easily create and configure the jobs for their repositories, without the usual copy/paste problems, while still allowing" If the jenkins.yml is only for configured values for already generated jobs, then how do developers "create" jobs for their repositories. It seems like they would need to work with the JJB definition files which is out-of-band of the repo. In the case that jobs are shared, then developers can configure their repo for those shared and already created jobs. But, if a developer wants to have a convenient UI view of their project jobs, it would be difficult to isolate the relevant job history from shared jobs (e.g. shared job0 #4564 triggered shared job1 #545212 triggered shared job2 #421). I believe that view support becomes necessary in this case. How do you help developers view their relevant jobs? -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/35b69b2c-35ba-4892-8cad-996999d25932%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to take care of a large Jenkins installation and still keep your sanity
Now this is more interesting. Using the .jenkins.yml file from the repository to inform the job generator what jobs to create is similar to travis. Of course, the details are in the implementation in the next post. I'm curious. When a repo needs testing, does it always go through the job generator before going through the generated jobs every single time? Does the job generator clean up any jobs that are no longer used when the yaml file changes? Are the jobs generated unique per repository or shared? Can you create nice views, folders, pipeline views as well? -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/39f08c0d-e426-43f1-9966-59291abd95a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Admin privilege disappears after restart
On Tuesday, July 28, 2015 at 1:16:27 AM UTC-7, Björn Pedersen wrote: > > > I would try to switch steps 7 before step 3. > > Björn > Agreed. All required perms for the admin user should be set before the save step. You also don't need to restart the server to apply perm changes. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ae7a99a6-9485-4f8c-88c4-ff8668f3f5b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Very slow view render
I've had this problem with every version I've tried in Jenkins. From what I can tell, Jenkins is parsing through every single build directory and parsing the build xml files as part of either cleanup, or sanity checking, or some other automated task. The logs are quite activate but the render only says "Wait while Jenkins is loading..." Only once Jenkins finished this does the start rendering, but this could be 30 minutes or more. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a3419431-839a-43f0-8f39-d784f4564284%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Search within Nested Views or Cloudbees Folders
Our jenkins has hundreds of jobs and views and I'm attempting to fix performance issues on loading Jenkins by categorizing the jobs. I'm found the Nested Views and Cloudbees Folders plugins. However, once I put jobs and views within them, they no longer show up as results in the Jenkins search box. Is this a configuration issue or a limitation of the search feature? Are there any alternatives to Nested Views and Cloudbees Folders that would allow me to categorize views and jobs and still allow for searching? -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
