Jenkins Infrastructure Project, 19 Feb 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Tutorial releasing docker jnlp agent

Description

Oleg Nenashev demonstrates and describes the release process for the Jenkins Docker JNLP agent. He provides an overview of the continuous delivery portions of the release process (Linux images), the experimental portions of the release process (Windows images), and the documentation portions of the process (finalizing the changelog that had been proposed by Release Drafter).

He shows how the Dockerhub autobuild process is defined and can be observed as the release is being published.

A

Today we have a folk session. Marco asked him to describe how we do the release for junkies doctor images. So today we will just have a shot oak through of release process and we'll get it published on the communication side. Okay, do you see my screen? I do take ok, just quick introduction for those that structure of doctored images for Jenkins agents. We have tuning repositories, one is doctored slave. Another one is dr. general P slave disclaimer I'm going to rename them soon, so they will be finally agents but sabatelli.

A

Do it so local slave who is base image, which basically said remote ink and few other components, and you consider that there is a bunch of buttons a very being released, and there is a second general asleep which actually provides bound connection support for Jenkins. So generally he it's not the Java Web Start, it's just historical meaning of the protocols, but what it really does. It connects agent using standard parameters so basically similar to how we connect the remote, injuring his master's, so it's advanced rapper in compared to Dexter.

A

Ok, we have a few local files. All of them are more similar. We use JQ slave. This is this repository as a base image and when we get rinsed, you can see that now the version we consume is 4.0 1-1. So what means we use remote connect? That is immortal project, and here you can see that what is the changelog and the last release of promoting was for the tool which fixed one issue which impacts destination of the service.

A

So it was a regression on the G his quarry. It's not a problem for us for docker images, so we don't bump immediately unless mark monster adopted as a part of this demo and what was the ask? We just wanted to release the current version. Now our state that for dakichan LP agent, he still didn't have the recent threes.

A

So he gave me when you said: release drafted and I totally change locks, and you can see what changes we have first page so, basically ones which haven't been pleased from the master branch, and here we have enable web socket support. So it's a which has been recently released in Jenkins code, so least we need an engine. There are also other things to process, so this is what we will be releasing how the release process works.

A

Key this episodic has contains the labelling you can go to doctor table and look at how people see that there is a number of labels the being submitted just here, and there are latest labels, so latest labels being delivered automatically every time you launch the pull request, so it's jeans, delivery and they're all set target labels so from some three-toed 40.1 GT 11 alpine.

A

This is what we still need to do so to have a cartridge for the new deployment in order to do that, and what we need is just cut a new release on the github side, because the rest will be handled by docker hub. So currently our built transform. huh That is the plan to move it, edging keys. Are you or the instance?

A

That's working so here with check that everything is ready to be released so again and the version we will be picking up this hold at 0 1. So we can start editing control so since I'm doing the rinse water do I'll just create, and in so the Russian force will be afforded at remoting question one. So how we prepare this fashion, there is documentation readily, but basically it's a base version of remote ink.

A

We use plus one number which we use for incremental versions based on this same base line, because we still we need to deliver changes in some.

B

A

B

So Oh like there was not already a 4.0.1 one. Oh no is 3.40 one. Thank sorry. It right so so the left hand side the remoting version number. This is the first time we will have published a release with the left hand side for that 0.1. Thank exactly.

A

Yet so we really still need to copy edit it so I'm just copying what you have now in the restructure, so you can see that there are. These draft is not complete because some good requests haven't been tagged properly and we don't need to review them and also maybe release title. So, let's double check.

A

What is our policy because sometimes forget it, so we use just version and name here so without any prefixes or whatever, and it's important to keep this version, because we have repositories which is dependable to pick up our dependencies and the destination.

A

So let's take a look at our release. Again, you can see that the better multiple images came and we need to double check that everything is fine. So here we have multiple versions. All of them should be aligned. So these are three images which we push to the production and another who once once so don't get er sorry mean those images are now experimental. We still want to ensure that they're more or less aligned, but here you can see that they use like fashion, but what it means.

A

They don't really do very management here, each time, so latest versions get released automatically every time. So it's not our problem right now. You basically control only these images. We know that them ready to go so, let's just get them here yeah and we have a change load which we still need to finalize.

A

So these changes are ready to go. But let's take a look at this one, so.

A

With this time on alternet card helper, so you can see that it's tested on Asia. So basically it's an internal change which doesn't import users. So we just.

A

This change is going to be able to complicated because promoting so here you can see that we basically bunker the dependencies and we already have adopted slate repository. So we can just take a look. What is the change? What we're so that we can pick it up and then change log? Where has been already prepared? It's updated remote and follows it or the fun to pick up minor improvements for the client side, and that's it.

A

It was one of Nicias severe head because it was marked as a security release, but it's not the security at least four agents on the master side. So we can put a single. You can feel wall priority message, so I just copied the release, text and I put the proper first reference and that's fine.

A

And this is actually dependency update, so we need to take another category for that, so just copied from another channel.

B

And now, if we had, if we had labeled that pull request as a dependency update, it would have done this for us automatically, but instead you copied it for us. Yes, well.

A

It wouldn't create this image look automatically because you can see that there are restrictions to remoting, changelog and other companies, so it still requires some copy, editing but hey. If everything was categorized and properly and pull request titles at a propitious, the proper text we have transplant last time, but yep it's business as usual, so this list is ready and I think we can just click a button.

A

A

So now just yep I just published.

B

The release so- and my experience has been that even after I've published the release, I can still make editorial Corrections to the release to this change log. So it's it's not a permanent or I'll, never be able to change it again. Yeah.

A

You can edit the release, so what happens on how to you click, publish first think you happens in that notification goes out to your users, so it means that this text already goes to your users, a button you can edit it if you need. But the second thing which happens here is again: we have continuous delivery, so doctor hub will pick up these settings and it will start executing so here, let's go to the build section, I'm, not locked in but typing that should pick it up.

B

So that's what you were in slash jnlp life isn't /dr jnlp life. Is this a different yeah.

A

Well, it's the same repository. It is okay. We truncate adopted prefix from dr. Hart, because everything is doctor there. Okay, so you can see that there is no guilt pending, but I suspect it's because I'm not looking.

A

So just a second I'll.

A

Show my screen again, meanwhile, do have any questions mark so.

B

So the the the process that will happen now is all going to happen on docker hub, the actual construction of the images and the publication on docker hub. So so they will actually get the build. They will they'll actually get the Builder the doctor files and publish the tags. Yeah, that's right, okay, and and do we have any control at a scripting level. Everything is just they execute all of our doctor files.

B

A

Like so I'll show my screen again: okay yeah, you can see that now. I have worked him. Okay, some information about the deans and we can just go to the ministry visitor here to see what they was really executed so yeah. Here you can see that the manager content and we have from a number built in progress. So basically we have built all time for GDP 11 and for based on which is right. Even this he gets a bit executed. So you have ten missions. You can check disciplines.

A

So the current curve would automation means the automation on the side of dr. Hopp is quite straightforward, so we have three baselines being produced yeah, so here's a branch, so master branch- it gets reduced automatically, so all time, doctored, etcetera and where they get latest labels and again protects every time. I take a release.

A

They went go so to dr. Hart under the half of the lipids of the bill. So it's a the bin switching a bit critical right now: okay, I'm, not sure what has happened but yeah I think that all the build process is managed by these files. So there is no additional magic inside.

A

It applies to almost all official Jenkins images. So if you use other images which are built on docker hub the process, smallest the same so agent images, Jenkins file run all tools like plug-in compatibility, tester all of the thing. So let's take a look. What happens with our beans? This particular build takes a while, mostly because of scheduling, but you can see that the version is already deployed for the base image.

A

So you can see that the bill has been executed and what it means that all users can now start using it and they can enable with socket supported language.

A

We can just check it just in case, so it's not something I always do because it's pretty well but yeah. Okay,.

A

A

So it's later to download and hear number we can just use.

A

You can just use the Russian command. You should should be supported in this image.

B

Well, and and just the fact that you're able to do a darker poll tells me okay, the the auto build on darker have completed it's there. It's been tagged and- and there are labeled and therefore readily ready to go.

A

Yeah, so the only thing is to ensure with it it's what you're chained, you can see that little help and help already references, WebSocket fault, so definitely the version we eat. We can double check it. If you want so comments are not passed here, that's easily, but yeah you can see the mesh so yeah we're good. That means we needed mm-hmm.

B

Excellent, thank you so so. Does that conclude everything then the release is now done. No other items need to be done.

A

So the only thing that it's better to copy that changelogs before you mushroom requests, because our general confirmation is based on more labels on labels and on our pull request text. So if you spend some time before merging or if they require submitters to prepare this text, we just say first angle and release.

B

Okay, so that's it! Thank you very much. All right thanks takes thank you, yeah. Thank you. I will archive this and submit a pull request to the doctor, jnlp slave repository with a copy of the a pointer to the documentation. Thank you.