| *** openstackgerrit has joined #openstack-jjb | 10:40 | |
| openstackgerrit | Sorin Sbarnea proposed openstack-infra/jenkins-job-builder master: Change file inclusion level from info to debug https://review.openstack.org/530339 | 10:40 |
|---|---|---|
| ssbarnea | any jjb expert around here? I try to find a way to disable the scheduler on the staging instance. | 11:41 |
| ssbarnea | i want to configure jobs the same on production and staging masters but avoid running job on scheduler on staging. | 11:41 |
| ssbarnea | i only want to run them on manual triggers. | 11:41 |
| ssbarnea | for gerrit it was simple to disable gerrit trigger on staging, but there is no "scheduler" that I can disable. | 11:42 |
| ssbarnea | who can make a new release of jjb? the beta2 was released back in march and there are lots of changes since then, how about getting a b3 release on pypi? | 12:42 |
| ssbarnea | waynr: any idea about ^^ ? | 12:43 |
| waynr | hey ssbarnea the way i used to handle that was to just disable "staging" jobs by default | 13:01 |
| ssbarnea | waynr: yep, i am now trying to change includes folders between staging and production in order to allow me to produce all jobs disables or all jobs without "disabled: true" in them. | 13:02 |
| waynr | so for example setting the `disabled` flag on job templates using a variable and only set it to "false" when i'm ready for the job to go live | 13:02 |
| ssbarnea | i hope it will work, is tricky especially because I cannot do "disabled: false" on production, I need it undefined in order to allow users to disabled jobs there. | 13:03 |
| ssbarnea | i hope it will work in the end. | 13:03 |
| waynr | also we are waiting on a critical bug fix for the jjb 2 release | 13:03 |
| waynr | i've actually got a five day weekend so i should be able to take a closer look at that bug finally today or tomorrow | 13:03 |
| ssbarnea | waynr: any hints on which bug we are waiting for? i miss an important feature which is not releases yet "-s section" option. | 13:04 |
| ssbarnea | the code is in trunk but I cannot use git version of jjb on production, i was lucky enough to be able upgrade to beta2 :) | 13:05 |
| ssbarnea | waynr: CC me on the bug, so I can help with it. | 13:05 |
| ssbarnea | waynr: just found one critical bug with trunk (b2 is ok): jenkins_jobs.errors.JenkinsJobsException: Unknown entry point or macro 'foo' for component type: 'scm'. | 14:23 |
| ssbarnea | waynr: not sure if this is related to the bug you mentioned, but clearly is a blocker regression, not clear to me exactly from where. i will try to replicate it with a simple test, now it happened with the entire set of jobs (>1000) | 14:25 |
| zxiiro | no way to disable the scheduler. we also have a sandbox system and we just tell developers to disable or delete their jobs when they are done using them. Our sandbox also auto deletes everything on the weekend in case someone forgets. | 15:18 |
| openstackgerrit | Merged openstack-infra/jenkins-job-builder master: Add messages and categories ignores to warnings publisher https://review.openstack.org/528092 | 15:34 |
| ssbarnea | zxiiro: in my case I cannot afford the weekly cleanup (which I already have). This is because we have ~1200 jobs all generated from a single jjb based repo. People create jobs there in subsets (1-50 on average). So the only way to avoid that is to find a way to compile/update jobs diffrently for staging and production. | 15:39 |
| ssbarnea | zxiiro: i am surprised that nobody found a decent way to do it yet, having a staging instance is so uncommon? | 15:40 |
| zxiiro | ssbarnea: in our case it's a sandbox system we only push jobs people are actively testing up to it rather than all jobs in the repo as we only have a single repo containing all of our jjb code. | 15:41 |
| zxiiro | imo maintaining 2 jjb code repos is a lot more work and requires folks to copy code back and forth | 15:41 |
| ssbarnea | zxiiro: i agree, I don't even want to think about two code repos. | 15:42 |
| zxiiro | we even have a production job that pushes jobs to the sandbox using a Gerrit keyword. | 15:42 |
| zxiiro | if you leave a comment like "jjb-deploy: some-job-1" it pushes the specific job in the Gerrit repo over to our sandbox so our developers don't even have to have jjb installed | 15:43 |
| ssbarnea | zxiiro: cool feature, thanks for mentioning it, could be useful to implement. | 15:43 |
| zxiiro | ssbarnea: This might interest you too. We maintain a jjb template repo containing the most common templates our major projects use here https://gerrit.linuxfoundation.org/infra/#/admin/projects/releng/global-jjb which we load as submodules in all of our downstream projects. | 15:44 |
| ssbarnea | zxiiro: here is what I attempt to to get now: use two templates one with "disabled: true" and alter the include dir for production and staging. | 15:44 |
| zxiiro | it contains all of our ci maintenance jobs as well including that jjb-deploy job | 15:44 |
| ssbarnea | zxiiro: I have defaults/ and I add defaults.(staging|production)/ ones. in theory it should work. | 15:45 |
| zxiiro | and this is the jjb-deploy job definition we use https://gerrit.linuxfoundation.org/infra/gitweb?p=releng/global-jjb.git;a=blob;f=jjb/lf-ci-jobs.yaml;h=c931f771ec401ffeac945bf40d00c34c2e942d00;hb=HEAD#l250 | 15:46 |
| zxiiro | ah interesting idea. We only have a single defaults for all of our systems. | 15:46 |
| ssbarnea | zxiiro: this is what we have now too, but I think that's the way to inject the alternative. I hope it will work, i will find out soon. | 15:47 |
| *** waynr has quit IRC | 21:39 | |
| *** waynr has joined #openstack-jjb | 21:46 | |
| openstackgerrit | Thanh Ha proposed openstack-infra/jenkins-job-builder master: Add support for PostBuildScript 2.x https://review.openstack.org/530413 | 23:47 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!