Jenkins Core Maintenance, 25 Jun 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Online Meetup: New Jenkins Features in 2.235.1

Description

Jenkins 2.235.1 is the most recent Jenkins long term support release. We will introduce the new features in 2.235.1 and review how you can best use them: Plugin manager UX improvements, User interface refinement, new System read and Manage permissions. We will also talk about what's next in the Jenkins core.

Presenters: Mark Waite, Tim Jacomb, Mike Cirioli, Oleg Nenashev. Date: June 25, 2020

References:

* Slides: https://bit.ly/new-in-jenkins-2-235
* Jenkins 2.235.1 changelog: https://www.jenkins.io/changelog-stable/#v2.235.1
* Jenkins 2.235.1 upgrade guide: https://www.jenkins.io/doc/upgrade-guide/2.235/#upgrading-to-jenkins-lts-2-235-1

A

So, really all right thanks everyone. This is the Jenkins LTS webinar for what's new in Jenkins 230 5.1, we're glad that you're joining us and delighted to be talking about things that are arriving or have arrived in Jenkins to tout 235 thanks very much for being with us. This is being recorded. This is a Jenkins online Meetup. Our online meetups are community driven meetups. It can be any topic about Jenkins case studies, success stories, other things of interest. We also host developer meetups.

A

You can find those on meetup calm under Jenkins online Meetup, and we are actively looking for speakers to present to the Jenkins online meetups we'd love to have your topics. There's a process that's described there. We invite you to submit your topic proposals and we'll welcome you to come present for us and share with others in the community during this particular session, we'd like to do questions and answers using the zoom question-and-answer facility that allows us to see the questions and allow some of the team hosting the webinar to help us answer the questions.

A

It also gives us a chance to help you interactively here in the session after the meetup. We encourage you to subscribe to the Jenkins user and developer mailing lists, in particular they're great places to help each other there's also the Jenkins user experience special interest group that has a Gitter chat where you can join in conversations about Jenkins user experience at the conclusion of this we'd invite you to complete the feedback form.

A

We love to hear feedback on how we can improve, make better or strengthen the messages were bringing to these webinars and to Jenkins users in the Jenkins community. Now, by way of reminder, the Jenkins project and all interactions within the Jenkins project are governed by the Jenkins code of conduct we like to treat each other well, we like to treat one another with respect and with dignity, and we rely on you to do the same.

A

This is a look at Jenkins LTS, we're going to look at new features and what things are described there you'll see the URL at the bottom of your screen that points you to the Jenkins changelog. It describes the current Jenkins release and past Jenkins releases and will highlight for you some of the features and capabilities that are being added in new jinkins releases. In particular, today we're going to talk about improvements to the Jenkins plugin manager, additional refinements to the Jenkins user interface.

A

We're delighted to have Tim Giacomin with us to talk to system, read permission enhancements and ways that will help you get more value out of configuration as code and configuring. Your system is code, we're also looking forward to Mike C, really.

A

Talking to us we'll look forward to his his presentation on overall manage and then we'll have oleg natasha share with us on what's new in jenkins core. What's next, what's thinking, it's all bits, I'm! Sorry, thank you all I! Guess you're right! All things correct! It's what's next in jenkins, core, not what's new we're gonna do what's new in the first four items on this agenda. Thank you like that's. Fine, all right. So first first topic is the experience for users and administrators dealing with the plug-in manager. So we've enhanced the administration facilities.

A

We've improved the notifications first keyword. We recommend that you search rather than scroll through the Jenkins plugin manager. So in the top right hand, corner of this screen shot. You see Jenkins to-220 to the previous version and what it shows is a long list of Jenkins plugins that are presented to the user when they look at the available tab. So here's my real demo. If you look at this scroll bar here, if I take away the search yet scroll bar is huge.

A

There are thousand plus plugins in that list and it's almost unbearable to work with that. That's the old way of doing things. Now, if I look at the new way, it just presents me a field and I'm ready to search so now it gets even better than this. So so the presentation initially no longer shows me the daunting list of a thousand plugins. It instead invites me to search so search. Don't scroll is the first idea and then it gets better from better from there.

A

So, let's go to the next, which is that it's got a better search inside the search facility. So in the old way here here you see the old way. If I search for gift, ok gets a pretty important thing in the Jenkins infrastructure. I search forget, and it shows me the first thing in the list is github authentication, gitlab authentication get colony. Those are not the first things, I need when I'm thinking about how to solve how to meet the needs of users with git in the new way of doing things.

A

If I search forget, it shows me the most popular plugins, first and notice that it gives me hints with tagging and labels. It also gives me hints, on version numbers and release, dates all sorts of waste and make my experience better as a Jenkins administrator, so sorted by popularity, and we have better search now when I say better search. It also means things like.

A

Let's, let's look at this one, for instance, if I wanted to do something with get the multi branch, I search for get multi branch in the old user interface. Oh, it didn't find anything. Why not I know there's something about get multi branch? Well, the new search actually does do get multi branch and there it is there's the github branch source here are more changes that could be involved in multi branch projects. So new search is just better now.

A

Multi word search, yep, that's great as well. We love it now. In addition, there are now hints built into the plug-in manager when looking at it. That show me labels and indicators if there's a security fix involved in something I'm doing it gives me a reminder about the plug-in release date. So I can hint oh wow. This plug-in was released just very recently.

A

I may need to think more carefully about it or oh, this plug-in was last release nine years ago should I had it should I be using that plug-in release dates can help you decide which plugins you should use and which plugins you should not. It also has hints on plugins that are up for adoption. So if a plug-in maintainer has decided to step away from the plugin, they can mark it for adoption, and you now, as an administrator, will get to see. Oh, this plug-in is up for adoption.

A

It's a good way for you to think more clearly and more cleanly about which plugins should you use and which plugins you might you say, I'm, not ready to use that one.

A

So the updates also are easier on you, so I'm going to show updates in the old world. Here's updates alright. My Jenkins here has several plugins that need to be updated and it tells me hey here they are and here's their version number what's installed and what I'll get well the new Jenkins user, the nutrient tank ins plugins, my plug-in manager provides not just what's the new version, but when was it released?

A

What version is currently installed and I get the benefit of all the hints here of labels telling me which things are involved, which tags are associated with these capabilities. So oh I want to look at only the plugins being updated with your API plugins there they are. It was that easy clicking a label gives me access to all the things that match the label. In that view,.

A

All sorts of new hints and new capabilities to make your experience better and simpler as you work with the plug-in manager.

A

So now I did see a a question here in the in the online that asks. Is there a plan to hide plug-in versions that aren't compatible with running Jenkins version? Will plug-in versions which require a newer version of Jenkins by default, won't be displayed as available anyway? We actually had a good question recently on that, where someone wanted to use the dark themes plug-in and their desire to use the dark themes plug-in, they were running a version that didn't yet wasn't yet supported by dark themes, so they had to upgrade to a newer Jenkins version.

A

B

Just taught more information to this answer: Jenkins update Center. So if you use updates and are provided by the Jenkins project, it provides details for weekly releases and for five recent ALCS releases so for weekly releases you will always see the recent plugins called cs3 mises. You will see only plug-ins and plug-in versions which are comfortable with your JS baseline unless your LCS baseline is told if you use custom, update centers for them. It's up to an administrator of this custom update center to properly expose plug-in information.

B

They provide tools for that, but ultimately, it's up to maintenance to properly define plug-in sets. Then.

A

Thank you Thanks, so like so now, in addition to plug-in management experience improvements, there are also improvements in the overall user experience for Jenkins users, the Jenkins user experience special interest group is making steady and very interesting progress on improving the Jenkins user experience. As one item auto refresh used to be available in Jenkins as a way to cause the browser to force a complete reload of that page. That complete reload of the page tends to be a heavyweight operation and it could cause performance problems.

A

We've taken away that enable auto refresh it was causing usability problems for users who they would have in the Auto refresh, enabled and open a forum and be dismayed when the form would be refreshed away.

A

If you need something like auto refresh, that usually is an indicator that we need to find a way to automatically update the content inside the Jenkins page that you're viewing. Rather than requiring that you refresh the page and in the short term, you could use a browser extension that will do the auto reload for you.

A

Now, in addition, Jenkins to 235 has added tiled tiled segments into the system configuration to manage Jenkins page so where, as you see on the top right here, configure system configure global security, we're all a long linear list of items it's now been tiled and the tiling adapts to the width of your screen, narrow screens, may get two columns wide screens, make it four or more, it's an a much easier way to view and find those capabilities and gives you a simpler way to navigate when you're, using the manage Jenkins page.

A

In addition, the the core layout of Jenkins has been improved by using system fonts more frequently. Now this particular screen shot may be a little difficult to see the difference. It's a somewhat subtle difference. In the top right hand, side things are a little closer together and the fonts aren't quite as crisp the bottom left. What you see is Jenkins 2, dot 235 with a little more spacing and a little clearer font.

A

Because of this, this change to use system fonts rather than the fonts that we were using previously we're grateful to the UX cig, they're, making great progress on the topic and looking forward to letting you know more about it during our what's next segment, that'll come up at the end of our webinar ad next piece, Tim jackal and read-only Jenkins configuration Tim I'm going to go ahead and stop. Would you want me to hold the slides here or what would you prefer.

C

It's been some if you want me to show a quick example or I would.

A

Love to have an example included if you're, if you're willing to do the example, you tell me when you would like it and I'll give you control yep.

C

Yeah I'll tell you when, when I'm ready, if you just get her out onto the next slide,.

C

So read-only Jenkins has been a topic for quite a long time when Jenkins I think the first issue about it was created about six years ago.

C

The driver for me for introducing this was to complete the story for configuration, discourage users so that users of that plug-in, wouldn't would be able to still view all the system configuration and help contribute to it without being tempted to make changes in the UI. So there's been a new commission introduced the overall system read which allows you to now have access to the system configuration but no access to change it most of the so everything everything they seemed interested in. Adding score is available.

C

You can see the Manas managed chicken's page the tool, configuration plugins configurations code to know everything's the year, but if there's something that you do want that isn't currently available because a epoch that you can create issues in as part of this. So a long time ago, about ten years ago now the extended read Commission was created and as part of this, we updated that to use some of the new engine that was built to make the pages. Actually, look read-only to me to improve the user experience and we found an agent extended.

C

Brief question was created a few years ago as well, and we fixed it up to actually work properly and so now you can also see agent configuration and cloud configuration if you have the right permissions to so I'll. Just give a quick demo on one of the difference project see is it's running there has this? Has this going?

C

Should I share my screen?

C

So this is the Jenkins project, infra CI, I I just have the I just have read access to this. So if we see here this is just me with read and mana and system read I go here. I can see the build executors to configuration. There's not much there. What's interesting is that I can go to the manage tinker's page I can see how it's been configured. I can go the configurations code and I can view the configuration or download it and I can also go to the configure system page. So that allows you to.

C

Can they will your users to see how it's been configured and then they can suggest changes to it via the code and even if you don't want it to at least they know how its configured? So it's it's giving more information to the to users.

C

So you see here- and the other thing is that it looks read-only so as much as possible. We've removed buttons, we've changed it to change the behavior. To show that you can't change them. These checkboxes are disabled inputs have been removed in general, we're possible they've been disabled, not everything, so everything this controlled and Jenkins call has been changed, but a lot of functionality and plugins, and it depends on whether they use the core components or whether they're doing or anything after doing their own thing.

C

There'll be some work needed to update the plugin, but in general it works very well and I. Think it's quite cool using it. If you just go back to the presentation mark sure.

A

I've gotta find my share button yep.

C

So this was released as an initial beta in 2.32 LCS. It was very little functionality. I think you could just see the managed system page in the system info between 2002 and 2003 5. We can please that's most pretty much all the planned work, especially in jinglun's core we're still UX improvements and some plugins that need support, but the core work is all being completed and to use it, we just need to install the extended, read commercial plugin, and then it will automatically activate us, and then you need to give you users the permissions.

C

So in one of your permission, plug-in new use of its matrix or for controls just need to add the required Commission's. The system rate extended, read and well Asia, Nixon, agreed and job extent agreed. I. Think that's all from me. Unless anyone else wants to add anything.

A

So so that this really is focused in on letting me define my configuration as code still show to my users what what they the settings are, so they are not kept in the dark about the settings are not hidden from them, but then the idea is, they will submit pull requests to my git repository that describes my my configuration in the llamó file. That's that's.

C

Either there or they know who to talk to, they know they know how its configured and then they can talk to the person who is able to, and they can also see who has access to do it as well. So the security configuration is there and you can see and they can see who has access to do what so they did. They know who to talk to as well as another knesset.

A

Excellent thanks very much Tim. Thank you. Thank you.

A

Alright I think we're ready to go on to our next topic. Then overall manage permission so system read: permission was one enhancement in to 235 overall manage is another Mike C really is going to introduce this one to us. Mike go ahead thanks. Mark.

D

So kind of in a similar motivation to to Tim's overall, read or system, read right now in junior before or 2.2 to you. Pretty much was an all-or-nothing proposition in terms of administering or allowing someone to administer your jinkins instance. You can give them overall administer or not, and they can do everything or nothing, so that doesn't really lend itself well to being able to delegate some things that probably matter more to day-to-day developers and users of a Jing consistence, while still being sure that things like security, isn't being compromised.

D

You know dangerous, plugins, aren't being installed or having you know allowing you some control over over the important parts, and so that was a motivation for introducing the new permission of overall manage it's listed, it it's less than administer, but it still lets you manage a number of things right now. Most of it is the working core has been done since 2.2 to 2.

D

There are a number of plugins that have been updated and and released or in the process of working their way through being released, and they take advantage of this.

D

Doesn't say so right now you can actually like go to the the next slide or actually I can just I have a little demo, it's sometimes as low easier just to show what the difference is. Yeah.

A

I, like demos demonstration, is great if you're willing to just share your screen and show us your demo. That would be great.

D

Guess see: Firefox we do I lost, I lost my view of what the screen is so right now, I've got like you, have a browser with three different users logged in this first one. This is the normal I'm, a full Jenkins administered review, and you can see you see everything you would expect to see here now in.

D

If you go into a global security you're using matrix matrix off you can see, there is a new permission here in the overall category called manage, and so, if you grant a user or group that permission along with the overall read permission that will allow them to first like actually see the manage Jenkins link here on the left hand map, because normally for a non administrator user, you don't have access to add. So this link isn't shown.

D

But you can see here, there is a subset of things compared to the the full I can administer everything that are available to your user and then within configure system. You can actually still you can Mac. You can manage plug-in configuration as they show up your X or really anywhere within the UI.

D

So this is not super exciting I, don't think many people will want to go in and change the system message like every day and the real power for this will call them as more and more plugins start to adopt this new permission.

D

It's relatively simple: to do you basically just change permission checks from currently being Jenkins administer to Jenkins manage and your plug-in, where you feel it's appropriate and safe. You can see here as a as a managed user I don't have access to computer with system security, for instance. So there's no worry that if I delegated some administration to a user that they're gonna go in and you know open everything up to anybody who wants to do something malicious.

D

Another interesting thing is that this permission also works well with the overall. The system read permission, and so this is a third user that I have granted both the overall manage and system read to you can see for this user. Now they can see things that you would be able to see as a user with two system read permissions, so I can see the security, but I can't change it, and even within configure system, for instance, I now can see quite a bit more, but I still am only able to make changes.

D

You know to the parts that actually had been granted the ability to be managed through the overall manage permission and you this is an opt-in similar to system read. There is a plug-in called your naval overall manage permission that's available by default. You just simply install that plug-in and you will see the new permissions available if you're, using a simple matrix off.

D

That's pretty much what.

A

I have to show thanks, Mike thanks very much so so for me that configure global security thing is. That is the the major one. It's it's that I can't I can delegate permissions to do many of the management tasks without allowing them to alter the security definition. Network I saw a shutdown was another one that there were some other things. In addition, it's not just security.

D

So you can, as a managers where you can share Jing consensus instance down, but that says of the sort of the guiding principle was in general. Allow a user would manage to do something as long as that thing doesn't have to lead to a potential escalation or privileges so run. Scripts is right out the window, anything with configuring, the security.

D

But beyond that, we don't right now, there's not a more fine-grained way to manage permissions and Jenkins, where I can pick and choose very specifically what a user or a group is allowed to do.

A

Thank you thanks very much much appreciated so I think I think concluded the the piece that you wanted. Overall Mataji. Okay, if I take back screen sharing I am all.

B

Right thanks a lot for the presentation. Mike. If you have any questions to presenters, please use ozone Connie and represent new features. Many of them are in preview and any feedback from you will be appreciated because it will help us and program.

B

Any adoption, any additional insights would be appreciated thanks so like.

A

Yes, absolutely so, for reference, you can refer to the Jenkins changelog to see more about. What's in Jenkins too, that 235 upgrade guidelines are also provided. These are both common features that we do for each new LTS. We invite you to read them refer to them, use them to your benefit.

A

Thanks very much for your interest in Jenkins to 235. You can find these particular slides at that URL, we'll also post a link to those slides into the meet up afterwards. We've now got what's next and what's coming so Oleg, would you like to take over? Do you want me to give you screen control or legs, or do managers home that.

B

Would rather prefer her toes clinch an okay, great.

B

Okay, there's my screen: yes, okay, let's talk about what's going on in the Jenkins project and what we're going to deliver in the next LTS baselines, hopefully in September s and teachers might take longer, but anyway we would like to share some insights of what what's happening in the project.

B

One important thing that create parents are working on the public changes roadmap and, if you interested to know more about what's in the project, you can refer to Jenkins io / project, / roadmap, and here you can find a lot of stories which are currently in preview or in ongoing development. So today we have followed. We presented some stories, for example, manage permissions system with admissions. You can find them here and yeah. There is a lot more in progress.

B

I will just share some insights about stories which are strictly related to the Jenkins core or to infrastructure connected to the junkies core. So it's just a subset of what to do. One important topic is a dark thing and it may be. Youth team would like to speak a bit about it.

C

Yeah sure so the dark theme is something else introduced in the UI UX hackathon, with support for CSS variables to Jenkins, to enable easier theming and to make it less likely to break which its core changes. So now it's using a CSS API rather than targeting individual marker, so it should be a lot safer.

C

It's been released as a plugin that you can just install, there's, also instructions and how I configure it was simple theme plugin. If you want to do that, instead, it requires at least two dot 3039. So the weekly version is currently the latest will be.

C

The best is almost every weekly there's been changes for dark theme, so the most recent will have the best experience yeah, it's a plugin how to do Jenkins organization, and you can raise a schism there I think if you find any any compatibility issues or improvements that you think could be made, but it's going quite well, I think it's quite usable and I'm using it every day and others are as well.

B

I still need to upgrade my instances to the recent Jenkins weekly, but they confirm that it looks pretty awesome and good support for many major features, including console logs pipeline stage view and many other components. So now the team looks really well.

B

If you are using Jenga speaker, you can already able a bit and one notable change which Tim didn't mention that this dark theme so say music, another plug-in on the hood. There is theme manager plug-in, so it allows not only to manage themes on a global level like you can do with simple things like you know, but you can also manage themes as a user if you're urging this administrative allows. So it's also an interesting feature to explore and it's available in the current weekly releases and it should be become available in LCS in September.

B

B

So it looks pretty well, there are some open topics and compatibility issues. So if you re related, please report any issues you hit. So, for example, here you can see that there are some reports from contributors who already tried it out and discovered some issues here and there. For example, github uses, dark icon.

C

B

You can see it how the logo, for example, on the label screen or there are some other reports, for example, about statistics- is too bright, so it Lisi peaches like that. This report that, because yet you're in here you're at first nobody applied a lot of patches and we keep working on that. So any feedback from our doctors would be appreciated.

B

A

Impressed with the ways that this can be evaluated and in the dark theme, plugin documentation, you had provided ways that people can evaluate very rapidly right. There are all sorts of suggestions of how you do this and do this to help with the evaluation.

A

That's great yep.

C

Yeah yeah and you can also there's two ones- two modes and dark name as well. You can either force it for everyone or based on system settings and then also users can opt in or out as well. So it's quite confirmed of rigor will we run it with the operating system settings so only the people with with dark with dark mode enable that they are always little get it and they can also opt out if they don't want to school. This is some compatibility issue.

C

That means they don't want to use it, but so far feedback from users that I support they're all using it I don't have any ways turned off.

B

C

I should check that.

B

But anyway, it's a great improvement and wait till we can add more things to theme manager, for example, new to theme and other popular themes, so they could be edited using the same engine and was a lot of groundwork. So I would like to thank all the contributors. We actually have a list of country here, but I think that we need to update this list amid but yeah. This is a list up for those who contributed during the ui/ux like first and now, I suppose twice more contributors.

B

So even more so thanks to everybody who helped push this project forward, mm-hmm.

B

Anything else I see the. There is quite a number of questions, but I'm not sure what I think is related to the dark theme. It.

A

I didn't see any specific to dark field request. Oh yeah.

B

You'll handle the rest later. Another important change we are working on is increment of configuration joy. So if you work with cotton, jigs integrations. You know that a they really long. At the same time, we table they're out, so you can easily configure Jenkins on narrow strings. If you try opening it on mobile, it's globe even worse, it's hard to maybe a bit throw multi-level configurations and, as a user experience, special interest dope is working on many improvement taxes, ability of the Jenkins project.

B

It's one of other projects on our road month, yeah I'll, keep showing it today. I find it, of course. Ok. So yeah one of the projects. He is actually improving accessibility and we need significant progress there during the hot rest and later and duration. Your tables is one of the stage over the quest. So it's not available imaging is weekly now, but hopefully we will be able to make available soon. I. Did they improve navigation a lot? So if you're interested in that take a look at the ticket I linked.

C

B

The testing guidelines available the right-hand side, the big ticket- that is also big, start demo. You can just run in docker or you can build it on your own. Actually, it would be a great help for us, because this change my input other plug-in configurations, but still we want to because great improves figuration pages, and it's not just the system configuration page, it's also job configurations and for other forms, like let's say, a build parameters, all of them. My experience for this change, I've.

A

Been I've been I was initially skeptical. Actually of this change and I've fallen in love with what it does for me, it makes things much more usable from the user interface I'm, I'm less frequently having to scroll horizontally left to right, even on my wide monitor because of this kind of change. So thanks very much to the people who are willing to launch this and for all the work that's gone in thus far to get there yeah. So.

B

The most of credits go to Josh, sort of Felix and him, and to many other contributors who report issues because it's a wide change, so it requires a lot of testing to move it forward.

B

Ok, other important thing, which is in common and jenkins core, is improvement of external fingerprint storage. We have some lutheran who is a g-shot summer, 20 student, so he is working on providing a new back-end for fingerprints. College which are not familiar is what that means. Do they basically a lot tracing usage of various items in jenkins, most haunted, artifacts credentials or docket images or continuous when you develop when you use to them, so you can easily see the entire delivery pipeline for a particular artifact or see where it was used in other jobs.

B

If you use various job chains, and currently this engine uses filesystem storage on jinkers home. So basically you have to manage backups on your own. Also, you don't have so much opportunities to query the date and to process that so as a part of the project, we want to move it as external storage, as many other items like clocks, configurations, etc, and it also allows them to publish availability and traceability of Jenkins in the future. We also want to support multi master tracing pop artifacts or images.

B

So if you use multiple Jenkins service in your delivery pipelines, you will also be able to use these two in order to trace usages of these octopods. So right now, this feature is in a premium code, changes I integrated. That is a plug-in with a reference implementation for radius and it shouldn't be landed. That is the before this meeting we discuss on the release of this plug-in and the immediate it's released. So if you want to try it out, please do so and next week we will have a more detailed demo bought this project.

B

Okay. So what's next, also working on terminology cleanup, so in 2016 we renamed slaves to agents, but still there is a lot of leftover scheme there. So we are working on cleaning them up, including Webbie already from occasional optimizations. We also do planning for jinkies call it a cleanup and again we invite contributors to participate in this effort, because there is a lot of changes here and there, and sometimes you don't even need anything except get half of web interface in order to deliver a change.

B

So, if you're looking for items where you can contribute, it could be one of the topics and again you can just open this change and see what's inside. So here, for example, we open this issue, and here you can see, become a friendly issues, so just run a query and basically half of the items in this query can be easily fixed without any experience of generous contributions. For example, a lot of bad items like that can be easily cleaned up before that.

B

The lot of examples just in the beginning, which were not involving API, is but we always pick inter them up so a lot more to do. We also discuss other terminologies so, for example, the governance meeting cost. If we decided that we want to rename master, we will be launching public boat about a new name. So if you interested that is the develop admin interest rate where you can find more details, and also for Whitely- is reckless and potentially other technology. We are working on, suggest and replacements and yeah.

B

We are well aware about this topic and we would like to change a bit state monopoly in the future.

B

Another important change in the project is the weight distributions. If you use drink is weekly, you have already seen a new windows installer created by alec, so it doesn't put bundled judicata improvements for a user management and many Advanced Options. We plan to make this store available in the LCS releases, soon, hopefully free in the coming months. We also work on docket images. We contemplate all the images to adopt openly key.

B

Most of them are based on open, GD key, and we want to extend support for platforms, so we want to provide official images, form 64 for IBM I, see 90 PowerPC g4 was Java 8 and Java 11, and it will help Jenkins on more platforms. We also want to change the signing keys so most likely in the next 30 leases.

B

You don't need to modify key CPUs, for example, distributions for, like just rpm or up to you, willing it to a big keys, and once we do that, we go see guidelines how to do the command paper words. Another important thing in changes infrastructure, because when you run Jenkins you actually use infrastructure and the right. Now there is a lot of contributions here and there, which we improve user experience, one of the notable changes phase, for example, on the plug inside.

B

So if you go to the plugins drink, say: oh, you can find a bit that already some changes on the flag inside so, for example, we're going to navigate here. You can see that now you can find history of releases or list of for deported dishes right and said the web interface. There are still patches to be done, for example, support for publishers or support for change locally files, but for many plugins you can already get these benefits and if you use plug-in manager, Marc demonstrate you can basically get to this web interface.

B

In one click now, so, if your investigate or changed and plugins etc, you can quickly get this data, and hopefully we will make it available to merging, is plug-in as soon as well.

B

Another important change, descritization and search for plugins. So you can see that plugins have labels and yeah. Maybe epi plugin is not that informative, but there are other labels, for example, if you're interested in plug-ins for kubernetes, you can just search for kubernetes there and you can find some plugins.

B

You can also find keyboards on the left so right now there is a lot of improvements to be done there, but we started doing investment in order to provide better search and to provide better categorizations of a plugin by default and the ones that done on the plug-in side will be also moving bit to the Jenkins core so that it improves user experience here as well delay. The change to the plug-in site is update, Center improvements because yeah plug-in site, as well as flag in manage and Jenkins core.

B

They receive data from update centers and they make improvements there. For example, Daniel Beck has created, but flexible update center. So now you cannot actually you can access available plugins for a number of recent weekly and LCS releases. So when I was uncertain, previous question I was a exactly correct so now for recent week is you can also get a list of compatible plugins and the results among metadata plant to become available for plug-in manager for plug-in side example, links to change logs and other such improvements TM there.

B

So we will keep on program pad another change which is important to Jenkins. Users is but a murderer infrastructure. So we, if you use Jenkins now you may be told it he be issues with plug-in not being available. It's not a big deal in Jake this web interface because you can just read download. It becomes a bigger problem. For example, if you do, the docker image is plug-in 60, but unavailability of a single plug-in. If it fills a facing server. All the trace basically fills the bill.

B

So it's one of the symptoms of current mirrored infrastructure. Every context pundit, we plan to add more mirrors in order to speed up downloads and make the maintainer and search more stable, so it just adds up and hopefully will happen soon.

B

Another thing which is rather focused on my junk is developers we're working a new release, automation, it's already available for weekly releases, so we should weekly releases from infrastructure sleek. You have overhead top it, for example, keys for Debian packages etc. But the same change is coming for Algiers, so that for OTS we will be using infrastructure. We will be able to model I believe without delays. And again this is the change we are gonna like to have by the next LCS baseline, so stay tuned.

B

There is a lot of changes here and there and, if you're interested this is a great opportunity contribute you can test the existing stories like tribulation cables, the deeps integration or read only changes configuration you can also contribute to documentation to newcomers and the issues you address and, of course, if you want to share your story to present, you.

B

So here this is just our blending for the information, for example. If you want to call so, if you want to improve pigmentation, you just go there and you can find references, including information for newcomers, different queries where you can find issues you could work on and yeah jenkees project is driven by contributors and we invite anyone to join and to improve the project together, and actually that's it from me. So thanks for your time, I hope it provides insights of what's going on. The game is just a slice. It's just what I gently score.

B

There is a lot of other stories and plugins like my client, scripts security and other important changes. So you can refer to this roadmap. Another tool find a full list of major initiatives happening to the project, not a full list of all changes, but at least a major initiative. We were able to watch here.

B

Ok, that's it from me. We get any questions.

A

Much yes exactly! Thank you. There are some questions that had arrived. One was sort of peripheral but I like the question and I think we should hoist it. How long is support for LPS and what is the lifecycle of long-term support releases.

B

Okay, the answer, so, if you go to the Jenkins download page, actually we have a special page, a gentle download, the LCS. If you go here, you can find more information about our release cycle, so yay OTS, it's a historical name, long-term support personally I call them stable releases. Every 12 weeks we select a new baseline me stabilize that this baseline made by poor patches and after that we do a three-bed part releases and after that we choose another GS baseline, stable boys line again with poor changes and make it available.

B

So how long the support falls years? Technically, it's three months at the moment, yeah there were a lot of discussions of in the community about having career LTS, let's say one year, but we do not do it at the moment. Yes,.

A

So the in this case, the the crucial piece of information for me is then that I need to I need to plant an upgrade about every three months to get the most recent Jenkins release that stable tested and then within that there will be roughly monthly releases. That will give me updates to that stable baseline energons.

B

Pelléas in practice, you also need to keep in mind security releases because yet stable releases, so they improve provide improvements. When we update to the baseline, when you are, did great dot version, you get some fixes, but sometimes these fixes are also good as if you are ability fixes, if you run Jenkins l88 environment.

B

Probably it's not a problem, but if you drink this instance faces public, you should really follow security updates, and here, although you can find our Advisory South curve- and you can see that the last security released for the Jenkins Corps was actually in March and before that it was in January. So if security is a concern, for instance, we subscribe to advisor race or tour SS feed and needs and pronouncements about releases, but this is a time when you really should run update.

B

Upgrading for other releases is basically your choice. You can use change log, of course, already present. Please link so here you can find all information about what changes in the releases and, for example, here if we released it one week ago, you can imagine what are the major bug fixes available when compared to previous versions? What are the major features? Basically, what we presented today and then you can make a decision whether you want arbitrate or not. So please refer to these change logs to make a decision if it's not a securities.

B

A

Now we had another question: this was I, think a little more peripheral, related or leg on further development of the subversion plugin. This may be a chance to talk about plug-in development in general. Okay, let's.

B

Spend a few minutes on it, so a subversion plugin yep. Let's take a look at the current state, so you can see here that this plug-in is up for adoption again it's a recent deployment and Jake is caught on a plugin side so now with the source of this fog and what it means. But basically this plug-in isn't actively maintained at the moment and we are looking for contributors.

B

There is a process describing how contribute how to step up and become a maintainer of a plug-in, and so, if you are interested in a new subversion version, basically the best way to get it is to contribute, in some cases, an exemption all the cases. For example, here five months there was a release: let's take a look. What was the histories? And this was a Security Adviser egg? So basically gently security team cut release because they were security vulnerability and they made a decision to use it because you can see that it still.

B

We users been used by hundreds of thousands users, because other plugins depend on that and we used to be bundled and the junk is called. Maybe it's because of lotion, maybe or something else I'm, not sure, but ok almost every instance has setup and yeah that's why it was released. But generally it's somebody. If you have a bug fix you would like to see. Then the best way is to just step out and offer help, because that's how Jencks communicate.

A

Rate well and and for me at least becoming a plug-in maintainer I initially had the flawed perception that I needed to be some sort of a brilliant expert on some topic, and rather what was needed in my case to become a plug-in maintained. It was willingness to work on it and willingness to learn and develop that there were plenty of people willing to offer me coaching to say no, that's not quite what you want to do.

A

You should do this, so so don't be shy about offering to help with plug-in maintenance, because you feel inadequate or you feel like you're, not the Guru of everything.

B

When I started developing and when getting my trust, plugins, actually I wasn't expecting my job in any means, and probably I'm, not an expert even now, but looking at my former code still if anyone is welcome to join and I, wouldn't expect major changes in the subversion plug-in unless there is an active maintainer there. It might be not an ideal question, but this is the best eight of our files in the project so yeah. Obviously, subversion is not a bit actually used as it used to be. Ten years ago, I mean maintaining a smooth on.

B

If somebody is interested, you're always welcome to join and.

A

Thank you now there's another question: maybe this is when we hoist a Tim on logging and for boat verbosity in configuration is code and I was assuming that the answer there is that hey we love to have bug reports, we love to have enhancement, requests and, if you're, finding something hard to read, submit a bug report or submit an enhancement request or submit a proposed change to the code Tim anything more. You want to add on that. No.

C

Yeah, just a physician is just a minute. There has been fixes down the path to improve it. The effects is done to add all the attributes and try and improve it. So they all the information you need is there, but if it's not readable, then just see in the examples and credit enhancement quest or a pull request and we'd love to improve it.

A

Thanks and then then there's one last question Oh. Actually, yes, thanks Oh, like you're a pointer to the feedback form for the meet-up. There's a question relative to a plain Jenkins container. That I think has been answered separately on the list. Did you want to address that at all oleg, or should we just look at the form yeah.

B

If I look at the whole fish, it's a way to get a plane jinx for without a Winston container, so Jenkins itself support yeah, sorry I'm stretching with the feedback form. But if, if you interest, please provide your feedback. So if you go to Jenkins I your download page here, you can find multiple options so with different distributions.

B

These distributions- yes, they come with Winston JK embedded, so we use jetty as embedded web container. But if you want to deploy Jenkins in other containers, for example, you know and liberty, in Apache, Tomcat or whatever you can just download a word package and deploy it in a proper environment. So it's possible you just download it. You configure your weapon use of this court file, similarly to any kinds of other war files, and you get it running in such case.

B

Yes, they will be Winston technically embedded in Jenkins, but it the web container won't be use in bed. You will be using external web container and you can also connect the identification and, in some cases, authorization to external web container so that you don't have to manage it on your own yep. Personally, I do not really recommend that, but if you want to do that, you totally can do it.

A

Now, back to the feedback form, so that was that was a crucial place where we would really like users, participants in these webinars to give us feedback and help us understand what things will help them more. What will help them less.

B

Yep and if you spend a few minutes to fill in on this form, it will be much appreciated later after they meet up yeah. Once we have a video, we will be sharing called the materials with participants and also a link to this feedback form, but now you can find it in the chat.

B

Ok, so basically we are running out of time. Are they any last-minute questions or any topics? Panelists would like to bring up.

A

Thanks very much to everyone for taking the time. Thank you very much for joining with us and thanks to our panelists Tim Oh like Mike. Thank you very much.

B

Thanks all okay I will.