 Hello everyone, to the bi-monthly platform SIG meeting end of January this year 2019. So we are going to discuss the usual agenda and new things in the platform special interest group area. So let's dive into it right away. So we wanted to get a look at the last meeting items, but I think Mark is not going to attend. So we'll probably put that for next time. But as Alex is attending, I guess we can move to that actual item. Alex, can you tell us where we are in terms of ownership for the chocolatey package for Jenkins? Alex, you seem to have an issue with your mic. You seem very, very remote, like your 10 meters from your mic. Maybe Oleg, you can cover that part when we get back to Alex afterwards. Can you hear me now? Yeah, let's dive to it for you. So the update there is that I contacted the original package owner on chocolatey and Mark kind of vouched for me, quote unquote. He added me as a maintainer on the package, so I have access to release new versions. Currently we're just keeping up with what they currently have. They have some automated process that goes and when I don't know if it's like daily they check for a new release of Jenkins or what, I don't know how they do that, but they automatically create an updated package. So we're just still using that for now until we have something in our pipeline to do that process when a new release is made on Trusted or whatever. Thank you. So we can say basically that now we can deliver things there and we need to now let's write something I should have written while you were speaking. I was just copying things instead of writing activity. So Alex now is co-owner, I would say. Yeah, and I can add any I believe I can I should be able to add anybody else. So anybody else who we need to have access right now, I can add them. I mean it's always good to have more than one person from the projects have access to something. So technically it would be nice to have the entire maybe not the entire platform seek, but maybe me but East because we also maintain the core so we can somehow coordinate the releases if needed and maybe also Mark because Mark did some testing and he knows this packaging already. Okay, I think you might need to sign up for an account on Chocolady but I'll double check that. I should already have an account there. Okay, if you can send me your username on Chocolady if you have one I can add you and then if you don't have an account you can sign up for one and then just send that to me and I can add you. Yeah, so you were saying something about that. I'm not sure what you summarize here Alex. So basically you now need to contact Olivia maybe or something to to discuss how to indeed push from Trusted.ci.trustkey.io. Yeah, so that'll be part you know when the the Chocolady package and the MSI changes are incorporated and we that's part of whatever build flow and and stuff like that that will need to be we'll need to figure out how to to push that you know on the infrastructure. It writes. So just just as a point of clarification the Chocolady package actually uses the MSI. Chocolady has that capability of using an MSI installer so the changes that are going into the MSI will also impact how Chocolady is done so that the two are kind of tied together a little bit because you have to have like a SHA hash for the MSI file that you're going to download during the installation so that's why I'm kind of tying them together. So that's just a verification they do on Chocolady is anything that's downloaded has to have a SHA inside the Chocolady package so. Okay thank you so I guess we are gonna just cross that I thought there was something can't find it anymore where is that crap do cross something can't find it anymore that thing keep surprising me um or like maybe you want to thanks Alex you want to put an update about that like yeah it's a work in progress technically I have draft for this job but I need to make some confirmations before I proceed. So yeah my hope that I will be able to do it next week no strong commitment though. Okay thank you oh right so that was the one where are we with that it's still open whoops um is this the date right so Alex about that what is the kind of is there an expectation like something like okay we should be blocking that until we have something or it is something that can already be published sorry I didn't I didn't review it I didn't I wasn't aware of that one it hasn't been merged yet so it's not published um I just put that date as kind of a I didn't I didn't know if the blog if there was like a restriction or not a restriction but like a schedule for when posts were published or anything like that um so I just it's kind of you know out there a little bit just in case but it can be published whenever um and yeah so it should be um I think I think if the date is future then yeah is going to be published at that date so I think we need probably to change it but I'm not sure that the naming here does get used I thought there was something here but probably it is the case actually yeah so I can fix the naming concentrate before publishing generally we try to not publish more than one blog post per day yeah and we try to publish in the time zone of the author unless there is a strong preference so that's it so there is no blockers from publishing and yeah if you want we can try to get it published today sure do you want me to update the dates then well I can do that okay cool I just realized I have permissions to do that but I think I'm not wondering why yeah I think probably it was because of the platform sync meeting I think it was a request from Oleg to um to Liam maybe yeah I'm mixing things because yeah I'm just discovering that I'm remembering more okay right so by the way if I have permission I should be able to then request myself it would be easier for if I want to have a look just don't wait for me just to note about that I was saying that for next one I think slide you I'm going to use like Alex or slide whenever you prefer but I think basically you can define variables so that you can for instance do those things only once instead of depriting these yeah you can do it in a ski dog but in such case it doesn't render properly in github right that's an issue but well yeah even now it won't be displayed properly in this case but macros macros expressions are generally don't work in github I'm saying I was thinking about that because as we are discussing the fact that I mean at your date you know you are going to have that to do that many times okay yeah anyway so great thanks a lot Alex so and also java 11 support status report I guess I can probably go or like you you can summarize also I think yeah I think you are more involved with the project now so so overall yeah I can I can do it no problem um so overall the situation is looking pretty good the last uh things uh so we are really now looking at GA soonish like maybe the next month or something uh I mean meaning the beginning of next month or something uh beginning of February yeah right something like this or me anyway so um because so the last outstanding thing that that's still in progress even in the core is probably jack's b uh put as a dash plugin specifically for java 11 I fixed an issue this morning that surfaced that that actually showed something about an issue on jack's b you actually all the version of jack's b use the evil system path dependencies which actually was failing under JDK's so um so well it wasn't really failing during build and it was quite quite working well for runtime but it was indeed failing the build because they may even would try to resolve things during the build by using system path to resolve the tools.jar and tools.jar doesn't exist anymore on the same path at least but I guess that doesn't exist anymore at all starting from at least in java 11 so that's why it was failing for a few prs like that one on that plugin in that race that was where the the issue got revealed so I ended up patching the plugin the jack's b api plugin that got introduced to actually use a version of jack's b that that doesn't have this issue anymore and that's rely on uh system path and locally install dependencies anymore and the good thing about that is that anyway uh if you look at the changelog like uh was uh rightly pointed out by ramon this is a good thing to bump to 30230 because it's the one that's deemed to support supporting java 9 so that's exactly what we should have done that I should have done from the ground yeah there is still one uh potential issue with it because um there are already versions 3.x for jack's b but these versions are available only for java 9 and above they don't work with java 8 yeah because you mean the bytecode is java 9 plus yeah all right now I didn't intend to bump that by the way I documented I explained here yeah that I I chose actually the closest one the lowest one close to that that that didn't have that that issue uh that would be the lowest one at the same time so that's why I ended up choosing even not even the 231 I think and the 2301 also if I remember correctly and there are many others 234 I think in the meantime in the in the middle but yeah that's the reason why I chose the the lowest one that yeah wasn't using system path basically yeah so the risk for us that currently in our docker packages we use a newer version and effectively we will be there on training before the java is which is probably okay here I also tested the the new jack's b api plugin and everything looks perfect so you mean you tested that thing uh that thing or the one that's already released I've already released one so I didn't hit this that's that's what I said because actually that's a build time issue because you know it's just that may even depend on system path what your build but what it's done well everything is a jar in the class pass every you know there's no resolution this way anywhere so that's why it doesn't surface when basically you're you release using java 8 for instance and then you just are at run time so that that's really a build time issue that we're surfacing in the middle of that plugin that's really the issue so I don't expect it to be a really an issue in the in the end but yeah overall it's going to be simpler and cleaner from a build time perspective and again overall it's a good thing so well it's actually some officially said that that's the one for java 9 plus so so it's adopt I don't expect it to be not my work compatible it's just that I think it's indeed able to work with that so that's the one was kind of the last outstanding one I would say not last we will see a few others but the current status is that we think that we probably will have some few issues few issues maybe in the future but we don't think we will basically hit them or discover them before we go GA because we know that you know like in many communities in general people just ignore not not everyone fortunately but you know there's there's actually a lot very few people that would test preview versions or alpha versions we will really get actual feedback from from the field when we deliver the GA and we're ready to fix potential mishaps but yeah we don't expect a lot we are pretty confident but well she tapens yeah in addition to the jugs b patch what else left is the river tank some experimental focused patches yeah so we have for example enable future java plug and an exact stress executable what we have experimental update center which is enabled by default so we will need to reverse this purchase and after that I think that the weekly baseline will be traded to g yep exactly I think that that probably by the way we could revert the patch about java 11 automatic switch already because it was as I remember it specifically for for specifically collier essentially for workflow support 3.0 and yeah this patch we can revert yeah I'm a bit more concerned about enable future java yeah right I'm really that that one could be postponed slightly there but I think that it would be probably nice to actually revert the experimental specific update center because now we know that workflow support the good thing is that for people not really knowing about that basically the for java for workflow support was something that that we hit only on java 11 the delivery that happened in the meantime make things work even for java 8 so now we are kind of everything is already in the field so probably you can even delete the special temporary update center that was deployed for that yeah I would keep it but just as a plan b yeah if something goes really wrong in a plugin and we can probably keep it a bit more for just to not do that again if we realize we missed something obviously but yeah so uh test tool so I'm not sure what we were meeting here I guess so there's another thing about java 11 status report that uh this morning I think or yesterday which merged and released and about the main hpi plugin that now should be allowing anyone to develop on the java 11 runtime which is I think when one has to fix something specifically on java 11 and wants to develop you think the hpi plugin so that thing now should work is expected to work and I guess that's probably a good overview I could go on for longer but I guess it's enough for the sake of this meeting uh don't think we really have something to cover here uh like we want to cover that those last three items um yeah I can cover them so it will be a quick update anyway uh so for job 217 one major update is that we go to bdfl delegator side so technically we can proceed with this job um and we can um so bdfl delegate is actually me yeah once we have several reference implementations so we will be able to proceed to be accepting this job formula so we still have an open up question about the name so Jenkins for a while we have a comment from him which we need to address and I will be addressing this comment before accepting the job but yeah it's still a topic to follow up in the media in case okay yeah I'm looking to show that I wanted to go to show some context but I guess that's fine so about the docker editor channel you want to yeah so quick update we just have it so the story behind it that there are a few docker related gsock projects and there is generally a lot of repositories and questions coming in github issues um so the idea I proposed was to actually have a separate docker channel so that we could redirect docker discussions there and maybe we could consider it as a sub-project at some point like docker packaging um under umbrella of platform seek but yeah I'm not sure we have docker packaging and we also have docker plugins so probably it may make sense to split it to tour address later but for starters we just created a single github channel and let's see how it flies yeah I think it it's yeah I agree that fewer the fewer the channels the better it is because yeah it's like I can understand this makes sense to do to split things when there is a lot of traffic but I think the contrary is absolutely should be avoided at all costs when we have like two or three messages per week on each it's just a waste of time for a lot of people that have to follow yeah I think that docker channel will be pretty active so yeah I expect that docker channel um shields to readme pages and these readme pages actually will get propagated to docker hub so I believe we will get a number of participants like weekly so yeah let's see how it flies but it may be a useful addition for the docker focus packaging great okay and the last topic is about gsoc projects so last the last meeting I was talking about windows service wrapper updates and this project has been actually published as a draft and we will also get a second got second potential mentor there so yeah it's open for the discussion and feel free to comment but generally it's now on the web page what is more interesting that we added a second project for the sick it is plugin manager sli and library so the story behind that that we have a number of implementations of plugin management for example in configuration is code plugin in docker it's install plugin csh then in passing work package and in many other areas yeah having meetings from burger king is definitely not a good idea at least you don't see what happens here okay so yeah we had a discussion with batista and agreed that it may be a good project idea to actually unify these tools and they will create a single tool to roll all plugins in Jenkins so it would be firstly select tool so that you can invoke it in any configuration from any configuration management flows without starting Jenkins and it may be also a library so that it can be integrated into other tools so this what this project about and if somebody is interested feel free to just jump into to provide some comments or if you want even to become mentors yeah thanks a lot again it's interesting project because yeah it's really becoming more and more of a mess yeah and even I don't I don't I don't think you mentioned it but there's an open ticket and the showcases I think in the docker packaging in the docker report itself where uh we ended up saying or Nikola saying well I don't feel like we should add that or that because well yeah what I actually hit like yesterday or something indeed about the fact that uh the docker image right now the installer doesn't handle implied dependencies for instance which kind of makes sense because well you want to document the things you're doing and anyway you're going to test your image but and it's like a docker way so things are you know etched in the image from the ground up so that's that that makes some sense yeah the results another pull request so if you make me a presenter I can show it um one of the issues now with the plugin management happens manually and there were there is a proposal to show updates in docker and also to show security warnings so actually I created the pull request for that and well the pull request is staged and it's ready to be integrated but the problem that everything is written in shell and there are strong opinions that it shouldn't be integrated so I can I'm kind of stuck the way I believe it's a really helpful enhancement for the docker projects but if we could move the same to the external plugin manager so it would be a good advantage yeah to be honest I kind of agree with despite the fact I'm pretty fluent and I like and I regenerate this pretty a lot I also really think that it's not the great language for for growing projects overall as complexity grows we know that even like things like you know replacing a string in the middle of something it's just a mess in in shell and and so many cases like those and so yeah it's really time to stop and I would say scalable I guess something like this I guess we made a nice tour of everything so anything else before we close everyone so I guess see you from now thanks a lot for your windows work side and for your hosting efforts you said like 99% of the hosting requests are those days so and we host like three plugins pretty pretty in the week so that's not nothing so yeah thanks a lot anything else anyone nothing for me so see you next time bye see you see you thanks