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 <[email protected] <javascript:>> > 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 [email protected]. 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.
