 Hello. Welcome to the Jenkins contributor summit. Today is June 25th, so thanks to everyone who attended the ACD con. If you attended the full conference, you already had three days for various talks, including many Jenkins talks from our users, from practitioners, from tech leaders. And today we actually focus on contributors and we will talk about how we evolve the Jenkins, we will talk about various issues and topics we would like to address, including interoperability, technical changes in the Jenkins core. We will also have a track for newcomers. And I think we can start. Okay, so what we will have today, so we have multiple sessions, I will show a better legend later. Today we will just have overview of what is going on in Jenkins, we will do some announcements, we talk about project and team updates, and then our sub-projects, special interest groups, etc. We will also be able to make the updates. The idea that this session will be a related shot. If you want, here's a link to the contributor summit slide deck and the program marker could share it in the chat so that everyone can access it. So, our slide deck is already public. Yes, Kara. Oh, so you want to promote. Sorry. I'll take care of that. Oh, like I mean, I'm working that. Okay. So, yeah, welcome to the Jenkins contributor summit. This is, if this is the first time for you, I will quickly explain what happens. The idea is to actually gather contributors from around the world, or at least from a time zone you have. So this time it happens in the America's time zone, and I hope that the next time it will happen in a packed time zone so that we will have a different slice of the community participating. But still, we have many people and hopefully we will have more people joining. What is the contributor summit? So this is an event which is focused again on contributors. It's hosted by contributors so you can see various, not so finished slides, you can see some organizational blunders, etc. So we are not doing a marketing conference. We are focused on the contributors on this live discussion. We invite everyone to participate to show live demos. We will have a session for lightning talks, which is still available. We will have an user panel, and everything is about conversation. So the goal of this summit is not to show many cool presentations but just to actually achieve something as a community. So this is a one day event. Actually, I want to be lost for six hours and the legend is available on the links. So once you get the slide that links you can just navigate because this slide is public. Okay. So here are the items for us. So firstly, if you're a newcomer, we have a newcomer track where Mark will be talking about how to contribute to Jenkins. This time, this is the first time when we have an user panel, we have multiple users of Jenkins joining and they will share the experiences, talk about the issues that experience with Jenkins and expectations from its evolution. So this is the first experiment, and I hope it will be successful. And if so, let's keep doing this sessions. And then we'll have a pretty long conference where we'll talk about topics which we discussed before the summit in the community. So there was Google Doc where everyone was able to contribute. So the idea that we will have three sessions. So, what are the topics here. I think on interoperability Jenkins X, we have actions in Jenkins cloud integrations open telemetry and observability. All of these are topics related to other projects. So it's basically interoperability integrations. And this is how Jenkins works is rather both integrations with other systems. It's easily a different issue or not. We are happy to support these integrations anyway. Also, we will have a discussion about a core Jenkins and its evolution. So there is a topic about the plugin and the fly policy. We'll talk about the goal of the technology update in the Jenkins core. And then we'll talk about Java 11 and 17. And the last but not least, we have a discussion about Jenkins Kubernetes operator, which is a new sub project to join Jenkins. And if you use Jenkins and Kubernetes, this is definitely something you would like to consider. After that, we'll have ignite talks and demos. So if you're a member of the chat if you have access to the agenda Google Doc, feel free to make proposals because we still have a lot of slots for unite talks and demos. If you want to present anything about Jenkins reslides results slides just live demo, please do so. This is the session specially for that. And then we will have closing session and happy hour, which is likely to happen either you zoom or in the work convention, depending on whether we will get the system running by this time. Okay, so you may have experienced some issues with connecting to this event. We will be sending links in the chat later. And these are temporary links for all the sessions and believe that Mark will be able to confirm these links going forward. Yeah, in the worst case, we have a slug. I'll share the links where we can do the coordination. So, you may ask where to go for newcomers. Yes, you start from the newcomer track. And then if you feel that you've got enough information, you can just switch it to class contributing to Jenkins track and it's up to you. For seasoned contributors, of course, we recommend to start from end user panel, because this is a session when end users will be talking to us, you're probably they will have some topics to share, maybe not that positive feedback but this is why we invited them. And this will be in the session. So usually it's contributors to presentations and users asking questions, but we will try the opposite. And then of course break out sessions and everyone is welcome to join our happy hour. So we will have more chat if you don't fall asleep by this time, it will be something like 8pm UTC, I believe, or 7pm UTC. Okay, regarding discussions, again, everyone is welcome to participate, share your feedback, share your proposals and do lightning talks. We also have a code of conduct, this code of conduct is based on contributor covenants, so please be nice, respect everyone and there is a lot more words but it's like that. For the conversation we have a Jenkins contributor summit channel on the CDF Slack, if you want to join, there is there are guidelines how to join. So you should follow these guidance so that you can connect with arbitrary email and it's basically just clicking this link entering email receiving the invitation and then accepting it. So, if you want to join just follow that and you will be able to participate in the summit. So, we will use this Slack channel for all kinds of communications and again we will post links to the slides etc there in parallel with the chat. Okay. This is all with the introduction. Now we have state of the union. So this is a summary of everything going on Jenkins. And this time we made some improvements because one of the feedback topics from the previous years was the state of the union is too long. We addressed this feedback and now we will try to do all the updates in 40 minutes. So we will have something like 10 people who will be doing a lot of internet talks right now, and get ready. So, let's see how it works. Okay, so I'll start from some governance updates and then we will switch to project updates, etc. First of all, I would like to thank Marki Jackson. So at the last time he was a board member and Jenkins events officer, Marki has decided to step down but thanks a lot for all your contributions Marki. And when you're ready, you're welcome back to our community. And then we will talk about the evening later, we will have some updates on communication channels. Thanks to our contributors treasury and community of arts. There are many other topics we can discuss during breakout sessions and later. Yeah, since Marki stepped down, we invoked our process for temporary work members, and we would like to continue to the ability in a wheel case for joining the Jenkins governance board effective for the February 20s. So, really, I will be a fifth member of the Jenkins governance board along with me, Kevin Morgan, will you have to run course a care and been in depth to focus on the end users communications and for example, the today's end user panel is actually inspired by a really unfortunately she's unable to join today, but we follow up on the discussions we had for the last month. Okay, also update for me. Yeah, I became acting Jenkins events officer so I will be a go to contact if you want to organize an event regarding Jenkins, etc. And I'm also joining the city for our technical oversight committee starting from July 1. So, before that it was also care representing the Jenkins project there. And if you have any questions to the city of just contact me and you will be able to follow up and again my job is representing the Jenkins project, making decisions for the Jenkins project, as I understand the million keys and any feedback and suggestions will be always welcome. Okay, a few major updates on the communication channels. I believe them and we'll have some more to say later, or maybe them and would like just summarize the updates now. Okay, then it's me. So firstly, RC used to be our main communication channel. It's not long actually through we still use RC but it's just the first class citizen along with many other channels. So we had to be created from a free note RC to liberal chart during due to the events. Well, everybody heard off in the open source community. And now for our main channels on the liberal chart, and because about eight other channels because we decided that mailing keys and guitar enough for this purpose. So if you haven't migrated to liberal chart yet, please do so because Jenkins and also hosting and the release teams are there, and also infrastructure teams. So if you participate in various infrastructure related activities is definitely a good channel to them. And the rest, yeah, you may have seen these slides we actually have too many communication channels. And thanks to Kevin Morgan, Oliver and other contributors, we actually hand in this pro and we introduced another channel to resolve issues with too many channels. So, thanks to discourse, we were able to deploy a community jinx IO it's a sponsored service, why we intend to move the most of conversations. It's not that we abandoned mailing please we will keep using them. But many conversations for special interest groups, etc, can now happen in the community jinx IO. And today's presentations will be referring to it multiple times. So, if you want to have a discussion of many topics. It's additional channel you can consider. And if you have a nervous in a discourse it's a kind of forum, where everyone can contribute and create their own topics. And what we have there we have placeholders for using Jenkins for contributing for various community things. Also language groups like the Spaniard Jenkins Jenkins, and there will also change the Jenkins soon. Again, everyone is welcome to contribute and expand this platform as a central communication point for unofficial Jenkins communications official communication still remain in the main case for the time being. Okay. We're going to update about our cash flows. So, as usual, we have not that much updates and we don't have much money, you know, but we have some. We have around $30,000. Over the past year we invested a lot in outreach, we invested a lot in our infrastructure. So we started from 30 K into 719. Now we are down to 13. I still like it on SPI but we will be moving to LFX crowdfunding soon. It's arranged. It just needs some governance when we do the migration. And currently we have quite a lot of money reserved for Google summer of code. So it's for Google summer of code 2020 and 2019 because we were unable to spend all the budget because of coronavirus etc. So we have some money reserved, and we will still receive the event for this year so that we will be able to sponsor students and private travel grants should the situation normalize by this autumn. Generally for contributors, please reach out. If you have ideas how to spend money. This is why we receive money from the major donations. We expect to spend them at the facility. We have multiple initiatives on our roadmap and we invite everyone to invest so that we could actually spend them. For example, documentation projects, design projects, and just develop new features all as possible. And yeah, thanks to our sponsors. This list is not complete so the Jenkins project can survive from this amount of money. So you can see 13,000 and while it's not that much, we spent a lot more on infrastructure every month. And thanks to our sponsors who make it possible and his delivery foundation, my AWS cloud bees, Red Heart, Bit Hub, JFrog, also all of them invest a lot of money to support Jenkins via various programs and also there are many other companies which support us through open source programs. For example, yeah, I just referred to this course, it's sponsored by this course house, this course construction, the company between this course and there are many other sponsored companies helping us in infrastructure and other services and yeah, thanks to everyone who supports the project. Okay, last update before we switch to more interesting parts and Cadiz delivery foundation community awards. So if you participated in the ceremony yesterday, there were multiple awards, eight awards plus project awards, so maybe 14 in total, focused on different contributors and there were multiple Jenkins awards because Jenkins is a dated project so we were able to have three hours this year, most valuable Jenkins contributor, most valuable Jenkins and security MVP, and we would like to congratulate the winners of these awards. So Tim Jacob, second year in a row, he's a most valuable Jenkins contributor, and it's well deserved. Thanks for your contributions team to various areas including infrastructure, user experience, configuration, scope, et cetera, et cetera. It's hard to say where Tim doesn't contribute this year. Daniel, Daniel has been Jenkins security officer since 2015 when this position was introduced. And this year, we were finally able to vote for Daniel because this year everyone can be nominated before the club this employees are apart from receiving awards. But this time, yeah, finally, we are able to recognize Daniel, who has been driving security and the most of the advisories over the past years, and well, a serious job, I believe we had almost 100 advisories by this point. And yeah, a lot of security issues disclosed all of them required in the nation. And again, thanks Daniel for that. So, yeah, most valuable Jenkins advocate that's me. I can share this later. I won't praise myself. And what I would like to say that Karadela Mark, currently the leader of the Jenkins cloud native seek, she became a top gtops evangelist, because your car is one of the top promoters of top and also secrets management and gtops. So, yeah, congrats Cara. And I guess that's it for today. And we can start from a project in teams updates. These updates will be relatively short because we had a contributor summit three months ago. So, we will have reduced updates compared to previous events when we had six or nine months updates. Still, we have quite a lot of content and we have something like 30 minutes left. So let's get started. Thank you security. Oh, like I think you may need to promote Vadek as a, as a panelist, I don't seem to have the permission to promote him. So sorry for the disruption there. Okay. Yeah, by the way, I have a slack open on my phone so if there is any destruction you can just ping me there. Oh, thank you. Okay. So I added Vadek. Anyone else I should add. So could you hear me? Yes, thank you. Go ahead please. Thank you for the reaction. I didn't thought you were talking so much until the point there. So perfect. So next, just for the introduction, I'm talking here instead of Daniel bag Daniel is just taking some PTO for having a longer weekend. So to reply to your question, Daniel, like in terms of number of advisories since the beginning of the project, it's 124. So not everything from Daniel alone. We were a team recently about security at the beginning. It was mainly Kosuke doing the thing. So just for the information in the last three months we published 10 advisories with a total of 46 vulnerabilities in total. So that's interesting. The number of growing and things like that. So we need to keep the pace in essence. Please next slide. So what we did in particular outside of the advisory directly. Recently, we did some mentoring for a master project in the Jenkins security area. It was with four students from Marseille in the source of France. They were doing some auditing for a lot of plug-in. Perhaps as a maintainer you have received some of the reports from them or things like that. It was during two months and at the moment 14 vulnerability were published. So we were very interested in the outcome there but also in the investment during the process during the project. They were very curious. All the things there were interesting for us for them for the project. So that was just a very nice success from my point of view. Just in case, there is a blog post if you want to read it for more detail and especially at the bottom of the blog post, there is a sentence saying that if you're interested in such project as an intern, as a student, as just someone wanted to do a bit more security things, please contact us with pleasure that we will set up something to work together. Please, next slide. So also concerning the different initiative we are doing, recently we got another XSS in Credential. So that was impacting a lot of instances. And so we decided to rewound a bit, to reset a bit the effort we were doing with content security policy. In a sense, with that API that we have the link at the middle of the slide, it's something that is really interesting in terms of protection against XSS, especially in the context of Jenkins. We have a lot of JavaScript that are in line inside the different page. And if we are removing them, we will unlock the possibility to have a CSP configured at the instance level and so protecting against a lot of XSS. Good feeling at the moment, 90% something like that. So if you want to help on that area, please contact us as well. There is information in the ticket and also you can see some pull requests sometimes about unaligning JavaScript content. So the topic is interesting, not only for Jenkins, if you want to learn more about security in general, that's also a good opportunity. Next slide, please. And also Alex was doing a very good job about the hosting request because he was doing some preliminary tests, preliminary audit in terms of security. It was mainly about like checking if there was some credential usage, some method that could be dangerous and things like that. This kind of preliminary audit was very useful for us in the Jenkins security to not spend time to do full audit on every hosting request. And with that quick approach, that was very useful to save us a lot of time. Because Alex is doing the auditing or at least was doing the auditing during the hosting review about the quality and things like that. So if there is any volunteer about this kind of part, this kind of job, please also reach out to us. That could be useful. And I think that's quite done for the things we did. What is next for the security team? So, Sunish, we will have a new advisory for the next core release with some vulnerability. I cannot disclose anything at the moment. You will receive normally information from Sunish. And we continue to do the different auditing we are doing for the different plugins and things like that. So expect to hear about us in the future. We will find something else. Thank you. Thank you, Wadiq. I will do a quick update about other topics related to Jenkins security delivery life cycle. So this is a follow-up from the previous contributor summit when we discussed this topic in depth. One of our follow-ups was to continue this job 229 continuous development on Jenkins components. And I'm happy to say that this initiative got some progress. It got some adoption and actually you can try it out if you maintain Jenkins plugins. So it's fully available for adoption. There are some things in there. For example, there is an energy stock project related to improved version of releases in our CD4. But anyway, you can start using that. And you can start adopting community plugins if you want to deliver Jenkins plugins for every pull request and for the merge commit. Okay, another update related to security. We started a joint partnership with the Linux Foundation team, particularly LFX and WeSneak. And the idea that LFX security is one of the host services offered by the Linux Foundation, which intends to perform all kinds of security. So currently it has two services inside. One is Sneak and it's focused on dependency scanning, analysis, or some license scanning compliance. And soon there will be a blue bracket introduced. It's all of the available for preview for limited number of projects. So it will be a basic analysis for secrets and the code brains for misconfigurations if you use configuration files and also for common mistakes in the code. We participate in the project in order to adopt the new version. And if you're interested to discuss why you feel free to reach out. So there are a few examples of how it looks like. So this is for example dependency analysis for Jenkins with vulnerabilities being disclosed. We also can get the issue details with references to CVEs. Jenkins can issue its own CVEs because we're CNA, thanks to Daniel Beck. So for all our advisors, it says we'll be releasing information about vulnerabilities on our own. And they become available in the database and then they become available in our scanners. And same for license analysis, so you can analyze what licenses have been used and sometimes components use licenses which are unable to use inside your company. And you can analyze that. So I'm showing you a red herring case when we have a GPL3 library configuration as code plugin. Please be sure it's not a concern in this case, but it's a nice example that we definitely need to work on false positives. Okay, and as I said, we participate in a polite project, so Jenkins was one of the first projects to join and there is a lot of security to zero. It will be adopted by the Jenkins infrastructure team and it will be adopted for Jenkins once there are particular features available. We are waiting for them because currently we cannot really adopt because of massive number of false positives. And once the fix is available, we will be happy to try them out and to stop our skype lines powered by sneak and LF security. So thanks a lot to all contributors who are looking into this story. Next topic is Jenkins infrastructure. So Damian, would you like to take over? Yes. Can you hear me? Is this okay? Okay. So I'm replacing Olivier today. He has a child who is sick, so I'm replacing him. He's excused and a good excuse. So can you switch to the next slide? So what happened during the past month on the infrastructure? The cost increased. These are facts. It's almost 2000 bucks per month more. You see that also the difference between AWS Azure and other sponsors on the cost we can evaluate has shifted a bit. We depend a bit less on Azure. Next slide, please. So we are working and trying to determine if this costs increase come from things we can work on or if it's intrinsic. So we have more downloads of more plugins, more people visiting. So we cannot say stop. This is an intrinsic cost increase, but there are still some levels we can work on to be sure that we control the costs. So we'll speak about that. But mainly we have two main personnel that are responsible for the services we provide. The users that download plugins or visit the pages and the developer will use CI Jenkins.io in order to build the plugins to contribute to validate the codes. So these are the two kind of person that we want to serve. Next slide, please. So one of the most important achievement has been the download mirror. It's for the person of the Jenkins user. So what has been done is providing more visibility for people. And better performances and we reduce the time between one artifact, a plugin or code release is published and deployed and the time it's available for everyone across the world. One of the main services that you can use as a Jenkins user, if you have any issue or have question, you can add on the query string, one of the three elements on that. For example, that will show you a nice WebView to see where are you located, which mirror are you using currently, and a bunch of stats that could help you diagnose. The goal is you should be able to be autonomous to determine if there is an issue on the Jenkins infrastructure or on your network or on the mirror and switch mirror if it's the case. Next slide, please. Another element is more transparency. This is for every persona and for the maintainer as well. So we try as much as possible to give you a state of the infrastructure on status. Jenkins.io, which is a new web service. The goal of that service is to let you let you know if there is something going wrong on our side on your site. Everyone is able to contribute if you detect something faster than us, that can happen and it happens. You can open a pull request to start an incident. You have access to metrics. You have access to maintenance window on the future. And each time there is an incident, an outage or something, we try to be as much transparent as possible and publish this post mortem afterwards. So don't hesitate if you have any issue, proposal for improvement, because it's brand new, we are far from perfect, but we try to give as much information as possible. So you will be again autonomous to determine if it's an issue on our side or on your side. Next slide, please. So the next step for us in the upcoming months, we started and we are going to keep the priority on controlling the costs. So that means diversifying cloud providers to be sure that we don't have a big outage will limit the blast radius when something goes down and also because different clouds provide different services for different costs. So if we can use a lot, we will have a more sustainable infrastructure in the future and an ability to switch the cost and control them a bit more as much as possible. Next slide, please. Also, a big effort is currently being done and will continue to be done during the summer on CI Jenkins IO, because that one is responsible for a part of the cost increase. So there are more activity, but we can still control more elements. In order to do that, we need to improve measurements to be sure that we control everything. And so we have foundational work to do. The main idea is to make that Jenkins instance, the, let's say the reference for everyone using config as code automation multi cloud providers. Next slide, please. So just one slide to thanks all the contributor to the infrastructure because we have people working day to day but we have people doing valuable work punctually weekly monthly depends. If you're interested, if you like this, don't hesitate, we try to be as open as possible. This is a shared infrastructure. Everything is open except the credential, I hope. But for the rest, yeah, thank you very much for everyone who contributed, even if it was one line of documentation, it's still a contribution. If it's reporting an issue, it's still a contribution. We need you don't hesitate. Go visit us. Next slide, please. So here you can learn on the static page on your own page. You can check the roadmap you can join us on IRC, and you are welcome to join our weekly meetings. So you can find on the link on the slides, the slide I've been shared on on the chat. If you want to join us participate or just spectate you are more than welcome. Thanks that will be all for me. Thank you. And yeah, then we'll have some updates from special interest groups and tails. And the first group we got invited this year's group. So team, would you like to share what's going on there. Sure. So few months ago, we got new build status icons and wither icons. That's in the latest LTS 2.289. Early's been doing some work on bootstrap five and each arts five. I think those are all available now. And some of some of the major plugins are updated to them. J unit is work in progress, but should be done soon, I think. And the charts configurable for the plugins that have been updated to use the new versions. So you've got a few more options kind of to replace different size options used to have in the old graphs. There's a poor request dashboard plugin around which is getting some integrations with different plugins. So you can customize what your poor request dashboard looks like. Code coverage and warnings in G and probably others. There's a pipeline view plugin that I've been working on which pulls the blue ocean graph into the classic UI. And there's a work in progress progress for logs as well. So it's quite nice. And hopefully means that we got to get rid of blue ocean for some of the people who don't enjoy it so much. And recently, Gavin Moven's done some work on the plugin site and searching release notes and we had a contribution to give suspended plugin pages previously they were just for four pages but now I think there's a link explaining it. So all some good improvements there. Thank you. And for some items on this list that if you want to know more. Currently we have a section on the community. It's just called show and call. And this is a session where we can find all recent updates. So, for example, let's take a look. Here we have Gov and team talks about blue ocean button classic UI. And here you can find some examples and links to the repository. So this is one of the ways for you to get new information because we encourage contributors to actually post quick updates here about what they're doing. So instead of spending much time writing the blog post etc here you can put an update just in a few minutes. And we will be happy to use this update to promote the work you're doing in the Jenkins project. So, thanks team for this work and thanks to all of you are you seek for all the improvements in the recent patients, because Jenkins has changed a lot over past year. And experiment I launched the version from February last year and from today's special one week ago and they were completely different in terms of how they look. So, nice work. Looking forward to see plug in monitoring and look forward to see motions. Thanks team. Anyone else from or is anyone else from the US sick, who wants to share the experiences. Sorry. Okay, then platform sick. Mark, would you like to share that right. Yes. So the platform sick continues to meet and discuss platform related topics like Docker and Java versions and operating systems. We've upgraded the Java versions and the operating systems inside our Docker images. We're really pleased with the results we're getting from the plug in installation manager tool. It's now included in the Docker images for the controller and the documentation PR has been submitted by Sudakar a new contributor so we're delighted to have new contributors who are submitting relevant and significant documentation improvements. The support improvements have arrived in core free BSD support improvements are coming and we're seeing lots of people doing testing and wider use with arm platform so it's not just an Intel world anymore. Next slide. We'll be discussing in the platform in the summit today, upcoming changes that are been proposed relative to Java 11. There are some different choices we need to make in terms of what the path should be forward for Java 11. And likewise in September, we expect that the open JDK project will release their next long term support release JD JDK 17 JDK 17 will be discussed in that same contributor track. And we have ongoing need for further Docker updates, including upgrades to Java and operating system upgrades as new operating systems are released and new Java versions are released. That's all that I've got all right. Thank you. And the next cloud native seek. So part of the coffee and should you give a quick update. Hi, I'm cards and I'm up I am, I lead the cloud native sake and really it's a space for individuals to to be able to bring their ideas on how to make Jenkins itself more cloud native. And I don't know why I'm not showing up but really, you can bring the ideas that you want to work on and we've had an fantastic year so far because a number of people have great initiatives to move forward and we have three of those individual contributors. So to you today we have Bartek Antoniak, we've got Bobad and Shruti Chaturvedi and Bartek will be speaking to you about the Kubernetes operator for Jenkins, which he has been involved in leading and also leading a G sub project on that Kubernetes operator. So Bob will speak about the second time plugin, which he created the POC for and has been working on and very exciting developments there and then he will also speak about the cloud events plugin which is now a G sub project that Shruti is our mentee for and all three of these individuals will be leading breakout sessions later in the day so please do join them because they are going to be incredibly interesting. So the cloud native sig itself meets by weekly on Fridays at 11 UTC. So please do join us for an open meeting we're very friendly, you can just bring your ideas and chat with us ask questions get involved, and we hope to see more of you. Thank you. Thank you. Okay, all right. Hi everyone so I would like to keep it simple now because we have another session later this afternoon so we can we can deep dive into particular topic and guys engage with the wider community. And I would like to focus on three key areas, which is roadmap and future releases so what team is currently working on. Then move on to a summary of the feedback, mostly from our community talks and some dedicated feedback for me to understand how people use Jenkins in a cloud native environment mostly in terms of Kubernetes and and how we can improve the overall experience. And finally, talk briefly about our involvement in the community space, because this is the very first time we are part of the contributor summit and recently, Jenkins operator itself became official sub project of Jenkins so there is more yet to do more yet to come. Could you please move on to the next slide. Okay, so one of the major things we are currently working on is a new API schema for the Jenkins operator. We want to basically provide more granular custom resources instead of having one big configuration file. We have more smaller individual parts, which can be configured independently, just to increase overall developer experience, as well as think about modular code base, which is easier to extend we can implement support for other platforms more than other capabilities, people basically can contribute in a better way, because we don't have this monolithic architecture, and it's fully modular. And a part from that it also helps with testing strategy, because we can test individual pieces running in individual reconciliation controllers when it comes to operator pattern. Beyond that, we also want to provide better integration with third party to link, especially in area of cloud native technology landscape. For example, safer injection allows us to integrate Jenkins with service mesh technology, for example, right. We want to stay on top of the technology upgrade SDK all components and bring back fixes and improvements over time. Could you move on to the next slide. Speaking of summary. This is the slide. We first we wanted to understand how people use Jenkins operator. And, as you can see, the Jenkins operator is mainly used in big enterprises. We have quite special problems mostly related to multi tenancy, doing everything at scale, and also some security and compliance issues. We want to simplify when using this operator. Next slide please. One of the main problems operator already solves. So this is the plug in management and dependency health problem so we can install plugins programmatically we can manage versions thanks to this plugin installation tool, which is part of the implementation. This brings a more scalable and better solution for developers so the entry point is lower for developers. They can easily build and deploy fully operational Jenkins at day one. They can configure everything in cold, which opens room for gtops model immutable infrastructure and basically scaling DevOps team in general. Next slide please. And, of course, we still have plenty of things to improve. And I would appreciate to understand what are your, what are the pain points based on the summary from from the feedback form backup and restore is still the thing, especially on demand how people can control backup and restore how backup restore strategy should work in Kubernetes in Jenkins. More granularity for configuration assets so how DevOps team can configure individual pieces using configuration as called. And again, plugins management related to versioning compatibility caching, all of that. So we still need to work on that. And I believe there will be a last slide. Do you want like. Yeah, so last but not least our involvement in community space so as mentioned earlier, Jenkins operator became official sub project so we are fully committed to be part of the of the governance board of the Jenkins community contribute to Jenkins itself be active. And also we take part in Google summer of cold. We try to implement additional security capabilities related to installing plugins, basically would like to have an additional security layer when installing plugins and monitoring security vulnerabilities on the fly. And, and also it's worth mentioning that we plan to have closer cooperation with continuous delivery foundation. I don't want to disclose any any particular information just will keep informed as soon as we finish the formal steps. And of course, dedicated category on discourse, feel free to bring some new topics, especially let us know how we can engage maybe there is particular topic we can talk about community meeting. So that's pretty much all. Thank you very much. A quick question. Maybe we could postpone it later because we're already running out of time. Okay, so hi guys, I'm the above. So before we move on to like the plugins that the cloud native site is actively working on right now. I would like to kind of talk about this idea of factors of interoperability, based on which we have chosen to work on these things. The first thing I would like to talk about is like factors of interoperability means that you know, when CI CDs need to work together, they need to figure out some stuff like they need to figure out through what factors they can work together. So we figured out that there are two different factors in which this could happen. You could work directly with other CI CD tools by in a client based approach, or you could indirectly work through events or like data streams which would kind of trigger jobs based on, you know, just events that might happen from other CI CD and you would listen on them, and based on them you would trigger your jobs are like pipelines. So this is the approach we went with when thinking about like what projects to pick up. So, looking at the examples. Next slide. Yeah, looking at the examples we have. So for the direct interoperability, we, we want to focus on tecton because tecton is is now like the first class Kubernetes CI CD pipeline system, and it provides a really good way to create pipelines which are based on CRDs and Kubernetes and it is very, very modular in this way. So, for that we started with the tecton client plugin for Jenkins, and this is this is the first take at you know, interoperability between Jenkins and tecton but from the Jenkins point of view, if Jenkins had to do something similar where it had to call a tecton custom resource or create a tecton sorry, where tecton had to create Jenkins job or like tecton had to trigger a Jenkins job. So for this, there is work going on in which the Jenkins tecton should be able to create a custom task which triggers a Jenkins job. So for this a custom task controller is being worked on, and you can see the link that is given in the slide over here, which where you can get like more information how that would work. So this is direct interoperability we are talking about in this case, but what about cases where you know, CI CD systems are like so disparate that you know you possibly cannot just call like in some different kind of world, you possibly cannot just do like client calls, and you would rather use like direct data streams or like events to make that happen. So, the first go at that was using cloud events. So cloud events are something that was already adopted in tecton directly. But now there is what going on in the in tecton for creating a new cloud events controller, which will use the continuous study really foundations CDF vocabulary, like the certain vocabulary which could be used across CI CD systems to kind of standard is what kind of events happen in CI CD systems, and you can check out sick events and see CDF or more information, but using the standard we can basically kind of, you know, say that okay upon upon this event in Jenkins, I want this thing to happen in tecton upon this event in tecton happen in Jenkins. So, for that, we started the GSO project for cloud events plugin, based on the cloud events controller that was existing in tecton at the time, and slowly we are moving towards, you know, getting a feel of what interoperability looks like There is also a POC which is being worked on in the sick events in CDF. So, which kind of which shows the interoperability between tecton and captain, but I hope in time we'll be able to do that with Jenkins and tecton so So, I'll talk a little bit more about the tecton client plugin itself. So it's Yeah, so it's the tecton client plugin here. So, based on what's given on the repo itself the tecton client plugin kind of allows us to call tecton directly and tecton is basically based on the repo tecton provides the ability to create a key test style resources for declaring CI CD style pipelines. So you can use a Kubernetes CRDs to create pipelines and Kubernetes. And this is very Kubernetes based and What so we recently have released version one for tecton and we and recently James track and also posted a blog post for using Jenkins with tecton and Jenkins X. So like slides are sorry to disrupt slides are shifting around like Sorry. Am I still connected. Sorry. Yes, you are. We're back to the outreach advocacy. Excuse us. No worries. Sorry about that. Yeah, I was trying to find the chat because we're going Over time for something like 10 to 15 minutes. And yeah, I messed up the slides a bit. Yeah, let's try to accelerate. Okay, that's okay. Okay, so let me continue. Um, so we recently released we one for tecton client plugin and you can go check it out and start playing around with it. But there's some interesting stuff we are working on next for the plugin itself. So we are working on some tecton cloud configurations with which you could use tecton from multiple communities instances and deploy pipelines from multiple on multiple communities instances from Jenkins. So that's something interesting we are working on currently, and we are planning on working on pipeline DSL with which writing tecton pipeline so it should be easier in Jenkins, as well as, and it should be a little more familiar to Jenkins users as well to like use tecton in that way and not have to deal with a lot of them. And the other stuff we are working on is support files with multiple types that that means currently when you give a file in creation for in the plugin, the file cannot contain multiple types it only has one, it only can have like one resource and not multiple resources. And then country we have catalog integration using Jenkins X, which is really cool. Tecton catalog is basically a catalog of different tasks and different tasks that you can reuse and you won't have to write your own tasks. So it's basically tasks which have been embedded and created by the tecton community and you know they keep improving it from time to time and keep releasing new version of the catalog. So it's a very reliable source to kind of start using tasks. So we would like to have better catalog integration so like the users will not have to figure out where to get the task from like they should just have it in their hands in Jenkins. So and the last thing is cloud events configuration. So this would be quite in the future but as the cloud events plugin grows and we are able to figure out you know how to create things and everything and we should just be able to map the image listeners from Tecton directly to Jenkins, Syncs and you know kind of figure that out easily without having to do a lot of back and forth. So, yeah, that's about it for Tecton. Thank you for listening. I'll now pass the course to Shruti. Shruti, run. Okay, I suggest that we move forward and then we can return back to that or we will have a breakout session if needed. Okay, Mark, what are you doing on the documentation scene? Yes, please. So very briefly, thanks very much to those who've been involved in improving documentation by adding embedded search thanks to the Sheikot Africa contributon for their work on pipeline help and syntax and snippet generator and thanks to D Raj for becoming the new maintainer of the weekly changelog. Next slide. We're grateful for the plugin documentation as code specifically the contributions from Gavin and from Oleg, and for the embedded search. Next slide. And really want to thank those who are involved in Sheikot Africa including Zinaab and the five contributors from Africa, Oninye, Sharon, Esther, Cynthia and Lucy, and our mentors Kristen and Meg and Angelique and Oleg thanks very very much. We're so grateful for what you did. Next slide. Thank you. And we'll be doing more of that. And that's really it for me, Oleg, thanks a bunch. Okay, thank you. Yeah, I'll also do a very accelerated update for the focus and outreach. So, yeah, as I said, we do a lot of social media management, including Twitter, LinkedIn, YouTube, Reddit, please subscribe to any channel. We do a lot of automation and they're looking for contributors. So if you're writing great content, please do so. And yeah, I always have this course. So this course for us is not just a play discussions, it's also a lot of special opportunities for Seek like doing announcements, doing crazy blog posts, showcasing achievements like I presented today introducing contributors or thank contributors. I will do some of the networks, but we intend to use this course a lot more. We also plan to keep working on teach programs. So we had CDCon this week, there will be the Oxford in September, maybe there will be other major conferences we participate. It's still yet to be seen. We also participate in our teach programs. So Sheikot Africa has just finished. We have ongoing Google Summer of Code, October fest is in October, as always, and we participate. And we plan to run one or two LFX mentorship programs in autumn, basically self-funded to address topics which we can address through existing platforms. And also thanks a lot to education, at least we have North Damien. They've been working on this topic and also Wadiq who contributed to security investigation and analysis with X-Mercel students. It's also much appreciated and we, you know, like people contribute to this area as well. So just a shout out to Sheikot Africa contributors. Basically, Mark has already said a few words, thanks a lot. And I want to highlight that it's not just about code, we also invested a lot in documentation. For example, Zainab was mentee in Google's Season of Dogs last year. Unfortunately, we haven't been accepted this year, but we will apply again and be a force for still a great experience and provide a lot of opportunities to Sheikot Africa so that we could collaborate between our communities. The terminology cleanup, there is some major updates. So we defined subterms for Jenkins controllers, so we unlocked the most of contributions. There are more than 50 pull requests that means over three months and there are more upcoming from the IC and the bug tracker and in the conversations. And there is Jeff by Angelic Jarth about the inclusion for terminology guidance and continuous updates so that we actually make a formal standard within our community. And there's many other projects we are looking for contributors. There is a link here which is pointing again to discourse which provides all the information how you contribute and what types of contributions we are currently looking for. And thanks a lot to everyone who wants to contribute. For Google Summer of Code that is here we have five projects in the standard framework, we do a lot of office hours, we do project updates, hopefully you'll have some books about JSOC this year. And thanks a lot to five students who participate, so Shruti, Aditya, Harshita, Adihara and Pulkit, they work on different areas in the Jenkins community on important topics. They are mostly called native system models, infrastructure, application plugins, and we much appreciate that. So, is Shruti back online? Shruti and I were just discussing, Oleg, and she was agreeable to hold the, her discussion on cloud events inside the breakout session that's going to cloud native. So let's put it to breakout. And yeah, what I wanted to say again that it's a great time to contribute. So there is a lot of opportunities for contributing. If you're a newcomer, please join Mark's session for newcomer contributor. And if you're an experienced contributor, we will start the end user panel, maybe with a five minutes break. And then at the end of the hour, we will start breakout sessions. I intend to start them on time. So we'll have plug-in and supply quality, technology, observability, and telemetry, and then we'll have most sessions continue. And thanks a lot to everyone who joined the kickoff. We apologize for issues with the webinar link and we will definitely run a retrospective enough to make our events better. And also, you have a lot of opportunities to share your feedback. I've already posted the link to the feedback form. Please use that. Also, there is discussed discussion where you can find or just use our slack and put your comments there. And that's it. So thanks a lot. So we can start, but actually we are going to have a five minutes break before the next session. So we start at 20 minutes. At 50 if you're in India. And yeah, thanks a lot to everyone. Let's keep working together. And I will share the presentation, the feedback form link, because many of you will make a lot of feedback to share. Thank you, Oleg. And I've had to revise the Zoom link for the newcomer session. So in the five minute break, those of you who would like to join the newcomer session, if you could just send me a chat message, I'll post a link to that newcomer session in the chat messages as well. That way you've, it's accessible to you. Yes, and for breakout sessions, we will continue here. So thank you. Yeah, so then see you in five minutes. See you in five minutes. Thanks everyone. Yeah, I'll stop the recording because I'll step the new recording once we're back.