Monday, 2018-09-10

*** caphrim007_ has joined #openstack-jjb01:46
*** caphrim007 has quit IRC01:50
*** jiapei has joined #openstack-jjb02:12
*** jiapei has quit IRC04:22
openstackgerritAnil Belur proposed openstack-infra/jenkins-job-builder master: Add config options --jobs-only and --views-only  https://review.openstack.org/58458305:32
*** hashar has joined #openstack-jjb06:20
*** aigarius has joined #openstack-jjb08:04
*** electrofelix has joined #openstack-jjb08:54
*** bek has joined #openstack-jjb12:52
*** bek has quit IRC12:52
*** caphrim007_ has quit IRC13:32
*** caphrim007 has joined #openstack-jjb13:32
*** caphrim007_ has joined #openstack-jjb13:33
*** caphrim007 has quit IRC13:37
openstackgerritMerged openstack-infra/jenkins-job-builder master: Use upstream default for allNodesMatchingLabel  https://review.openstack.org/60071514:13
*** bmwiedemann1 has joined #openstack-jjb14:20
bmwiedemann1zxiiro: saying Hi :-)14:21
zxiirohowdy :)14:22
bmwiedemann1btw: we are using jjb with https://github.com/SUSE-Cloud/automation/tree/master/jenkins yaml files to update our internal and external instances to test OpenStack, crowbar and ardana deployment + config-management14:23
zxiirothat's awesome. It's great to hear from folks using JJB.14:24
zxiiroEven better that you have your scripts online :)14:24
bmwiedemann1we also have most sources in the public, but it is not always straightforward to make good use of them14:25
*** bek has joined #openstack-jjb14:26
zxiirobmwiedemann1: not sure if it's useful for you guys but we have a repo we maintain called global-jjb which is a set of reusable job templates https://docs.releng.linuxfoundation.org/projects/global-jjb/en/latest/index.html14:26
zxiirowe deploy this to about 10 projects now and it's saved us a lot of work of having to redefined JJB YAMLs in every project.14:26
bmwiedemann1I guess, we might be able to use some in the CI-jobs category14:28
zxiirowe're trying to build jobs that can manage all of the config in the global jenkins configuration too since JJB doesn't offer a way to manage non-job items.14:28
zxiiroso far we have openstack-cloud-plugin and global variables but hope to expand that to more sections in the future.14:29
zxiiroIt's very hacky as we use bash to generate groovy to update jenkins hah14:29
bmwiedemann1We use jenkins-swarm-client for most worker nodes now, so at least we dont need manual config there anymore14:30
bmwiedemann1and https://github.com/openSUSE/github-pr/ helps to trigger jenkins runs for github PRs and report status updates back14:31
zxiirothat github-pr sounds interesting. Why did you choose to make your own instead of the GitHub PR Trigger plugin?14:32
zxiiroI'm interested because we have issues with the GitHub PR Trigger plugin currently.14:33
bmwiedemann1because the plugin is written in Java, so hard to compile, and updating plugins requires shutting down jenkins for several hours (until all jobs finished running)... and ruby is so much more flexible to work with14:36
bmwiedemann1also every team can run its own github-pr with its own config using the same central jenkins instance14:38
zxiiroyeah it seems interesting. I will have to dig into it more closely later. We're having issues with managing the GitHub PR Trigger plugin especially in terms of management and I dislike the t he GHPR Trigger plugin wants admin access to manage GitHub hooks.14:39
bmwiedemann1our code is ~beta quality, so might have some rough edges atm. Some external users+testing is certainly welcome there.14:41
bmwiedemann1I guess, it would be good to add something like the "ok to test" logic of ghprb14:43
*** jiapei has joined #openstack-jjb15:08
openstackgerritTan Heng Yeow proposed openstack-infra/jenkins-job-builder master: Add support for "Build / Publish Docker Image"  https://review.openstack.org/60129115:33
zxiirobmwiedemann1: Forgot to ask, do you need a patch release of JJB?15:34
zxiirobmwiedemann1: we loosely release every 2 weeks but if you can't wait I can do a patch release with that patch.15:34
*** bek has quit IRC15:46
openstackgerritTan Heng Yeow proposed openstack-infra/jenkins-job-builder master: Add support for "Build / Publish Docker Image"  https://review.openstack.org/60129116:12
openstackgerritAnil Belur proposed openstack-infra/jenkins-job-builder master: Add config options --jobs-only and --views-only  https://review.openstack.org/58458316:30
*** hashar is now known as hasharAway17:17
openstackgerritТарас Постумент proposed openstack-infra/jenkins-job-builder master: Extend multibranch pipeline project scmAdd suport of available extensions from default git scmStory #2003620Task #25743Change-Id: I79454844e63b31aeb4ddcceb5859e2c6bc656caf  https://review.openstack.org/60132317:24
openstackgerritТарас Постумент proposed openstack-infra/jenkins-job-builder master: Extend multibranch pipeline project scm  https://review.openstack.org/60132317:26
openstackgerritТарас Постумент proposed openstack-infra/jenkins-job-builder master: Extend multibranch pipeline project scm  https://review.openstack.org/60132317:33
openstackgerritТарас Постумент proposed openstack-infra/jenkins-job-builder master: Extend multibranch pipeline project scm  https://review.openstack.org/60132318:00
*** electrofelix has quit IRC18:11
*** bek has joined #openstack-jjb18:11
bekhi.  I have a quick question with jjb - is there an easy way to figure out what exactly is triggering a duplicate entry point ?  I'm working on some configs that work fine with 1.6.2, but when 2.X is installed, they break..18:37
bekerror in question:  jenkins_jobs.errors.JenkinsJobsException: Duplicate entry point found for component type: 'parameter', 'parameter',name: 'string'18:37
*** hasharAway is now known as hashar18:44
zxiirobek: you could enable debug logs and see if it gives you any more info.18:48
zxiirobek: you could also try this: find . -name "*.yaml" | xargs grep name | uniq -d18:50
zxiirobek: it should show you all the lines in files that are duplicated18:50
zxiirobek: sorry I forgot to sort there18:51
zxiirobek: find . -name "*.yaml" | xargs grep name | sort | uniq -d18:51
bekzxiiro: ok.. I have been running with debug, but not haven't seen anything that is standing out.. I'm still digging though..18:52
zxiirobek: do you store your jjb in git? it might be easier to spot if you look at commit diffs18:53
bekSo I run into the problem where I've inherited this system and it all currently runs fine under 1.6.2..   I'm attempting to upgrade and failing.18:53
zxiirooh yeah jumping from 1.6.2 to 2.x is a pain,18:54
zxiiro2.x also finds invalid configuration that 1.6.2 allowed18:55
bekI'm learning that. :)18:55
zxiiroso you'll spend most of your time tracking down broken YAML configs, it was annoying but once we got through it, it was worth it because we found some jobs that weren't working in the first place that JJB 2.x caught18:55
bekLooks like we have some parameters: string (two of em) in jobs and that is causing the failure.  Which is odd, I removed one and it still errored, but the output is correct with 1.6.2..19:14
bekthey are part of a job-template.19:16
bekShouldn't that be valid behavior otherwise?  Since multiple parameters are allowed?  jjb is failing as duplicate entry point, but they're not being used anywhere else.  I isolated it to one job.19:23
bek(which I'm sure we have many jobs doing this, but want to get an idea if it's a bug or just me)19:25
beksmall snippit of config and where there's problems, removed quotes, changed quotes, etc, made no difference.  removing "parameters" outright did..  all variable expansion files and such are in the same dir..19:27
bekhttps://gist.github.com/bkruger99/dcbf1fa4c56059390940e7839c4c293619:27
*** hashar has quit IRC20:23
*** caphrim007_ has quit IRC22:01
*** bek has quit IRC22:34
*** bek has joined #openstack-jjb22:35
*** bek has quit IRC22:57

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!