🔴 What's New in Jenkins LTS 2.303.1

welcome to today's live stream about jenkins lts 2.303.1 uh normally we do these a little bit closer to the release date which was last wednesday august 25th but um my co-host mark decided to go into the woods with no internet how is that even possible it was it well actually the embarrassing thing is we did have internet i just ignored it so i was great because it was it was a cabin we were on the shores of a lake in northern utah and near the idaho border it was a lot of fun with internet but you ignored it and yeah i admitted i acted like i didn't have internet in large measure it was great if we have time at the end we may talk about that um but anyway lts and this wasn't just any other lts this was the next big lts right this was the big move from 289 to 303 in case people haven't watched this before my name is darren pope i'm i what am i one two three a developer advocate for cloudbees mark waite over here is the documentation officer for the jenkins project as well as being a clubby's employee and every four weeks it's stuck to that since we've been doing these every four weeks we come on and talk about the latest lts okay it's almost five weeks because of last week but give us a break come on mark was on vacation and what we try to do is get the community caught up just in case you haven't seen what the new release is about or some of the gotchas that might be occurring and you know today that's what we're going to talk about is and there were a lot in the it didn't seem very big and as we were preparing for this today it's like oh we need to remember to talk about this and this and this it was like oh there were actually a lot of things in here so if you haven't been with us live before if you're watching the replay you're going to want i'm going to want to watch this one to the end there's a lot of details if you're going to be installing or upgrading to the latest lts but just in case people don't understand how the jenkins lts process works mark you get to do your standard here's what the jenkins lts is so what is the lts process mark so the jenkins long-term support process creates a stable release every three months that's based on a selected baseline of one of the weekly releases that base release is selected then changes that might be necessary are back ported to it so that it is nice and stable and then that becomes the base that we use for the lts releases that now happen each month thereafter for the next two months so 2.303.1 releases now a month later dot two a month after that dot three and then the next month we choose i've chosen a new baseline we roll to the new baseline this gives our users a nice stable baseline and lets people who want the more aggressive weekly release to stay on weekly help us test it validate it see how things work lts users see changes major changes about every three months and but that's it right and sometimes you might see a point for you know on a rare not even as often as a blue moon you may see a dot five right and and in fact we're even considering a dot an out of order release right now and we'll talk about it during the session we can talk about locales in docker images and that that's a good topic for us okay well why don't we go ahead and get into the release notes because again we talked about them if we take a look at it real quick uh it's not that long i mean it looks like it's long uh and some of the line items are long but it's really compared to 277 or even 289 this is a fairly small release it is right and and it looks relatively straightforward and in many functional areas it is quite straightforward but there are some crucial what you might call infrastructure or environment kind of changes that are worth discussing here and people need to be aware that these environment or infra type changes are happening yep and in case people don't understand what these three weather icons mean the the sunny the cloudy and the rainy what what do these mean okay so that's a direct access to the jenkins rating system where a user of the jenkins long-term support release can tell us by very simple non-authenticated non-prompted answer hey what's your experience been with this release we have it for both lts and for weekly if they click the sunshine that's meant as a vote to say i had no issue if they click the cloud that says oh i had an issue and it will then pop up a dialogue that offers to have them tell us what is the bug idea of the problem you encountered that that then gets flagged in this community reported issues line that is right below it and that last column that rain falling out of the clouds that's i had to roll back and and that's that's a more serious condition that says something was so surprising in this release that the user said i have to fall back to the preceding version yep and usually on most of the dot twos dot threes or whatevers and just not the dot ones uh we don't have this section here but since this is a dot one let's talk about what this means yeah so so because it's a dot one we had to do some back port so a back port means we selected 2.303 as the baseline while after having made that selections there were three or four releases of jenkins weekly after that in those three or four jenkins weekly releases we discovered issues that we thought were important enough we should back port them to 303.1 and so each of these items that you see on the list here is a back port that's brought into 303.1 that was not in 303 so these are things that weekly throughout 303 did not include but we felt were so important we need to include them to assure that they're in 303.1 right and one of these items using java 11 and docker images instead of java 8 we're going to spend a lot more time talking about absolutely um let's get into the meat of this of the big changes since the latest lts sure a couple of big bugs that's what the big red means in case you don't understand what the coloring here means there's a legend right here at the very top of the page and i'll tell you the the larger the dot the bigger the thing is i guess let's say versus the smaller the dot it's like okay not as big as the bigger dot does that make sense it does and you're right you described it very well major items uh security fixes major bugs or major enhancements are a bigger dot so you look at them more likely yep so a couple of larger fixes at the top uh but then this third one that's here removing digester right so so jenkins for the longest time was bundling inside of at the apaches common digester 2 library and by bundling that library it allowed plugins and others to develop a dependency on that on that library however commons digester 2 last released over 10 years ago and is no longer maintained so commons digester 2 really is not a an especially safe choice of something to have inside something that's deployed like jenkins core is on 300 000 installations around the world so that the jenkins developers intentionally removed commons digester 2 from jenkins core they worked with plug-in maintainers to notify plug-in maintainers of plug-ins that depended on and assure that they would release those plug-ins or that the plug-ins were so old that they were no longer maintained and they would just have to users would have to find another solution for those plug-ins right and we'll talk a little bit more about commons as we get into the upgrade guide uh in a few moments but that was probably one of the big ones and then to me the next big one was recommendations for running on java 11. and we have one comment i do want to go and put up here and this this could be what you run into i had a problem installing java 11 on my windows agents but not on the linux ones that it doesn't sound too surprising to me but mitch if you're still there what flavor of the jdk were you trying to install on windows was it adopt open jdk was it a different one because that that would be interesting to know right we've we've had i've been running adopt open jdk on my windows boxes with agents for quite a while i run agents that use both the the inbound agent protocol classically incorrectly named as jnlp but it uses the inbound protocol and the ssh protocol so mitia by all means if if you've had issues there feel free to submit a bug report we'd love to know more about or ask the question in the chat channels on the user list for more conversations about the problems you encountered yeah and what was the backstory behind the recommendation to 11 now now obviously jenkins has been supporting java 11 for how two years now yeah two years plus so what what was what was the the item that pushed it over the line this time to finally recommend it well it was a it was more a combination of multiple themes that were coming out because java 11 support is becoming significantly better on multi-platform environments so the arm 64-bit platform for instance just has better support for java 11 than java 8. system 390 on the ibm mainframe has much better support for java 11 than for java 8. and that made it interesting to us to say all right let's it's about time we move to java 11. we still support java 8 we actually still compile with java 8 but we want our users to begin the process of moving to java 11 so that when the day comes that java 8 is no longer supported they'll have running java 11 that they've been confidently able to use and run okay and that's that's good and we'll go back to mitchell here he says if i'm not mistaking it was oracle java ah okay well and so oracle java's license agreement is commonly restrictive and it may be a barrier he may want to try either adopt open what's now called tamarin adopt open jdk's new distribution tamarin or amazon coretto or the open jdk distribution from red hat uh any one of those three are validated with the jdk compliance kit and fully supported by those particular vendor vendors and they all provide a windows platform okay i did not know that openjd case now supported windows installed yeah red hat red hat has done amazing things i'm very impressed with their work on openjdk okay good to know um let's see what else did we want to call out on this one that i thought was funny i have to call it out uh change the word number to integer in the error message of the number field did you look into that one at all i i remember the discussions on it and and it in fact is doing a more precise description of what that thing is it's an integer a number could be a floating point and this thing really requires an integer and actually this that was one that was sort of like the joke one this is the one that i've been watching for a long time is that now process management for freebsd actually works out of the box right and that's fine that's nice that's nice for those of us who are free at freebsd lovers it really is great to have have one more evidence that jenkins cares about platform portability and this now gives me the opportunity to shoot some new videos for freebsd because i was doing this before realizing it's like oh wait right we don't have support for freebsd yeah well i mean well you could but we've not process management we've run on freebsd for years yeah and and we're very happy with freebsd but this is one more one more improvement for the freebsd implementation yeah uh any other items that you want to talk through specifically on the release notes before we look at upgrades um just systematically upgrading various components like jetty and spring and things like that that it's just healthy for us to do those kind of upgrades we'll talk about the upgrade guide on more details but be mindful that we're taking care to upgrade components keep them up to date and more rigorously track them as up to date as as the world has become more sensitive to the security of components in the software supply chain jenkins is also being more sensitive and more aware to be sure that we keep the components on which we depend current and up to date absolutely okay well do we want to go ahead and move into the upgrade guide i think we should because as much as this list and of course if you get beyond the uh from update stapler on down that's basically just bump bump type items right so well there's some there's some hiding in there there also mentioned the upgrade guy but i think we'll do better if we use the upgrade guide as our framework to talk about them because it's it's not as clear to me looking at this kind of a list as it is looking at the big headings in the upgrade guide the big headings in the upgrade guide warn about the big rocks that might be in the way yeah what i i guess what i was trying to say is if you look at just basically this part which is right above the update or remove type things this doesn't look to be very big right in contrast typically the upgrade guide is fairly small yeah and this release it's very large correct so let's let's just tackle it from top down the default docker images now use java 11. right so so now this there are many different ways to install and interact with jenkins i could install it with the msi file i could install it from an rpm file on centos or red hat enterprise linux i can install it from a deb file on debian or ubuntu many users are deciding to move to docker images as their way of managing their jenkins installation and those docker images are referenced by these tags and there is a tag that is intentionally simplified in this case lts or 2.303.1 neither of those give you any information in the tag name about what operating system is being used what java version is being used etc those are all just you as a user except you'll take whatever they give you and and that's good that's fine you have every right to make that choice we needed to make a choice about which version of java should we be bundling here and so we've intentionally shifted from bundling java 8 inside those images to bundling java 11. now some users may say i've got to have java 8 i cannot switch to java 11. then they can use these different tags jdk8 that more specifically say i absolutely want java 8. and so we don't we don't prevent users from using java 11 with docker but if they were previously using the on the undifferentiated tag they now need to switch and specifically say no i want jdk8 right it's a fairly common pattern for i'm gonna use the word deprecate not it's not what it really means but just it's it's older and yeah let the default be the current recommendations which since the recommendation was to be 11 with this release then why not also allow the container image default to also be 11. right it's it's it's a variation on on what we did in an earlier weekly release where we did the same thing for jenkins jenkins colon latest it's pretty common in docker images to have a tag called latest and the tag called latest is one that users know is not guaranteed to stay fixed at any point it will regularly be updated with newer version of something if you want exactly a specific version you need to say much more than just give me latest correct um let's move uh do you want to talk about some of the changes though with some of the images yeah yeah from buster to um because right i think that falls does that fall into here or does it fall into this no that's the that section that you're in is a good place to talk to that so as part of this change we also use this opportunity because our images the lts and the lts-slim images are both based on the debian operating system and we use this change in this opportunity to switch the base operating system from debian 10 the code name is buster to debian 11 the code name is bullseye debian 11 had spent a good two or three years being developed and just released in i think it was in august so it's a relatively new release nice and fresh with all sorts of current packages on it a good good time for us to make this transition so we switched from debbie and buster to debian bullseye now that that's a positive because it means you get a newer linux linux utilities you get newer capabilities inside the thing however the vendors sometimes change packaging in those transitions and in this case debian changed the packaging it's a good thing they realized they could make their images a little smaller and they made them smaller by removing some packages so some users of jenkins 2.303.1 may need to install additional packages into their docker image as an example my jenkins controller uses the ps command to check for orphan processes it's a check that i like to run because i'm trying to find bugs the ps command was removed from the debian bullseye default image it's still in the buster image but bullseye doesn't have it so for 2.303.1 i had to install one additional file set to get that utility users may find some some tool they need was installed before and isn't installed with bullseye and they'll need to install it now the bigger question is should you be executing into a container and doing things directly in the container that's not why we're here today that's a different conversation well and and and that's that's actually it's it's even worse the thing that i'm doing because i'm openly acknowledging that there are times when i will allow myself to execute a job on the controller and in a in a production environment that's a really bad choice and we have administrative monitors that tell people don't you do that but in my case i'm watching for bugs in jenkins with this little check and and so i i give myself a pass that i allow myself to run on the controller about once an hour and other than that i'm always have disabled execution on the controller so so it's the case that i'm doing is is a little bizarre right it's not something that a production jenkins user would do because their goal is not to find bugs in jenkins their goal is to create great software using jenkins correct now let's move on to this next one a couple of obsolete images and one of which is centos now don't freak out it's like wait didn't we just see centos above we did see centos above but we saw it as centos 7. and this is basically because centos 8 is no longer true i guess is one way to say it yeah it's well it's it's a fun story right centos has has changed their strategy centos used to be a direct derivative of red hat enterprise linux and and the centos project said that's not terribly useful so instead they've changed that now they have this thing called centos stream that is an immediate predecessor to red hat enterprise linux so it's it fills the gap between fedora which is their cutting edge try everything out and do really wild stuff and their enterprise grade red hat enterprise linux centos stream is very close to enterprise linux but is not yet red hat enterprise linux and so it's it's a different place in their in their hierarchy and they've stopped delivering updates to centos eight so centos 8.4 doesn't exist or it didn't exist until a few weeks ago and there isn't a docker image for centos 8.4 at all so so centos 8 is is an orphan from the centos project and we decided this is a great time for us to drop support for centos 8 from ours if someone needs an rpm based distribution they should use centos 7 or they can use alma linux which is a newly added distribution that is following the same pattern that centos 8 did now i want to bring up something that marcin has here switching 8 with ubi 8. also yes and that's a that's a good choice as well that's a perfectly valid choice and the ubi images are available and they're based on that same nice stable red hat infras red hat red hat code base so we spent a lot of time talking about centos i think we'll spend about five seconds saying microsoft has ended support for 1809 images right so use ltsc 2019 instead the long-term support channel is what they call ltsc yep okay then we get into this your favorite thing to talk about 390 right so so i'm i'm really pleased to announce that we support multiple architectures this is an item that's been on the jenkins roadmap for almost two years now and we wanted very much to be able to support more than just the amd64 the intel 64-bit architecture and what we've done now is thanks to the the amazing work of tim jacom and of damien deportal we have support for arm 64 power pc64 and system 390 in certain of our key images and we're really delighted to have that the it's it's good to see it's fun to interact with people who want to do work on these other on other platforms we've seen for instance a nice performance boost and cost savings by switching some of the jenkins infrastructure to arm 64. that's a good thing i'm just i was going to say other things but i can't say those today um let's let's move into um plugins that don't support java 11. now we talked about if you're going to be using that container image that's and you're using the default that's based on java 11 but then you're also trying to use these same plugins okay what's the back story for this one yeah and the back story here is that about seven eight years ago um the cool and creative idea was let's allow users to write jenkins plugins in ruby ruby's a nice very powerful scripting language great great place to write code let's allow them to write code write jenkins plugins in ruby and so the ruby runtime plugin was created it provides an environment where a plugin written in ruby ruby can be executed using the jruby runtime however we've since learned by painful awful hard experience that the ruby runtime plug-in is a terrible thing to maintain we could we're unable to port it forward to java 11. and so because it can't run on java 11 any plugins that use or require the ruby runtime won't run on java 11 based jenkins either now the relief thing here is that most of these plugins were last released between five and seven years ago so if you're dependent on one of these plugins that uses the ruby runtime you need to find a different thing to do and almost all of them it's pretty easy to find that different thing yep long list here we'll let you go through that i want to talk about this next one i had not read the upgrade guide and i'm going through and setting stuff up on a new set of centos 7 machines and all of a sudden nothing is installing and i'm getting ready to open up a nasty jira saying this is broken but then i realize oh wait let me go look in the upgrade notes and then all of a sudden actually i didn't even look at the upgrade notes let me show you what i went and looked at i looked at the actual documentation and the documentation here says oh you need demonize what why do i need demon eyes now what caused that fresh pain to occur yeah so so one of the contributors looked in carefully at the jenkins packaging system that was delivering our rpm and saw that for rpm based solutions it was doing a bunch of heroic push-ups in order to place the jenkins java process into the background detach it from its controlling terminal basically turn it into a unix demon right and it was doing all these heroic shell level things that on the debian distributions we use a simple command called demon to do all the same things the nice thing about using those simple commands is it's much less likely that we've made a mistake in how to become how to detach from your controlling terminal how to put yourself in the background because the demon program or in this case on on the rpm systems the demonize program is carefully written to do that very very well the short of that is it's hard well it's it's an it's another opportunity to have a bug right it's another opportunity for somebody to make a mistake because they aren't as familiar with what it means to become a demon as the authors of the demonize program are correct so in case you're running on centos and you're doing the upgrade or doing a fresh installation you're going to need to [Music] grab the apple repo make sure it's there or wherever else you can get demonized from it all boils down to it's not so much that you need apple but you need the demonized package that's what it's going to look for right and and that's a that's a fun story that one of we had a user who was running centos 6 who said hey my centos 6 doesn't have demon eyes i'll just install demon eyes from source oh that doesn't work because what this rpm says is it depends on the package demonized not just the program demonize and and that's how rpm dependencies are expressed is by packages so it's the right thing to do but it means you need to use the demonize package and in order to get that package the easiest way is to is to enable this this e-p-e-l so ep you call it you pronounce it apple i call it apple release package uh i want to bring in one comment from marcin because i've had the same question why not use systemd oh that's that's a great that's a great thing and we would love to have a pull request that proposes to switch to systemd because that's really the place where this belongs absolutely the person who implemented this change specifically commented during the implementation really we need to switch both debian and the rpm system to use system d system d when we originally implemented these things was pretty young that was now seven or eight years ago it's now a very mature well-loved system used almost universally across linux distributions so absolute wholehearted agreement we would love to have a pull request for the the debian packaging and a pull request for the red hat packaging from somebody who is confident in their creation of system d packages and willing to provide the pull request wholehearted agreement that's the reason marxism that's the reason well you have to think about it you just called out centos 6. i can't do system d on system centos 6. right correctly thankfully system centos 6 was obsolete as of november of 2020. they're no longer doing maintenance on it so we can safely ignore it you you might be able to safely ignore it but people are still using it obviously correct yeah and i've still seen people using centos 5. oh wow so this is this is nothing just because we've moved on and like marcin said it's like systemd man it's been out there mark you just said seven eight years you know it's been really warm and fuzzy for the past three to four years absolutely right but not everybody upgrades os's that often so having a rock solid unfortunate we'll call it that way demonized process is still the um is is the lowest common denominator right now system d is not so yeah and i wish it were i i think we would we would be benefited by going to system d and i fully support it we just haven't had a contributor yet step up to say hey i'm gonna do system d right okay now we get into sort of the what i call the the nuts and bolts of this release and this was like the bottom half of the release notes right so commons digester gone right last release you've already said this in 2010 right i'm no rocket scientist but that's 11 years well for me it's it's somewhat of a point of pride wow we've got a system that's able to execute 11 year old code so that's that's really cool we've done a good job of preserving compatibility that's really cool but it's time to admit this one needs to be removed yes so just a handful of plugins or some suspended plugins already that were gone so again hopefully if any of your plugins pop pop up on this oh and this is one thing we didn't mention that we've talked about before before you do upgrades like before you do your yum upgrade jenkins or whatever it is or app apt-get update jenkins upgrade all your plugins actually your minus one on that is back up everything first with the processor shutdown get a good clean backup then upgrade your plugins make sure everything's still working good and then you can actually go and do your upgrade because these kinds of things will pop out during that process right and most most of the time you've got the exact right story please upgrade your plugins before you yes please do a backup please upgrade your plugins before you upgrade jenkins core so that you're confident you've got the most recent uh that's that was especially important with 2.27 it's equally as vital with 289 and now with 303. so first off cummins digester gone from core stopped bundling plug-ins with jenkins this is where i'll be honest i get confused um like the ldap plugin if i do install suggested plugins is installed that's correct but but that is not the same thing as what we're referencing here right so this is this is a packaging change and the packaging change is for most users not relevant that's why in that second paragraph it leads with the text in very rare cases most people they install the recommended plugins and it's all good they're done what happened was these plugins the three that are listed here external monitor job plug-in ldap and pam authentication were at one point part of jenkins core and because they were part of jenkins core that made their apis part of the jenkins core api so published part of the api and so consumers would expect that that api would still be there now beginning at this i think it's 1.467 so many years ago now that has they've been split out to independent plug-ins and now it's time for us to say all right we're removing the bundling completely you need to if you need the external monitor job program you need to install that plug-in if you need pam authentication you need to install that plug-in it's likely you've already got them installed because they are were not always in the bundled form the current release right okay so that's that one and that would probably only apply to people if you're doing a fresh install you're getting ready to do basically a job migration from well it's this could be a use case i've been running on centos six i'm on a early version of 2x like you know whatever the early numbers were and now i'm moving to centos 7 or i'm moving to some other os and i just want to get a clean jenkins instance running and i'm going to move my jobs this could be one of those things that you might want to it could sort of blindside you right and and your use case is a good example if you're doing a long upgrade a long jump from many many versions back to the current release you might see something like this and it's good to have it mentioned in the upgrade guide absolutely okay removed a handful of jet 200 jet 200 came out in 235. yep wow okay thank you for acknowledging that i might be right um so just removed some of the workarounds that were there no big deal yeah and and all that does that list for me supports the reminder please upgrade your plugins yes truly if you're running a git client plug-in from 2018 you're making a mistake we've we've put work into that plug-in since then and the same holds true for every other one of these plugins they've been worked on since then it's important you update to current plugins what would be your response to someone saying i tried upgrading my plugin and then everything broke so i had to downgrade my plugin back to the version i was using and i haven't been able to upgrade my plug-in now for two years what is your answer to that so there be sure you open a bug report because that will certainly surprise the jenkins developers look at your system to see why that was broken because it's not uncommon for someone to say oh i was broken by this when what we did was we implemented for example a security defense mechanism and you were dependent on the insecure code so when you find those kind of things where ooh i can't upgrade it becomes more and more dangerous the longer you avoid upgrading because you may in fact be choosing consciously to have security issues that you have not closed by leaving those things at old versions okay i just want you you sort of brought it up so i wanted to go ahead and just be explicit with an answer great because it's important it's important to upgrade your plugins it is um okay in the last three we're just going to sort of bundle together i'm going to let you talk through these yeah so so the last three are examples of cases where jenkins core had a capability that was added to it for purposes some years ago and that capability that was added has long since become unmaintained by the people who provide it or not relevant to the jenkins community and so these components have been removed from jenkins core so that jenkins core can move forward more easily so that's what these last three are all about right much like we so this is a variation though of what we just talked about of removing ldap and external monitor and whatever the third one was right this is that variation of that same story well and and the same story still applies here upgrade your plugins those plugins that are actively maintained the act of upgrading your plugins will resolve any issues here those plugins that are no longer actively maintained for instance the ones the examples on jna posix you just need to find a replacement for them and in each of their cases they're very easy replacements right okay so that's pretty much it from a what's new in 303.1 and the upgrade guide which is really long so although it's not as large of an upgrade as what we've seen before or excuse me it doesn't appear to be in actuality it is because you're going to want to probably measure three times and cut once you want to go that one extra step this time i think um as i found out with demon eyes and yes it would be wonderful to get system d i do not doubt that um this is a great question from mitcha if i can find my mouse there we go um what can i do with plugins that don't have change logs check the commits that's it i think right that's the only thing you can do right and and we've we've been actively promoting that plug-in maintainers should use should automate their creation of change logs with release drafter we actually did a whole session and we have recordings available of those sessions teaching jenkins plug-in developers how to change their process so that they use release drafter what it does is it assembles a change log as a draft based on the pull request to that github repository and then it's as trivial as publishing that drafted change log and now it presents very nicely both in the github repository and on the site plugins.jenkins.io maybe darren what you want to do is show open up a browser and let's look at plugins.jenkins.io and pick the git plug-in so just search git you know who why would you do that so across the top tab of this thing there are force choices documentation releases issues and dependencies if you'll click releases it will what it does is it reads from the github release notes releases items and presents it here in a nice readable format so this change log was generated for me automatically by the mere act of me merging pull requests and notice that it's filled with hyperlinks it tells us who the creator of the thing was what the pull request was that generated a brief text description this is what release drafter does and it's actually a lot easier for me as a plug-in maintainer than the old changelog files were hopefully that helps you know understand how to do this right the reality is you have to ask the plug-in maintainers please could you give me a change log please could you give me use release draft or follow our our recordings and submit the pull request yourself to the plug-in offering to that implements release drafter because i've done that with a number of plugins now sometimes the maintainer just ignores you that's their choice but if you submit a pull request saying hey here's how you do release drafter you may be even more likely to persuade them to start doing change logs do you know where that video is where you went through release drafter is it on the jenkins youtube channel it is on the jenkins youtube channel and i can i could hunt it down i'm not sure i would we will find it terribly terribly quickly so youtube.com in the jenkins channel and i think it's called jenkins ci i think that's right and then here if you look search for release drafter and let's see if it finds it okay oh now that i've never used so you just chose to search inside the playlist yeah there it is first i'm searching within the channel right i had never done that before that's brilliant yeah because when i search up in the top box it searches all of youtube and it doesn't help me right there it is so that first first hit is includes a segment on how to do release drafter this is starting to get a little old it might be about time to plan a new one it may not have changed but it still can't hurt to maybe touch it up well and and the cool thing there is we could consider doing that as part of contributor summit that's coming up in early october for asia pacific right we're going to do an asia pacific contributor summit october 2nd and we could very readily say and we've got hacktoberfest during the entire month of october this is a great hacktoberfest topic to say look you mean fest that's the one yeah or hacktoberfest that's what happened um but okay i have to give our forensic digitalocean a little nudge now if you look at the top banner it says 30 days and so many hours right but if you look really close at it it says hacktoberfest 2020. look we know 2020 is sort of drug out but it is 2021. we should uh we should speak with our friend at digitalocean we have at least one there i'm i'm sure i'm sure when they get the new logo ready they will refresh it yes i know but it's still funny because it is 30 days out now we're not going to speak a whole lot about hacktoberfest this time but we will have a plan to talk about hacktoberfest in the stream four to five weeks roughly from now because that will be leading up to october 1st and hopefully we can have somebody come on and talk about what the jenkins strategy the jenkins project strategy is going to be for hacktoberfest this year absolutely because doing it the quote-unquote correct way so you can either like if they do the same thing last year either get your shirt or plant a tree you have to tag your things a certain way in order for things to work so it would be good to have somebody on probably from the project to talk about how we would like to handle that this year i like that i look forward to it okay um one more thing to talk about today before we leave uh and this may be the only time we talk about it depending on when the next release occurs i haven't looked at that i haven't done the math yet it may fall right in this time frame devops world happens september 28 through the 30th the first day is a day of workshops 29th and 30th are just the two primary days all online so all virtual and this year the keynote speaker is none other than the waz the great and mighty was and this should be interesting i'll put it that way the law is going to be there and again we take a look at it lots of sessions from last year and all the sessions that are available for this year you can check it out under agenda at the top there's workshops um workshops i'm not sure if there's paid ones or not i'll be honest i should know this uh but i don't well so i'm doing a workshop this year oh you are yeah come join us for the now we've got we're limited to not more than a hundred registrations for the workshop so so each workshop is 65 so the workshops are paid let's see where yours is do you remember what yours is actually and i think mine is free i think mine's one of the complimentary ones it is this is a free one contributing to open source and we'll be we'll be sharing with people how they can help contribute to open source projects and we'll use jenkins as the example and it's going to be a bunch of fun okay so i'm glad you brought this up because i had not actually looked through this page yet there's actually two that are paid and then there's a handful of complimentary workshops so um at least that's the way i'm reading it it says complimentary let's make sure i'm not messing up here nope okay we're good um so what's this other one here we'll look at this one so uh terraform bridge crew s-bomb which we sort of alert alluded to today software bill materials is now a hot acronym spom uh and some stuff with cyborg yeah okay so again devopsworld.com registration is free if you want to take one of those two courses or workshops that are paid those are paid marks though is completely free and you know what mark do you have your link i forgot to give did you do you have your link for devops world sign up i do not sorry i don't have mine either uh normally i would give out mark's link here too it's very kind of you to so he would get the credit for bringing people in i just don't know what it is yeah that's that's and we've got to do more active promotion we will have more fun with devops world it's going to be a great conference yep uh lots of jenkins uh related uh s what do we call them sessions on yes on this really on the 29th and 30th so i want to call out one in particular and this one if it loads up for us thank you and let's go to wednesday so it's wednesday thursday so you still get your friday off um the one session i want to call out here and this is really small i apologize there we go this one that dylan dewhurst is doing which he's one of our senior developer support engineers from big and slow to small and agile splitting monolithic jeans controllers for increased performance if you are in charge of maintaining and managing the jenkins infrastructure at your company if you don't watch anything else even if you decide to blow off laws go watch dylan's session this session is going to help you understand what you need to do so you're not going to be pulling your hair out and working on sunday mornings at 3am this this is going to be a great session and there's numbers of other sessions too but i wanted to call this one specifically out that dylan is doing so please please please like i said if you blow off anybody else your choice do not miss dylan's session excellent thanks okay uh mark anything else that we want to call out today i think we've hit all the points that we wanted to talk about i think uh if anybody else has any other questions you can go and drop them in the chat i want to go ahead and go back over my notes one more time to make sure that we hit all the points which we did uh again we'll be back in about four weeks i think yeah four to four to five weeks if mark doesn't take another vacation um we were okay all seriousness and and completely breaking the fourth wall uh this was planned for last thursday about a month ago right because we plan it's like okay it's going to release this date so we'll set it up to do this day we usually wait for a day number one we don't want to do it on day of just in case something goes sideways just complete transparency but mark knew that he was going on vacation but forgot so if nothing else we need to help mark remind him of his vacations so we can keep the schedules more correct that's an excellent plan i like that plan if there was only automation software that could do that for you mark or a written calendar on a piece of paper i mean there are all sorts of things that could help with that problem yes thanks okay anyway uh you know what we're just going to wrap it up here for today and you know if you have questions they can you know what i do want to bring up one more thing uh i want to show because recently chat changed for jenkins and i want to pull up um so it moved from irc to i can't remember the name of what it moved to yeah libera or libra it depends on i'm not sure how they pronounce it libra but more importantly i want to call out one thing if i can type it correctly i did okay i'm going to share it again community.jenkins.io oh yes and this is wonderful this has this is based on discourse not discord discourse correct i wish we had discord but that's a different conversation um if you have not looked into community.jenkins.io and i need to bring gavin on to talk more about this um this is a big deal this does not replace the mailing lists this does not replace jira this does not replace fill in the blank however it does give us different ways to ask questions that don't necessarily fit the mailing list format right like this one here eks jenkins setup ask a question great question right this is what we should be looking or like when you post it i'm guessing you probably posted this one let's take a look at it i did you did post this one so this is talking about 307 and java 11. that's actually where the back port came from for 303 was from 307 for that image right so you know if you're if you're if you're fed up with trying to find things in the mailing lists i'm one of those people um this is there's two two sides to this coin yes there's one more place to go look right now but at least this is it feels like it was in the um i'm gonna duck and cover for this at least it's in the 2000s right well and and there are so many cool things about about discourse and what it does for us with labeling i ui overhaul of code coverage plug-in that's about two-thirds of the way down there darren is a great example of uli hoffner a professor at a german university who uses jenkins in his coursework to teach is proposing some significant changes and this is his request hey give me some early feedback i want to make the coverage plug-in more usable for users and i'm thinking about this this and this this is a great place to give feedback to people that are doing crucial and very interesting work correct and uli is also the primary maintainer of warnings in g i believe right okay yes that's correct all right so if you weren't aware of this community.jenkins.io and thanks to the people at discourse for helping make a lot of this possible yeah their donation is has just been wonderful okay that's that's the one thing i did want to call out so anyway let me go ahead and wrap it up for today if you've watched live thanks thanks for hanging out with us through the end if you're watching the replay we'll be back in about four to five weeks roughly um obviously the date's probably been set for the next one which is now almost three weeks away now since today is tues today is tuesday today is tuesday where we are it's still tuesday it may be wednesday where you are i don't think it's monday for anybody else anymore time zones right um and we'll talk about the next release which should be 303.2 should be oh wait was there you you had one more thing i did and so we've we've got an ongoing discussion right now one of the one of the changes that came in as part of the transition to debian bullseye was that the locale on the docker images changed from c dot utf-8 to posix now we were quite surprised surprised because c dot utf-8 can represent characters from all over the world and in fact some character sets for languages that are long dead etc whereas the posix locale doesn't represent characters outside of u.s ascii and so that change was a surprise for us and it's it's getting in the way of some users now those of us who build our own images it's pretty easy you can set the locale yourself but there's some discussion happening now should we roll a new version jenkins2.303.2 to make that change and and the discussions are happening cool okay so there might be a dot to that is just that thing right and and it will be a full release but we've got to discuss it further in the community before we decide yes or no it the the work around is pretty easy but easy workarounds still tend to be a distraction to users correct okay so also one more thing i'm gonna leave mark up for this one today if you look right underneath mark if you're watching on desktop you'll see a subscribe button or if you don't see subscribe and already says subscribe thank you for subscribing but if you haven't subscribed go ahead and click on subscribe and once you do that click that bell right to the right side of that and you'll be notified any time we do these live streams or anything else that comes out on cloudbees tv so mark thanks for hanging out today for everybody else whether you're live or watching the replay thanks for hanging out with us today and we'll see you again in about three to four weeks bye-bye everybody [Music] you

Channel: CloudBeesTV

Views: 416

Keywords: darin pope, mark waite, jenkins lts

Id: 0fnS1pCFUMc

Length: 57min 31sec (3451 seconds)

Published: Tue Aug 31 2021