 Hi, all. Today we have a short sync up about Jenkins, Asceptance, Thais, Harness and Java 11. So in the platform special interest group we are working on Java 11 support and there is a good progress there. So effectively we had a meeting on Monday where you can find all the information. It's linked from platform sick page and one of the lockers we have right now to release preview availability in Jenkins is actually a test automation because we want to have some test automation and Jenkins Thais Harness is kind of done now. There is good progress with PCT. There is good progress with Asceptance Thais Harness by Oliver and yeah at this meeting I would like to just sync up on Asceptance Thais Harness to understand how we can run it, how to test it and what is more important, how we can help to get this task finalized. So I have created a sync up document so I'll just put it in the platform sick check. Just a second. Oh yeah, I don't share my screen, right? Yeah, you're not. Okay, until now it wasn't right. Yes, I bought the recording again but whatever. It's an internal thing. Okay, so I've pasted the link to the status document here and platform sick. So effectively what we have now, yeah there is a status update presentation I was talking about. So it's linked here. It just lists all the current information and current progress and yeah there is a pull request by Oliver which actually has support for Java 11. So it looks to be relatively small but I believe that there are some upstream changes which are quite related to that like Selenium 3 whatever. So maybe Oliver you could briefly describe the current status and what's left to be done there. Right, I certainly can. As you surely know we started with, you know, putting things together on a heck of a sneeze and at that point the automation was broken because of switch to Selenium 3 and Selenium 2 stopped working for us. So ultimately the quite big change was integrated yesterday. So I started following and following with this work. Actually the first decent build of the effort I got running this morning rather than sooner. So we're finally getting some test results. There are some failures. I managed to briefly look at where we are. We were still identifying some problems both in the test suite and in some of the pipeline plugins. So it would be up to us to have a look at the result. I expected to complete sometimes afternoon today, have a look at where we are and we can start working up until now it was all just getting the thing, you know, getting a test suite started and running. So we can start have a look at the test failures. Yeah, right. With regards to pipeline plugins, there is actually a pending work for that. So there is Jenkins work flow support plugin pull requests. And yeah, there is Java 11 support. Actually there is multiple pull requests. Currently we have this one, Java 11 support clean version. So this is what you need to include into your build if you want to test the pipeline. So here's the latest snapshot I created yesterday because Baptiste also does experiments with Evergreen and we needed to upstream that. So in order to run anything against pipeline, you need that otherwise pipeline just hangs. And that's sort of interrupt. That's a new version of a plugin or a completely new plugin we have to throw in? It's a new version of the plugin. So pipeline support plugin is an engine which actually includes serialization context. So the problem here that pipeline data serialization to the disk doesn't work unless you have new Jbos Marshalling version. That's something I have identified and I found some pull requests. Could you please share this link to pull request with me? Yeah, I just put it to the status document. I still share my screen, right? Okay, so yeah, you can just go there and pick a version from there. But yeah, before that, it just doesn't make sense to test pipeline. There were some changes integrated on the core side, but yeah, I believe that 2150x actually should include all Java 11 patches. We know about. So if you run tests against the candidate for the new LCS baseline, technically it should be working with Java 11 fine unless we discover something new. And if you want to run Java 11 now, how would we do it? I mean, for example, take your pull request, how do we spin it up in Java 11? So maybe we could help with fixing particular issues. Right. I put together Jenkins file in a way, so it actually builds both on Java 8 and Java 11. So looking at the pull request verification and seeing at the CI Jenkins IO is probably the preferred way, except that there is a way how to launch it locally just in case you would like to experiment or quickly iterate locally. But I'm afraid this is not documented anywhere, so I will just put it into the pull request so people can have a look. So if you could do that, it would be really helpful. If I understand correctly, Ramon tried running it yesterday and experienced the issues with it. Is that right? Right. I check out the Oliver branch, run the docker image, enter in the docker image and run some scripts. The script that set up the environment and the RAM as an additional script. I have some failures, so this one is okay. I'm just wondering how to set up all the environment and the test to help with this. Right. As I said, until yesterday, we were stuck that some even more essential thing didn't work, so I got some real progress on that last night and this morning, so it required some changes because there was no way to provide this, you know, enable, unsupported Java or whatever is the option to actually provide this to Jenkins, so I guess it's new since this morning or something. So I have updated the description of the pull request, which hopefully enough of an instruction of how to run this, but of course if there are any questions, just shoot and I can improve the documentation needed. Okay. And just second, I'm reflecting the page. Oh yeah. So enable future Java for Fox LTS. Do we also need to pass specific environment for Java 11? Because if I recall correctly, so at least PCT tests fail if you do not pass models. How does it work with Java 11? I mean, how does it work with acceptance test harness? Well, I haven't discovered any such problems and a test suite is running right now. Okay. So enable future Java Jenkins Ops, but is it possible to pass Java Ops to acceptance test harness? Yeah. Jenkins Ops wasn't possible until today, and there is Jenkins underscore Java underscore Ops for options for, you know, JVM. Yeah. Jenkins Java Ops for JVM. So yeah, most likely it will be needed. Most likely we will need these things in order to run correctly. Okay. I just added it to the comment. And do we have any specific test categories, which would you recommend to run against Java 11? Well, I'm trying to put, to have everything run against that and see how far we go. This is the first decent run we've got running. So we haven't even got anywhere close to actually, you know, evaluating what was working or not. In Jenkins core, we have this, what is it called? Smoke test category, which is a very small subset of core-based tests. So I guess it would be a very nice low hanging fruit to get running against core, whilst we actually make sure that it makes sense. The other advantage is that smoke tests are relatively small. Yeah. It's like, I don't know, 10 tests or less. It takes maybe five minutes. So just a second pill show how to get it. So there is essential YAML file here. And effectively, find the smoke test category. Or like you don't seem to be sharing the screen. Or are you? I do. Oh, sorry. No mistake. Okay. So yeah. Thank you. Yeah. So profile run smoke tests. Or if you use essential YAML, something like that. Yeah. It should enable this smoke test. So yeah. With that, it should be possible to run it locally and maybe explore some problems. So for example, we know that plugins like Djokko core will likely fail. And most likely Kuberstura as well. So if there are ETH tests to confirm that, it would be nice. Right. I presume that we will get quite a lot of input on what does and doesn't work. So I'm wondering what's the preferred way to communicate back to platform usage? So what we have in JAP 200, sorry, JAP 211 on JAP 200. So here we have testing section. And there is a Google doc, which actually contains all the tests we are about running. So now it's pretty much empty. But yeah, what we were doing for JAP 200 and what makes sense to do it here, if you hit any issues, just put it to this Google doc. And yeah, if you submit the tickets, link it from there so that we have a kind of central document for issues we discover. Right. So we'll try to feed it with yours. So if you reported here, just make sure to add your name so that we know whom to contact. Yeah. And we also got a plugin compatibility test framework running. So we will be also updating some results here soon. Effectively, what I want to get in the beginning, in the end, JAP 2000, I believe. So in JAP 2000, there is also testing and there should be JAP 200 testing nodes. So it's a pretty big document we created together with JCGleek and some other testers. It's what we were testing and updating before the JAP 200 release in the weekly. So yeah, something like 20 pages, but each document is rather something like that. So what we hit, what's linked if applicable pull request and yeah, that's it. For JAP 200, we had to update a lot of plugins because ancient plugin forms didn't support it. I expect we'll hit pretty much the same for JAP 211 when we run PCT. But for substance test harness, it shouldn't be a problem. It should be able to run existing tests without modification. So yeah, if you hit anything, just put it to the document. Right. If you want, I can give you edit permissions so that you can just watch the document. It'll be good. Should I also give permissions to Lucie? Yeah, please do. So I have only her red heart email and I also give access to Ramon. I will likely need your Gmail account link. So I'll also give you access later. Okay. Okay, thank you. So we can just use this document in order to report everything and sync up with that. And yeah, actually, one question I also had left is how we can help. So for example, if you know about any tasks in addition to testing and exploration, just let us know so that we can report them in Jenkins Jira and maybe help to get some tasks for the fence. Yeah, I mean, speaking for myself, this certainly helps. More guidance of what to do, how to proceed would definitely be good. Unfortunately, I do not have enough information for what are the specific areas and the APH would need help because, as I said, we only get it running this morning. But I presume that we would have that tomorrow or something like that so we can get our hands dirty later. Okay. So what we could start working instead? So there is some understanding of what needs to be done on APH, but we also have Jenkins Infra pipeline library. So current Jenkins core, so in Jenkins core, we have enabled Jenkins Test Harness for Java 11, but we didn't enable acceptance test harness so far because we depend on this run ATH step. And the advantage of this run ATH step is that actually it allows pinning version. So for example, since you are doing patches in your repository, it would be possible to just get Jenkins. So here, you may see that there is Essentials Test YAML and that there is an ATH revision. So probably one of the things we could take to help is to try creating another ATH step for Java 11 and looking at whether we can update Run ATH to run with this step. So it's effectively Jenkins file and Run ATH is here. What do you think about it, Roman? Okay. It's interesting. So generally, while we wait for the first run. All right. I guess one thing you would have to do is to update the ATH revision to version that actually supports the Selenium tree because I suspect that the tests are just failing all the time without it. So this is something to review whether the core build is actually have a healthy run of ATH just failing for something terrible. So we can update it to at least give it a chance to succeed even if it wouldn't really work for 11. And I'm just browsing through Run ATH just to verify whether we need to change anything on the first place. There is a chance that it would actually pick the changes in the port request in ATH. I've got open. So it would actually consume that and test against both versions. It would probably be the best. Yeah, right. So if you cannot merge your pull request, it may be something which would help to get running Jenkins file. So this is something we can start working on now. And yeah, it still allows exploring it and maybe discovering more issues. And once you have this first run finished, yeah, I believe we could sync up on Monday then. And I think what needs to be done there because yeah, most likely many tests will fail right now because if you run without pipeline patch, all pipeline tests will fail for sure. Probably it's also a subject to update because we can update your pull request in order to integrate models. Right. There is one other thing I can think of all of you might be, you might recall there is a pull request or pipeline library to actually permit it to run against both versions, I mean several versions of Java and different version of Jenkins, which is one thing that we haven't released all along. So update run ATH to support multiple versions of Java. I'm sorry, that's not what I'm talking about. I guess it's the pipeline library. Maybe we have what is it built plugin or which one is the one we have modified. Oh, you mean getting this pull request over the fence? Yeah, I'm just trying to find it right now. Well, there is a ticket in Jenkins G for finalizing it. I'll make sure it is linked correctly. The fence. Okay, that's the one. It doesn't seem to be any objection of an interesting discussion. I'm sorry, I might not see any comments there. But the point is that what would certainly help me to finish this is to have a way how to get it tested or what was the process of getting it actually deployed to CI Jenkins IO? Okay. So there is no process for that, unfortunately. But yeah, there is an instance how collecting a bunch of demo Jenkins configs code. So effectively, this demo reflects configuration of CI Jenkins IO because it was specifically designed to run build plugin. And when we were working on the hackathon, I created a branch for Java 11 support. So this branch actually includes the JDK 10 11 images. And if you want to test the script, there are guidelines how to actually test that. So we're developing pipeline libraries. So you can pass your local location over the pipeline library and run with it. Yeah, I guess this is what we use that a hackathon and it's where we where we developed that. So you're confident about a fix. So can we just ask Tyler to merge this and deploy? Technically, I can do that. So I'll review it today. Yeah, I did some initial testing. It seemed to be working for me fine. So yeah, to review the cool request. Technically, I and Raul are currently maintainers. So yeah, I'll just do that. Right. So this will permit us to actually test individual plugins against Java 11. Yeah, right. So even now we can technically do that. But it requires some hacks. So maybe we'll verify it. We are running overtime a bit. Is it fine with you guys? We come again. So it's already beyond the meeting schedule. But yeah, it should be fine. So this patch already allows running it, but we need to somehow support both versions. And he would only be implemented in this pull request. So yeah, I believe it can be merged right now. But yeah, double check and then provide review feedback. That would be great. I guess there is a white space ignoring if that is not all that scary. And one thing I'd like to do is just add some documentation so people can discover it and find how this is something I haven't done for now and I'm taking the action item. Okay. So generally, this pull request is also in the list of blockers for a J and Jenkins weekly. So we should get it over the fence. Yeah. So I believe that's it. So we have some tasks we definitely need to do to get all these stories over the fence. And yeah, I believe that we'll need to do all of that. Ramon, do you have any questions about these tasks so maybe we could clarify some things together? Yes, indeed. I have a lot of questions about these tasks. He brings them on. Because I have no too much context about the ATH. So I will need some help with this, perhaps after the meeting. I can sing with you or even with Raul that knows a lot about ATH to try to help me because now I feel a bit lost. Okay. So let's sync up after the meeting. And yeah, what would be the best channel for us to communicate? Is it RC or Gitter? Oliver, what do you prefer? Well, I don't feel strongly. I'm not yet on Gitter. So I guess that's something I'll have to do. Okay. So let's just use Jenkins then. Jenkins, RC. That would certainly work. I understand that there's quite a lot we managed to cover we all like. I mean, I sort of envy all that he managed to understand all that and keep track of all this. So definitely all like, thank you for bringing all this effort because I have no idea how it would work without you. So I do understand quite a lot to cover. So perhaps you guys, I don't know, narrow the scope where, you know, where it can actually help. Yeah. So we will review these tasks and try to break them down somehow. So there are many people on this call. And yeah, let's see how we can organize together. Okay. Yeah. And thanks a lot for doing all this work with acceptance test harness. Yeah. It should really help. And yeah, this thing we also integrate, of course. Okay. And do we have anything else to discuss for now? I'm afraid we don't. Just one single question. Do we have a follow up for this? A follow up meeting? Yeah. So I believe everybody needs to stomach the information a bit. So let's try doing something next week. But I'm not sure. Do you have any preferences about the date? It's at a similar time. Works for me almost every day. Oh, that's cool. So yeah, probably we could just set sync up maybe even on Monday or Tuesday to review each test run results together. Yes, they work for me. Okay. So Tuesday it is then. So it will just help us to understand what's left on the quality side of it. Or maybe even Wednesday because I would also like to involve Kevin. It's one of engineers working with test automation and test quality bars. But yeah, maybe Tuesday or Wednesday. Most likely we will need to rerun ATH with pipeline flux by this time. So, but yeah, if we do that, there should be some information for discussion. Okay. So I'll set a meeting to Tuesday and then yeah, let's see whether we need more syncopes. But in general, we'll try to keep these meetings short. Sorry for running over time at this meeting. Okay. So thanks a lot to you guys. I will stop the recording then now. And yep. Thanks again. Thanks Oliver, Ramon, Adren. Thank you very much.