On 01 Sep 2015, at 05:02, milki milk <nitesha...@gmail.com> 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. > So, while you have a handle on job management, do you find yourself with any > performance issues for creating/deleting jobs? Actual job creation/deletion is quite fast. To my surprise, the bottleneck are all the github api calls we are doing. There is certainly room for improvement there. > 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? ;( > 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? Yes, when for example a feature branch is deleted, the corresponding sets of jobs for that branch are deleted as well, including their history. So far, no one was ever interested in that history. Marc -- 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/D7DE5EEC-EB19-4460-B5EE-4572076188D6%40ebay.com. For more options, visit https://groups.google.com/d/optout.
