 Okay it's been recorded. Cool all right so welcome to the office hours for the 11th of September 2019 on the call we have myself Tim Jacobs, Oleg, John and Joseph. Today we'll start off with last meeting I think we've had 16 days ago so we've had one release which is not very exciting the logs we're adding an extra space they're not needed but when people were testing against configuration as coded they were having to add that space in and we wanted to fix that before it got too wide so we didn't have to update too many places that's because we're working on adding configuration as code to the Jenkins bomb and we had some compatibility problems with the plug-in plug-in compatibility tester was highlighting issues with tests not passing on new versions of configuration as card here we go so I think all of the yeah so here I think all the poor requests have been merged we're just waiting on releases just waiting on release of SSH... no which one? I think it's SSH credentials plug-in is that right Joseph? I can't remember actually. I know I think SSH credentials was done by Matt. Maybe I think it's SSH slaves then. Yeah Kurtz who has to do... yeah yeah okay so once that's done we should be unblocked on adding it to the bomb it should be quite nice it means that people updating the bomb will be will keep up to date and we'll get some good plug-in compatibility testing through the bomb as well and plug-in site updates so the work to pull documentation in from GitHub instead of the wiki is being deployed there are a couple issues with configuration as code but that's unrelated to I think the emerge that's will be in fix now so the documentation's looking quite quite nice yeah so basically we migrated around 30 plug-ins by now and the total number of plug-ins using GitHub is up to 50 so yeah it's a nice progress in the general system if you're making any plug-ins you can see the emigrating because yeah you can get to re-talk wiki almost nice yeah I don't use it at all how do you know that how many plugins use GitHub for the documentation I can show so we need to share the screen no okay do you see my screen yeah so yeah it's a part of Jenkins Update site project so we can update the code base which basically generates Jenkins Update site and it's also being used by third parties so yeah you can basically use it for internal hosting for example using city for internal stuff there are the projects like joseph but our plug-ins site basically uses Jenkins update center and as a source of information and in addition to common metadata there are also few files being generated and one file is plug-in documentation URLs JSON file which is specifically for the update site and here well yeah there is no pre-file option so there is that but if you want to know how many plugins use GitHub you can just search so you can see that now there are 50 here it lists only released plugins so we have many plugins which were migrated to GitHub but haven't been released yet so yeah these changes are pending but yeah here you can discover 50 plugins the most of them will work so basically if you and is just if you just put your repository URL it will work if you put something else so there are some examples where custom links are being used so for example here pragma references could have a cool I have no idea what this or there is for example chef plug-in which uses Mediashek chef plug-in so it will also ignore because it uses another GitHub organization it's not supported right now but yeah the most of plugins here which are listed actually gets deployed and visualized by the plug-in site so that's how you discover that yeah if you look for configuration as code so yeah you can see that we have some plugins so one is configuration as code plug-in it references a bit help configuration as code Groovy configuration as code secret SSM and configuration as code support basically reference nothing so if you put this plug-in pages you will like you just see VK we can try nothing no nothing well it depends on the weather plugin site is able to find VK well definitely cannot so probably it's so one of the improvement of our clinic is for us because well I wouldn't say that this documentation is extensive but at least it's some documentation yeah it's better than what's they know yeah so yeah it's something which anybody could contribute to the jcasc system just by defining links so these pages start working okay no any other questions about the plug-in site okay yeah configuration as code support is maybe separate story because yeah I guess it depends on Joseph's fix for deprecating plugins because once we have an engine for deprecating plugins I can also reflect it on the plug-in site currently if you go to the site you get basically there is nothing well there is a duplicate label here but yeah that's it yeah we could improve it a bit later publish the documentation that seems to not use this that's one option another option is to just check this label and put really big warning here yeah or have the deprecation engine support that yeah the plug-in site knows that it should display a warning that does for security well it's pretty easy so if it's a predicated label so even without any additional logic I can just play warning here I will actually create a full update for that because it seems to be a good improvement for the plug-in site definitely yes yeah you need to fix update center but the plug-in site would be awesome nice anyway it's going down so yeah it's 300 installations less than it wasn't made so yeah we are doing good progress there hopefully with the deprecation engine I would like to support like automatically go uninstall when those version matrix is correct like I hope we can have some version matrix but then just auto install if detects all the right versions are like installed and gets rid of like support plug-in for instance makes sense okay so they'll probably just stop sharing the screen so that we return to common agenda cool and we have one pending change which is an enhancement for allowing check for null to override parameters and on null by default suppose it was done for the sonar cube plug-in which has a compatibility issue right now and to allow the to allow that plug-in to be fixed in a easier way it's pending release at the moment may may release it today but just catch up with that later on update it's recent compatibility fixes so mailer plug-in just had a new version out which fixed all the issues with it believe security whitelist filter is it that's good security or something else something very wrong with your mic if you're not aware something very wrong with your mic yep no that's part they heard I apologize for the fact that something is wrong okay use different headphones next time yes script security looks very close to be merged been pending for a very long time yeah right am I missing any other plugins yeah I'm subscribed to the dashboard but they haven't looked for the meeting yeah I've got a poor grace for the build monitor plug-in but seems abandoned it's also not in the Jenkins Jenkins CI org as well which makes it more difficult yeah I think that's it won't wear of anyway ongoing development so we've already discussed to bomb we just need their release on SSH slaves which you said he would do this week get her documentation we've already discussed Jason schema so Slaydon has got a progress for that which is working in the current approach it works to release validate types that and it's the schema that's not broken which is a lot better what we currently have doesn't oh yeah this is the right poor quest so it's pending review I've I've reviewed it and I'm happy enough with it to if we can get it merged soon there's more work to be done but we just need to decide whether we're going to link to the schema in this version or whether we add that later currently it's not linked to anywhere you have to know that URL progress is not that large but it would be good so that we can merge it soon and iterate on it yeah we'd rather merge it as soon as possible because basically there is a pair with the quest which marks Jason schema as a better feature yeah it means that it gives us enough freedom basically to place it as we wish but in the current state it was unusable anyway so I'm perfectly finding this half-made feature if this half works better than the current state yeah it's only way it's better than the currently broken one and yeah the only comment is do we want to change the link to point to this one now or do we want to just leave it unlinked in this poor quest so if you feel the current schema is better than well that new scheme is better than the current schema yeah just to replace it yeah I think so I think so too yeah just replace it okay okay well we'll catch up with Slade enough for this and he can watch the recording as well now hopefully we can get this merged this week okay plus one so we've got the sister repo quest she's um hasn't really had any changes since I think Daniel Bex the only one who's reviewed it slightly not sure what we can do to get that moving along yeah I can take a look to get it over the line so basically yeah we will heads down with the new LCS cutoff because yeah we've got well two or three regulations to process but yeah I think that this blue request also can move ahead so it definitely improves the situation you need to look at the compatibility concerns but yeah the rest is more or less fine yeah I also linked to the red only system configuration plug-in which was created by Red Heart a while ago I didn't have a chance to look at it yeah I have looked at it yeah it parses the jelly and rewrites the jelly before passing it to the user and I know bad teeth just said that when they were doing some compatibility work it affected that plug-in and when he tried to use that plug-in he couldn't get it working in certain situations so I'm not sure how complete it is I'm sure how many installs it has read only Jenkins not that one you know the name of the plug-in is yeah I'm looking for it right now because sales with the link yes this one I had seen it before I looked at it before I started on the poor Chris configuration plug-in it's got a thousand installs and last release thank you yeah I I haven't tested it myself but I suspect it doesn't work what doesn't work completely you're right to use a sanctioned core so yeah why I brought it up just understand whether it makes sense to use it as a base for example for the permission plug-in I mean that's the additional plug-in we use to apply reflection magic and offer APIs for all the core dependencies so yeah if we if this plug-in is not suitable we can just move on and you're once the story is done hopefully this plugin can be considered as deprecated yeah yeah yeah definitely would be deprecated the only API in this plug-in it just tries to look up the permission so just yeah just links to a system permission it tries to look it up and if it doesn't exist it falls back to a minister just exactly what we need to offer a PA consumers so this yeah such microplugging is perfectly fine yeah yeah it's very simple yeah part of something could be nice but yeah whatever yeah well I'm here okay cool yeah I'll try to take a look at the Jenkins pull request this week cool there was a comment here from I think this was just copied up from last time about a devless thread I'm not sure exactly what was going to be on there nothing really happened so basically the intention of this discussion was discuss features we would like to have in the Jenkins core by the next LCS baseline and send this list to the developer community so maybe we could facilitate some contributions there yeah this is the list we discussed at the last meeting basically if somebody wants to put something to this list then yeah just to do that cool they all look very useful and we're skipping the community bridge updates cuz Slayton wasn't able to make it today cool is anyone going anything else nothing from me your one comment about community bridge please vote for the meeting times because yeah we still don't have regular meeting slot for jcasc developer tools and for me it's really hard to find time every week yeah if we can I don't think I have a thing to vote on at the moment I voted initially I don't know if it's I don't know if there's been a new one sent out he's he sent a meeting and by tomorrow that I can't make love to kind it so let's see what we can do the topics to discuss today anything from you John you guys hear me is there audio yep okay cool news so just first time to speak with him okay so welcome back thank you so maybe one additional topic to discuss while we are there so on October 1st we will have October 1st yeah so there is if you don't find I'll share the screen for a second just show okay not this button okay do you see my screen yes so from October 30s yeah 31 yeah whatever you will have for breakfast so it will be an online hackathon where everybody is able to contribute we also try to organize some on-site events so for example they will be one event in Switzerland one event in Munich one event in China and hopefully one event in St. Petersburg and you that I meet up organizers we also invite you to do so what is specific to Jenkins configuration as code project that yeah last year we had configuration as code plugin here on the list at that point here we had only few new befriended tickets but I think that this year we could have some more example this documentation migrations whatever smaller features or whatever integration test or if somebody you would be interested to just create a bunch of new befriended tickets it would be nice so that yeah we could facilitate some contributions to the plugin so yeah that's why I wanted to link it up so if you have any ideas what could be done let's do that I struggle that fine I find that JKS isn't the most newbie friendly plug-in it's very reflection heavy and Jenkins internals heavy right but for example integration test or something like that yeah yeah hard to say some bits could be done so yeah if you have any ideas or maybe just creating demos I'm sure this folder seems to be pretty useful according to traffic stats so maybe we could just suggest creating new demos for plugins where you have issues often so yeah there's a nice work in progress pull request that actually tries to consume these demos from the integration plug-in now yes I was about to mention that our case and configured with demo which pulls the integration test config from the demos folder rather than the class path yes the pull request from Victor my team Martinez I guess this one yeah but the new one at the top is okay yeah that one is cool so definitely to take a look at that but the original it starts there's a hard cover first last year when you wish we had in these so maybe at least October first we could get it over the line so yeah it doesn't necessarily have to be newbie friendly so newbie friendly tickets kind of condition but there is a chance that we will have experience contributors as well yeah there's probably a few we can stick October first is it October first labels or newbie friendly or both so last year we adjust the link on this list so we did half issues jira query so let's see what you have in the list now okay but yeah definitely could be more and definitely could be more here so yeah so the filter in jira is jcasc compatibility dev tools compatibility or anything in components so for example when I create tickets to move documentation to get help for these plugins they will appear here and they will be definitely newbie friendly but yeah having more issues would make sense so yeah if you have something like this you don't just create them okay so yeah thanks for your time thank you okay thank you and you see in two weeks