Wednesday, 2020-09-16

*** zxiiro has quit IRC05:10
*** zxiiro has joined #openstack-jjb12:00
*** nweinber has joined #openstack-jjb12:48
*** MuggenHor has joined #openstack-jjb14:39
MuggenHorHi14:52
MuggenHorI'm trying to use the skip-notifications-trait Jenkins plugin by adding a raw XML snippet14:52
MuggenHorBut it seems that raw XML snippets at the branch source level get ignored14:52
MuggenHorSo I went ahead and just added direct support instead. But how do I go about creating a PR?14:53
MuggenHorI read some stuff about a contributor agreement, etc.14:53
zxiiroMuggenHor: I forget the process exactly but you need to create an Ubuntu One account which is used to authenticate against review.opendev.org once you have the account and logged into Gerrit, I believe it will ask you to agree to a contributor agreement. Once you do that you will be able to push a patch to the jjb/jenkins-job-builder project in Gerrit.15:42
openstackgerritGiel van Schijndel proposed jjb/jenkins-job-builder master: feat: support the skip-notifications-trait plugin for git repos  https://review.opendev.org/75227016:03
MuggenHorIt seems I've succeeded at creating a change request :-)16:03
MuggenHorThanks for your pointer zxiiro16:04
zxiiroMuggenHor: np, I've just reviewed it. The typical workflow here is we wait for 2 people to review before merging but if no one get's to it before I produce the next release I will just merge it before releasing.16:05
openstackgerritMerged jjb/jenkins-job-builder master: Updated ext-email support  https://review.opendev.org/74907116:22
zxiiroMuggenHor: looks like your patch failed the linter. If you run `pre-commit run --all-files` locally it should automatically resolve the lint issue and you can `git commit --amend` to update your patch with whatever pre-commit fixed and resubmit.16:51
zxiiroMuggenHor: some instructions on how to get pre-commit installed if you need it https://pre-commit.com/#install16:53
zxiiroor I can update your patch too if you don't want to mess with pre-commit. Let me know.16:54
MuggenHorYes, I just noticed it. Seems I missed it in tox's output16:55
MuggenHorI switched to my laptop (with a more recent Python installation) and just fixed it16:55
openstackgerritGiel van Schijndel proposed jjb/jenkins-job-builder master: feat: support the skip-notifications-trait plugin for git repos  https://review.opendev.org/75227016:56
openstackgerritGiel van Schijndel proposed jjb/jenkins-job-builder master: feat: add support for specifying the git user's identity  https://review.opendev.org/75227716:58
MuggenHorThose now fully pass tox with 'tox' and 'tox -e py38' (I don't have any of the Python versions from tox.ini's envlist)17:01
zxiiroMuggenHor: great, thanks. I'll review now.17:27
MuggenHorthanks17:42
MuggenHorzxiiro: on what kind of schedule do you creat new releases?17:42
zxiiroMuggenHor: no schedule. I do it whenever I feel it's been awhile since the last one (we're probably due for one soon actually) or someone pokes me because they really need a release.17:51
zxiiroJJB these days doesn't have the same level of activity it used to.17:51
MuggenHorGuess people don't like Jenkins as much as they used to?19:13
MuggenHorOr switching to different ways for automatically configuring it?19:13
MuggenHorAt work there's a bunch of people using a combination of Ansible plus custom written Groovy for configuration19:14
Odd_BlokeI think Jenkinsfile support and pipelines made some of the simpler/smaller JJB use cases easier (or possible, at least) to do in Jenkins itself.19:21
Odd_BlokeAnd OpenStack stopped using Jenkins as the backend to their CI, IIRC?19:23
Odd_BlokePlus hosted CI too, I guess.19:23
MuggenHorI guess the hosted CI might have the biggest impact19:26
MuggenHorBut it's kind of the new vendor lock in19:27
MuggenHorSo I don't really like it myself19:27
Odd_BlokeYeah, I'm wary of using it for anything more than just CI; if it's just running `tox -e $TOXENV` in a container for me, then the lock-in isn't too drastic whereas if it's (e.g.) deploying my webapp for me then it's substantially harder to migrate away.19:35
Odd_Bloke(Of course, it's very easy for me to hold that position because I don't have any such webapps. ;)19:35
MuggenHorSure, but it's usually the nice GUI integrations for custom checkers that require a lot of effort19:48
MuggenHorE.g. github's "actions" and "apps"19:48
Odd_BlokeOh sure, for custom checkers, but in terms of vendor lock-in, there will always be multiple CI platforms that have already done that for you.20:04
Odd_BlokeSo use one until they inevitably destroy themselves because they're VC-backed, then move onto the next one. :p20:05
Odd_BlokeBut yeah, I agree that the integration required makes it harder to bring your own CI solution, absolutely.20:05
MuggenHorHmm, except that github is MS-backed so isn't likely to destroy themselves anytime soon20:07
MuggenHorAnd we have the misfortunate at my work of having a former MS employee as the lead manager for CI & devops20:08
MuggenHorIt's fun though, having conference calls with MS telling them that they miss this or that feature. Having them reply with "but Jenkins doesn't have that either", then replying to that with "it does with this plugin and 10 lines of groovy"... :-P20:10
Odd_BlokeBut you don't have to use GH actions, you can use Travis/Circle/etc.20:11
Odd_Bloke(Though them forcing all of those into a single pane of glass view within GitHub _is_ clearly the extend phase of this round of EEE.)20:11
MuggenHorTechnically that's true, and for private and open source stuff I do that instead of GH actions20:12
MuggenHorHaving a MS-happy VP though policy is "MS + GitHub is the solution -> now find the problem it solves"20:13
MuggenHoranyway, I'm off to bed20:19
*** nweinber has quit IRC20:32
*** zxiiro has quit IRC23:39

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!