Jenkins User Experience Special Interest Group, 29 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Jenkins UI/UX Hackfest Demos, May 29

Description

On May 29, 3PM to 5PM UTC we have had demo session where some of hackfest participants presented their demos

Demos:
* Félix Queiruga - Migrating Jenkins config layouts from tables to divs
* Tim Jacomb - Dark Theme for Jenkins
* Oleg Nenashev - Evaluation and Test environments for Read-only Jenkins Configuration and the Dark Theme
* Wadeck Follonier - New Script Security approvals management UI
* Mark Waite, Vlad Silverman - Documentation migration highlights
* Oleg Nenashev, Mark Waite - How to develop jenkins.io locally?

Links:
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/270932348/
* Opening slides: https://docs.google.com/presentation/d/1uUwIE2m-krnN3aUPMKQcUTSbwtpeVaO5ZUFrU_MK4sM/edit?usp=sharing

A

Well, welcome to the Jenkins eix heart fest. At this session we will be recording demos by harvest participants. We will have a number of ideas which have been submitted for this session, so Felix will be talking about engaging Jenkins contact layout. So then we will talk about dark theme, about test environments and evaluation environments for various topics. What it will talk about, no security approval management here and then we will talk about the communication. So this is the current least.

A

If any of participants want to suggest something, please edit to the list- and we will either demo schedule today. So the session was scheduled for two hours, but yeah I think that we will be done in 60, maybe 90 minutes. You could see. First of all, before we begin, I would like to thank all contributors. So it was a one big event and we've got a big number of contributions to Jenkins UI to documentation, and that other is so far. We have 42 contributors who have submitted by contributions tracking site.

A

This is not a final number, because we still have some stories on Jenkins's the way so ten stories there. Also, there are contributing shunts which have not been reported yet and if you haven't reported, please do it because say we needed to collect information, and you would rather I wanted to know it sooner. But anyway, thanks to everyone who has already participated, maybe a number of major achievements during this harvest. So, first of all you don't digest inspiration. Preview was released on Monday and you can harvest you put on some testing and some bug fixing.

A

Then there was a dark theme, proof of concept which is now again available for radiation and for distant. There were many improvements and other components, for example, management, potential, security of the authorization and when smaller, bigger patches in different components, also documentation. Immigration went pretty well, we've migrated around 40 the communication pages and modern 20 plugins.

A

So from what I've, seen and mania mark you'll have more detailed statistics later and last but not least, those had it knowledge transfer sessions for contributors and for junkies users, where they able to study modern practices and to be point formation about how to develop and improve Jenkins.

A

So, what's next for the hard test. Yes, today is May 29th, but the hot fest is not over, so it will be open until midnight, UTC, minus 12, so basically anywhere on your earth. So if you participate in this session, you still have 18 hours or so. If you want to contribute, then on Monday we also have a few sessions, one session by slowly newness about custom shape distribution, build service at and that 2:00 p.m. UTC on Monday.

A

We will have results session, we'll talk about final statistics and about our next steps with regards to swag redistribution feedback, etc, etc, and not that you may just hand them call the logistics and hopefully we'll be able to handle it as soon as possible. So that's the plan, other questions before we place it to the demos you.

A

I guess not, so if you have any questions during their demos, please ask some Cooney or just chat people. Ask participants about the question so give us permission. So you can ask questions on your own and that is also a guitar channel which we'll be using for the hot rest and again you can use it to not ask any questions. So that's it from me and the next presentation will be by Felix.

B

Hi everybody I'm going to share my screen.

B

B

What can I put my video resume? It's okay, so I want to talk about jet again about into another interesting and important PR, that's being on the works for over a year, and we extra push for the last three months, which is appeared, change the form layout from using HTML tables to it to dips this PR, and there are many changes and come these.

B

There is a big implications, mostly about a rework of j-league widgets, such as for a form, entry, optional block, descriptor least many of them, so am I'm going to show you show to show it how how they look, how the new forms look. So, first of all, this is the PR, the PR number, three, eight nine five. We appreciate all testing possible. There's, never say you github freckle, just for our equity instructions. You have to test these created by all that make a lot.

B

You can put the link in chat and yeah and I encourage everybody to difficult if it to try give it a try, look for complex plumbing combinations and if they fail, please report it. So, first of all, I want to show how the management form looks. This is the big manage, Jenkins form Manek system configure system. So the first thing you could you could notice is that the form is vertical follows the vertical layout, no more side of nesting.

B

Now it follows a nice vertical layout for every section and everything we are working also to make them with narrower, so that, because it's not really intended for them to give these, why? Yes, we are going to optimize for readability, you serve it before the forum, so this is, for example, they come either configuration part of the follows: a vertical layout and here's on to the interesting stuff which has the job configuration.

B

This is a pipeline job configuration. You may notice the various also some we are. We are indicating nest, different nesting levels, for example, when they when want every way somebody uses the optional block tele with it, you will notice the content. We thing is indicated by a by this dashed line and everything we think it belongs to this parent code block so yeah. This is how it looks with the grid.

B

Plugging in the pipeline script from support control management- okay: this is a really famous one because it used to overflow and to leave the boundaries of it is boxed, not anymore. Oh yeah. This are an to show for the sake of completeness. This is what the configuration for our for a three stage. Job looks like would look like keep planning configuration a month before in widgets same nesting, the are kind of with you still work. Everything sort of works the same so but there are, there, may be bugs with certain plugins we right now.

B

Actually we only have one or two outstanding bug out and the bugs in the whole kinky in sky dragon ecosystem. There may be more and we appreciate any reports and any contributions. Any questions.

A

Now, questions and each other so yeah one question. So what is the current delivery plan for this feature and what we could do to contribute to that.

B

C

B

Basically it will. The plan is for it to be merge into the correct anything wrong, but to match it to the geekiness master branch within the next two to three weeks, maybe as soon as possible and right now it's going straight into master. If they're, if people find problems or people would rather opt out, we can create, we can try.

B

If somebody would like to commit time into creating an opt-out option, it would be an idea, but it's going in so any it would be opted out in case somebody wants to put in the work, but if it's going in by default, I.

D

Don't know if that what you were asking yes,.

E

Thank you so, and can you give guidance for those of us who are plugin maintainer x' and you showed the poster child that I I worry about and show that it has some embarrassing awkwardness in it I solemnly promise to release a new version that will fix many of those issues, but are there other guidance you want to give us as plug-in maintainer x', hey check this or check this? Is it yeah how.

B

E

Your UI basically.

B

Yes, there is one I have one an example for you, for example: here you see this. Actually, this is the docker half notifications plug-in entry. So you see here this. This text book should be hidden until the selectees. When you click it children, it should only expand, not overpower everything and get.

B

So basically, the and the reason for that is happening is that this plane really finds jelly with its basically, this planning will really find the entry of the only option of the daily descriptive list, so dragons should use default, jelly widgets and which is possible and avoid redefining them.

B

Especially hetero list is something that's most many times really fine, that's a recipe for having a breaking important, basically and if they're, if any plugging author such maintainer finds the Hinkins widget API to be too limiting, please be welcome to contribute the change instead of just forking it, because it will go out, it will fade, it will complicate it so.

E

So my problem is I'm I'm not terribly skilled in jelly. Can I ask on the git er UX cig when I have jelly questions? Is that the place to go for gee I? Don't understand this or don't understand that? Where, where should I go to find to get more education, yeah.

B

Jerry York sig, it's nice, for it's a good way to do for over F for general doubts, and if it's just more of a jelly programming questions I would welcome everybody to asking the developer mean. We are all monitoring that list anyway for for jelly, but that's I think that's a resource for more developer, oriented I believe but yeah. We, we are also paying daily attention to the yolk sac, though any.

F

Research would.

B

G

A

Thank you. So we got one question in the chat is this feature makes a lot of sense for mobile devices. Do we also want to change the menu to be more mobile, find it step-by-step.

B

So right now we're working on the forms. Currently, the tables should be next we're made to make in responsible, responsive, so basic.

B

We're getting friendlier, we will not get during 100% mobile worth in one single PR, but this is a step towards it. I.

A

Think, thank you any other question so to Felix.

A

So no questions yeah thanks a lot to you to judge the team and all other contributors who work on this feature, because it's really big improvement, I'm not going for mobile devices because for narrow screens. So, basically, everything which is smaller than the 1,000 pixels.

A

We have another question.

H

Yeah I have another question so for our testers testing this feature is there any special things that you would like or know that we should pay special attention to.

B

Yes, if somebody knows of a plugin that that has complex, UI form stuff, like checking about selects and all that box, checking us electing an option: populates a select box in another part of the bar. If you know about some of these, please test correct.

H

A

Speaking all about such type of plugins does this change currently applied to parameter forms. So when you trigger a build, you can also specify parameters, and there are many applicants today which have quite extensive for an opinionated layouts.

B

Yeah I mean the real parameters are supportive.

B

If each plug-in I mean delay as soon as I lay out for it to the for the view for each plug-in works.

D

B

Shouldn't be any problem: okay, then we oh yeah, so just to wake up plugin, that's not enough that it is the get parameter plug-in and it works. Fine I.

A

Wonder about advanced plugins like active choice, cetera, but yet guess we will figure it out it. You can see the next phases of testing thanks a lot for a demo. If there is no other questions, we can continue.

A

Thank You Felix, okay, so the next presentation is by team- and this is dark theme for Jenkins.

C

All right, I'll just say my screen: it's not really much to talk to, rather than show what we've got to and you're.

A

Going to have a darker background for this presentation, oh.

C

Hello I would it effect appeared in time that my computer decided it's not gonna work, neither than restart, and can you see my Jenkins yes,.

A

We can okay.

C

So one of the areas we've got quite a lot of feedback on in the UX areas which aims to improve was a lot of interest in a dark theme. So we had a bit of a look around to see what dark things already existed and there's been a couple over the years, but none of them were maintained anymore and we're trying to run them.

C

They didn't work in quite a few areas, especially with the new UX reworks, but even some changes from a couple of years ago on the new job screen completely didn't work at all, so decided takes them. Inspiration from the Camelot dark theme for the colors and the styling contrasting, but all the code was created as part of this. So what we've managed to come out with is a garage, a completely functional, dark theme, there's a few issues and a few plugins that need some tweaks or different images, but in general it works.

C

Fine we've tried to make it just a so listen basic, then some of the other themes and Jenkins like material and neo. This is using all the Jenkins built-in images. It's all. Those changing is colors, basically, so it should be, should be quite maintainable and we've also done a big rework into the chickens core to use CSS variables instead of overriding selectors all over the place, which again should be more maintainable as we don't need to worry about the CSS markup.

C

As long as the CSS variables stay in place, and if they do change, then it should be quite a minor change. So that's a short introduction. Let me just take you through a few different screens. Just so you can see what it looks like. So what you've got?

C

What you can see at the moment is just the king of time page there's about a dozen jobs that are created to showcase what it looks like with different sorts of jobs and just build a table up a little larger and see the build queue which it is the air. It's got. The different nodes I said a build executing in the bill. Queue you've got the pop-out window here, it's all working, fine and the context menu here.

C

You've got a breadcrumbs there put this search bar here and you can click through and go through the job.

C

So the pipeline stage view plugin needs a bit of work, I'm, actually just going to go back and pick one that has a few runs so pipeline. It's got a few different stages and some ones you can see here just doesn't look the best, but that's so that's all contributed by a public plugin. So slightly a bit more work- and you see here all these icons here inside bar work.

C

Fine is one icon where we aware in the pipe one of the pipeline, plugins is using a gift rather than a PNG, so it doesn't have transparency, so that needs to be fixed in the plugin to use a PNG instead. But that's I think that's the only issue, we've seen and well, I think it's one or two issues with family to icons. So it's been surprisingly good.

C

Another menu here, I'm going to create a job next single singer to create job experience, views work, of course, as well, for the create a job. This is going to be pipeline for okay, a pipeline and I'm going to copy it from pipeline.

C

And see here, we've got, and so it's sort of happy pulled in pipeline from the previous one. I can prioritize it and add a string parameter.

C

Scenes another issue here, which is another pipeline control on the plug-in, so that needs effects.

C

And then, if I go build with parameters here, you'll see this is what the form it looks like. You need the scene of it that you can use this.

C

And then I forget.

C

Okay, so this bills, they use a focused view of it, never just go what an admin would see to manage, Dinkins or the tiles here show up appropriately if I go to the manage plugins.

C

Plugins Center shows up, and some contrast here for the categories.

C

That's really normal.

C

Here but to show you.

C

The systems for main system configuration page.

C

Which is smoke.

C

C

So you can do a system, research and then preview it, and then this is just going through. This is some figuration page and there's nothing really jumping out. Possibly the info message is a little bright.

C

But it's functional, so that's pretty much. The demo of the running Jenkins just show you where it is and still have to be, some links that you can find as a github repository in the jinkin CI organization called dark-themed.

C

It's here at themed or CSS, and there's instructions, I'm gonna github page and a couple of screenshots.

A

That is really included. Oh this one yeah.

C

So only I could put together a demo folder with instructions on how you can run this as well. You can I think there's a published dr. English and you also just run make from inside the demo folder. If you want to try it out where it's currently using a pull request on the chickens core for the CSS variables, change, I. Think it's looking quite close to meds, though very soon you won't get to do that, and then this will be available to use and will release eight zero zero. One version.

C

So there's a poor quest here, which introduces the variables have a few reviews already and so hopefully to possibly buy the next Jenkins version next week, we'll be able to release the initial version, the dark theme for anyone to use. In the meantime, you can test it by building a custom version or using the docker image and just test it and give us feedback.

C

The best way to do that is to create an issue you on me have a buzzer, sorry, and so we've got a number of issues already open and we've got a number of issues closed as well, so please go to go and give us any feedback, and thanks for anyone, that's done any testing really swell.

A

Okay, Thank You team. We've got a number of questions from the chat, so the first one is you mentioned that we did some changes in the code, this other than the impact for existing themes that were created for the simple thing plug-in no.

C

So it's completely compatible because the changes in the core are just random variables and some very minor consistency changes. It's found that some colors were slightly different in certain places and some weren't using variables when, when the variables already existed, there's no there's no real styling changes, part of it and we have. We have tested the I think the earth I was just over there just in case to see it. There was and we've edits.

C

So there is one caveat with us that it doesn't so that means not gonna work I in live them because of the patients that we're using and we've done some testing just to make sure that I leave them to break because we had to add some full decks, but we tend to just maintain credibility for now. That's no dark name support. We for are you living right.

C

A

Also worth mentioning, but even if this particular change, it doesn't break themes, we will break themes because there are other changes coming down the line. For example, the story Felix was presenting about invasion from without tables to leaves and main the other stories. So recently we have published policy for you, I think support, and they explicitly say that we do not guarantee compatibility, though Vanya or to I think we will be doing a best effort to keep it up to date. I believe the same for dark thing, but in principle we don't currently until again.

C

Is another question how easy what a bathing users to make a dark variant of the existing thing, so once this missus marish, then they maintain I could migrate I written using the variables rather than I'm, going to override all the styling that be a bit of rework for the enema theme and also be reduced to conversion that available. So, basically, you need to use the bleeding edge version of Deacons. We hadn't used this, but you can still they could definitely duplicate, they have their existing selectors and then duplicate.

C

It would be variables as well, and that would work together. So it should be quite straightforward. I haven't shown the code in this, but the dark bean curd is about 50 lines of variables, plus a theme over 80,000.

A

C

We've got we've overridden the theme for the script console as well.

A

And now two team is more than 400 lines in total.

A

Images VG s VG's various Hawks, which allowed all the right images, etc. It definitely looks great but might be difficult to maintain it when we start doing all the changes in the UI, so I would anticipate that neo2 team thing and other things you're subject to CSS variables. Soon. Yes,.

C

Very keen to keep this theme minimal and using core as much as possible, so it doesn't have to worry about breaking as much.

A

Okay, then yeah other questions.

A

Looks like not so then the next presentation is by me and they will be talking about test. Environments am I still online yeah sure I can get because Tim screen froze for me, so I wasn't sure what's happening. Okay, so I'll share my screen and hear me: oh, this is my screen.

C

Yeah three 300 icons, yeah.

A

If you're a Windows user, that's how you use your desktop, because I really really visited okay I'm guilty of it. Sorry, it wasn't the case when I was using Montes. Okay, let's go to the actual demo, so we had two presentations over to do. One is about tables to the expectation another one number I came about that key and both these areas have one common problem. If you, as a user, want to evaluate that, you need an instance which you want just the top, and you need to stop plug in significant.

A

They can figure the instance just evaluate this component and there, for example, during hard. First, it was difficult for those who want you to do. X testing for these companies and, as a part of the hard test, I created a few O'day in my environment, say in order to support various kiss kisses. So if you have seen previous changes online meetups couple of years ago, I was present and my demo project is configuration was code. It's fully it's a repository, demonstrating figuration is code for development pipelines for edging Sao.

A

This repository is fully configured by configuration esporte, mostly I drove it hooks at the moment, but I'm going to Jake asked, and this repository includes a number of potential good items, for example, jobs, users, say agents and also plugins in more than 100 units, and some of them are freaking. So I decided that what, if I updated this demo and made it possible to easily test the dark theme or table students meditations for users and just think I've done. I just updated this demo.

A

So you can see that this this demo has been just released a few days long, and this demonym would support persisting, read and manage permissions. So this is what was released on Monday I Jenkins weekly. Then there was a lot of updates but basically concludes all the recent patience of plugins with configurations and also the support for additional users.

A

So, for example, for this demo, you can easily test common admin users with manage permissions users, the system reads, or just common users and all configurations included, and in order to run this demo, you basically just need to enter make run in this repository to build everything. Can run well so I won't be presenting this repository because actually have a demo. Specifically, let's see for the dark theme, so I kept extending this demo and if you go to the demo folder, you can see that reduce them is actually based on my demo jenkins configures code.

A

So you just take this demo. It every right so changes war file because we need one from the snapshot so which is not released after that we install additional plugins. Actually, it's just a simple theme plug-in when you install additional scripts, so why there is so much additional steps is because we want to support multiple modes. So, for example, you may want to just run this demo or you may want to run it, for example, in developer mode. So you can develop theme or you may want to run it. This preview, user interface, James corner.

A

We have not only a standard theory, but also preview, who you are, will be some experimental features. You should put try out and well-supported, so that is, for example, some more script and project which says additional flux. If you want to run development mode or these experimental UI and after that, there is a groovy hoop which basically configured steam, etc, based on the main image.

A

So as a user, if I want to test the dark theme, I will just need to run a one command make run and after that you basically will get the same interface like Tim presented, but with no plugins etc. I will launch this demo. It will take one to two minutes to startup. It really depends on your present memory. So in my case, I don't have much one, so it will take some time.

A

What do these demo does is basically starts Jenkins instance, when it installs plugins, we shall bundled in the image. Then it invokes Jenkins configurations code configure some bits of the instance when it invokes system, groovy, screens and configures the rest, because my image has a lot of dynamic project. You should connect current, the country being Jake asked well, you can, but by doing by eating live expressions as well. So let's wait for a while.

A

I'm not sure how long but didn't take that long from this day you can see that that was Jake asked already it's quite quick. Then we have brewery hooks which also initialize own instance, with appropriate users, complete the particular plugins I initialized Emma's setting pipeline libraries, etc, etcetera. So everything is built in and after that yeah, why some time production folders, we configure more plugins, more tools and them in Ableton, so Jenkins's fully up and running.

A

We can go to our host, and here we get to the instance again is dark theme, but currently along a theme with managed separately. So it's still, you have to be done, and here I will.

A

I

Just a question: Eric: did you meet yourself.

C

Yeah you sound cut out for me I really about 20 seconds ago.

G

So, okay you're back yeah.

I

Walking again perfect sorry.

E

We missed about 30 seconds of your dialogue or like I.

A

Stopped on the login screen, okay, so basically what I did I just looked in, as did on the user, so to show you you don't losing his configuration with the same demo and yeah? That's okay, so you'll see dark theme. You can see that I have much less controls and apparently misconfigured my instance, so it doesn't show all the jobs here or maybe the reason is because it wasn't showing them now. It shows them. I, don't know. It's definitely topic for testing.

A

But what's interesting here is, for example, managing so, for example, if I want to test system did only system configuration. This is how I would do that. I kind of example, go to the plug-in page. I can verify that I have access to this plug-in page, but basically I can't modify anything.

A

Then I can go to system configuration and then I shouldn't be able when, if I anything as well, gift opens.

E

All like the the scripts that you've got that are doing all this are right inside that repository they're, just groovy scripts, that you've got that. Are there doing the between configurations, code and yeah.

A

If you go here to my repository, so you can go to any scripts and you can see that there is some magic inside, but basically the magnetization is here. So, for example, if I want to initialize my development folder for pipeline development, you can see the script here so basically checks whether the result development folder I planted, creates that then it checks whether it is a local pipe library, development, environment and if, yes, it just initializes jobs, and there must be this folder so that I can test it without really committing anything.

A

So yeah there is some magic I was presented at previous meetups. I won't be going deep inside. Some of these thermos can be actually replaced by a configuration as code at the moment. Not all of it so, for example, he's one example: here's another example: food. Okay, again, you could configure it misconfigurations Caggiano, but Jake asked, doesn't support a template link now and here basically do templating using Ruby features, so I create a template for docker image and then I just have a right.

A

This is a template for common agent and form alien agent, which sets additional options, link.

C

I guess does support there in the latest version to agree with some anchors.

A

Yeah, technically, you can do comprehensive than occurs.

E

Nice. Thank you thanks for sure, you sorry to derail your demo, you you can go back to your demo I just I. You give me hope when I see things like that, oh there's, even more I can automate. Thank you. Yeah.

A

Right, so if you want to try out, add them I, which configures a lot of things. So, for example, at some point we created a demo for this dinky distribution and Jake asked so it's a janky distribution, but basically it includes the same. Open source begins. So here, for example, you can find a long er mode with which calculates a lot of plugins underground, more demos like that, for example, and configuration is code repository. So you can find more examples if you interested for Jake asked my name is just in the told style.

A

Thank you you here the demos for Jake asked okay. So let's go bit whatever showing yeah we're showing admin configuration so yeah. You can see that it works well almost there. So, for example, all these companies are read-only these components read-only, but we still can modify them.

A

So there is still some improvements to for system admission, but generally it works pretty well even now, yeah, that's why we have several months before the next LCS baseline, so yeah, you can try it out with this demo and, for example, if you wanted to, if you want to try the UI felix was presenting, I also deployed a demo like that. So basically it's exactly the same. I just copied the demo from the dark team and I spent 15 minutes to update the dependencies, and now there is a demo also for tabs.

A

This configuration immigration. So this demo is basically the same. We just uses another baseline at a it enables additional permissions.

A

This common thing is from preview and you can get in that faces felix for showing, but also this applicant rebirth set of plugins and jobs.

A

So it's good for evaluation, and actually these demos can be just run by micron and this micron if you're interested it's just it's something like that. So basically it runs the image and everything is parked inside. So if you want to try out the new features you can take, one of these images and the demonic don't even need to build them because they deployed to doctor hub.

A

A

Okay, any questions.

A

Yeah so again we will appreciate all kinds of testing for these new features because yeah there is a lot of changes happening right now and we will definitely benefit from some additional places for them. So, for example, this is manager admissions which is also in preview, and you can also tested from this demo and it just doesn't provide the entire config I tested it. It works, but definitely we can keep improving all these configurations and we will check your feedback.

A

You, okay, that's it from me. If there is no patience, we can move on.

A

Okay, so the next presentation will be by Roddick yep.

I

So if you see my screen, that's good.

G

A

G

Clip I guess it was just removing two icons but.

I

Yes, so this demonstration is especially, but all to manage, descriptive role so for people that are not aware, ourf, you have normally some script, some job inside your instance, and sometimes you have some pipeline script. If you are not using the CSM, so the get enter Direction directly or co-author CSM, as, of course, you have multiple version, multiple possibility to insert your own script. In that case it just inline pipeline. You have also the possibility to retrieve them directly from get in this case.

I

If you are doing the it'd the configuration with the inline pipeline, you have the possibility to either retrieve them from the right the pipeline directly there with approval from an admin or using groovy sandbox with the sandbox. You are requesting approval for different signature. In my case, if I'm using the sandbox, this call to the method. Printeron is something that need to be approved by an administrator. If you are not using the sandbox, it just the full script that is approve or not. So what is the problem with the current version?

I

So if you are going to the in process script, approval management link so inside the main and Jenkins page, you will see the number of things that need to be approved and you get to something like this. So a full page of things that you need to approve, deny and things like that. You have the full script.

I

You have the possibility to approve or deny the different things, and you have some signature that are already approved, the things that you need to approve and the possibility to clear the previous approval, so that the previous, the current version, if you want- and you have the new version that I was working on- and you will see the pr directly there, so the new feature that I am proposing with that PR is that you can see all the pending approval inside the table so that you can expand the code or minimize it.

I

So you are not put in a page with a lot of noise if you're only wanting to approve one script in particular, for example, in the previous page, you have some script that are not very long but still taking. Alph of the screen in term of space, so it's not really something that you really want in term of UX. In this case, you just have the number of things that need to be approved. What are also added in term of a feature adjust the size of the script.

I

Nothing's really fancy there, but also the request date so to know better what is recently requested or not could be helpful for the admin to determine the order of approval if you want, in addition to that, you can now select multiple things and approve or deny directly in mass editing. So that's something that will normally give you some time because doing it manually in this page could be a bit more annoying. Potentially it's not really a big deal.

I

It just a nice, a feature that we are dinner, that's one of the page, but it's not really the most important part. The important part of that PR is for the scripts that are already approved. So in that list you have the possibility to see the previous app or script in the previous version. When you approve a script, it just the information you ever it just all previous script approval and you have only one possibility to clear the approval. Nothing else.

I

You are potentially a Jenkins's expert and you know that t script are just stored in the file system. So, if you want, you can just remove the different ash data store and it's good. You can manually and individually remove script, but, as you know, you only the ash and in case of ash you don't know what is the script, so it just like playing a game trying to remove things, and, oh it's breaking my instance or not with the new approach. You have no matter that are by default because we still have just to ash.

I

We cannot find magic leader formation behind the dash, but in the case that Ash is used by someone with the approval. So it will not block anything. But if you are using that information, for example, that system command to hone the agent that you are seeing there, you can see the command because the ash is completed from the other script. And so, with that information we can collect together some meta data in this case I know that it's that command, that is linked with that ash and so I can show you the information.

I

If you want to know what is the content of that ash, it just explained the code. You see the the content you know also, who was the requester in case we have data formation, especially if it's something that was approved after the meta data introduction. You can see the approval when it was approved. The last time also concerning the usage. If you are using that script, that could very often you will see a number of usage that is the way I and in control.

I

If you are never using the script, for example, or this one, there are all script legacy version that we are not using anymore, and so the ideal thing is that you can just revoke drop over there. So you are reducing the potential attack vector in a sense, it's not radio in term of security, but more about technical depth. If you want also confirming that page compared to the previous one, all the script are loaded dynamically. So only when you click on the expand code, you will see the Reformation there.

I

It's especially means because that page could be very long. You can have some user with hundreds or even thousands of entries that are already approved, and with that information it just impossible to have something like this, with all the script content being loaded, dynamically anatomica story statically when you request the page, otherwise the approved page will take a long time to load. So to prevent that problem, we just put some asynchronous loading of the script, and so even if you have chosen a script normally it will not text too long.

I

In addition to that, you have a very small thing that I really like is that little tick in the green that if you are an admin, configuring, a job and that job contains some script, all the scripture you are. Writing are already approved because you are an admin. So it's like you, you don't have to approve your own script, it's automatic, and so that tick is just saying it was a script that was written by an admin or someone with one script, and so it's automatically approved.

I

So that could be a nice difference for some of the script between something that was approved or something that was pre-approved. It could have some value for some user, potentially concerning the other tab before the tab, reduced separation of the things that were done in the single page before it just for the moment separate into multiple tabs, we fought an eerie walk and then, on this part, induced separation between tabs. That was already a good thing, but their content is not changed directly and in addition to that, just a nice feature.

I

Also, you have knowledge about the number of things that are inside the different tabs. Instead of just having two blows to the refund tab. You have two information directly in the title and in addition, if the pending approval is empty and you are requesting the page that one you are redirected to the first tab with something inside so that could be really useful for you. If you have something to approve, or things like that, so I think I covered most of the thing I wanted to discuss. If you have some question, don't hesitate please.

I

It looks really.

A

Great well to be honest, I have never really used this choice from my production instances, but yeah I definitely know users who do use them and for them it will be really handy, especially since it's not just about pipe. It's also about other engines that job they sell, etc. So all of it can be approved to them, and it looks extremely handy, more.

E

Yeah I use this interface regularly and absolutely adore what you've done but I. Thank you very much. Yes, sir and people chide me that I use this interface regularly, but I use it for testing in all sorts of ways, and it's wonderful. What you've done looking forward to seeing it perfect.

I

So, just in case the PR is ready for review. If you want, the tests are not written for the moment, not corrected because they are failing, especially I. Don't want to write the tests before we approve. What is the UI we want to have so just in case.

I

You have also some screenshot with the explanation I just gave before, and if you want to use our new instance in the early on the backup of your instance in case it's breaking and breaking everything it should not, but just in case so you can see what is happening. Especially I want to get the ring of the meta data. It could be readiness, so.

E

I I could grab a build of this from Sierra Jenkins at I/o. Where would I go get a prototype build of this, but.

I

Christian, actually, due to the test failing and that build it's not possible directly. So I, don't know that myself exactly! You are to use my branch and with that bunch you can just move and install, and you and I think right.

E

I know how to do have PR check out so I can do that great. Thank you about it. I.

A

Have a question can I manage scrip approvals for my mobile phone asking for a friend.

I

Honestly, I never tried, but let's see if you reduce the page, as you can see, the table is especially not done for mobile.

J

I

J

I

Problem when you have a page with a lot of information, doing that in mobile is always a pain, and if we want to do something for mobile, we can potentially reduce the number of karoon increasing the size of the row. And things like that. But to be all.

A

Jenkins IO, we have several tables and they applied magic layout, which basically converse tables to rows. It goes gets narrow. I have no idea how its implemented, but it looks awesome so anyway, it's just an H case ideas, but for managers that should be really useful.

I

Oh yeah prop just one point: that is the most important feature that I was a bit not sufficiently highlighted there. Yeah you had to approach script, you can know we work individually. The script. Do you work in the UI? We for choosing the file system so just in case keep effect. So I'm done with that made the move. Yeah.

A

One maybe question so.

A

I

Planned on the moment, the IP I used the regular Fink from Jenkins. There is nothing specific, so if you have a token you can call the different apply method, and as do you have the different ash, you can just call reply with the correct action. It's good. So it's an interesting question because actually, in the Korean version, everything is done with a JavaScript API I mean the JavaScript from stapler. It's something that you cannot request using regular hosta pi, but no I'm using a regular hosta P I.

I

So you can use them directly in your script. Potentially interesting.

G

I

You need to know the script, the ash of your script. Thank you.

A

Okay- and we have one presentation left so mark and why and what will present her documentation equation and the highlights we had there.

E

Thank so like, oh dear, where did my I had my web browser on the screen seriously? I instead, I show everyone a blank screen this one. No just a minute, please sorry, there we go. Okay, no.

A

Does the brim of this thing yeah.

E

Yeah, so so what I wanted to do was show show some of the progress that we've made and we've had amazing progress in the last week of the hackfest. The the results are just sort of breathtaking. Okay. Here's one example: the Jenkins and docker page has been rebooted. It's thanks to the Vlad. It's been much improved in terms of current videos. Instead of five-year-old videos, it's a lot better layout. Well done! Thank you in terms of progress on issues we started the week with about 80 or 90, open issues and 29 of them closed.

E

We've closed 30 plus issues here about 25 plus issues here, just with ongoing work there, and you see a bunch of these these issues that are all still in work now, so we're so pleased with the results. Let's show some of the examples, for example, using local language is a new page added to the using Jenkins guide.

E

Fingerprints aborting, a build referencing, a project by name all these pages added to the to benefit users of Jenkins, as they have questions about how to use it. The remote access API great documentation here on different authentication techniques, different ways to use it using with python, elegant, elegant work, done to gather information from the wiki and put it into jenkins thought io now. In addition, the pipeline section got a major new addition thanks to Devon Nussbaum for migrating, the pipeline, CPS method, mismatches page and bringing it up to date.

E

So this was this was an excellent example of a place where we had good information, but that was dated on the wiki and the process of transforming from wiki to Jenkins thought I owed meant that we would revisit that and make sure that it was correct and more complete than it had been before. So thank you very much for that transition.

E

Likewise, in managing Jenkins, we've got a bunch of new new capabilities like instructions on the Jenkins command-line interface, how to use it adaptations and corrections to it. Authenticated scripted. Clients has just been added so that we've got examples for people who want to use curl or dub you get or groovy or Perl or Java to authenticate to the Jenkins REST API s, we've got progress now is showing dramatically and continues to increase on our plugin migration.

E

So about five or six months ago, plugin documentation began the process of transitioning to documentation as code, so the plug-in documentation was right inside the plug-in github repositories. Well that progress. Now you see it here. Over 400 plugins have completed their migration to documentation is code with another over 80 with pull requests pending their next release. So we're we're so delighted with that progress and encourage it to continue.

E

This is giving us a much better layout through the static site, plugins now Jenkins dot, IO and making it easier to maintain plugins we've got a project that tracks that progress.

E

It's showing good results on automation and the work as we go through from from each of the steps to extract the documentation out of whatever location, it was put it into the github repository all highlighted here and we can see visible progress. Likewise, our administrator guide project in github is showing its progress and the user guide.

E

Those are really the things that I wanted to show Oleg. Are there any questions relative to documentation.

A

Not from here awesome progress, so I guess we will spend the next week and maybe one week more to just review the pull requests because we still have something like 30 or 40 staged. So thanks to all contributors who submitted their Politico is now yep. It's our turn. Yeah.

E

It is absolutely sorry, I hadn't turned on my video. It's absolutely amazing the number of pull requests we received and we are so grateful for those who have submitted those pull requests and glad to continue working with them to get them all the way merged so that they're, helping Jenkins users.

A

Speaking of it, we have for google season of dogs starting soon. Somebody wants to keep working results so that I would have a team adjustable that EQ Alec Thank You Tula.

A

So we ran out of demos. Does anybody want to show any last minute lead, hawk ones.

F

Well, I can show basically it's something that I had done couple years ago or one year ago, but I would rather discuss it first, with the quotation officer with Marc and with your leg before you jump into any demo. Just wanted to ask, though I'm not sure, if this forum is the right one for the best approach to running, for instance, Jenkins I go and making this I usually use make inside my ID, something like inside visual code, but I knew, as there is Jenkins file inside that folder.

F

So does it make sense to use another Jenkins project and start this build process from another project using this Jackets file or in some way you both are there some time ago, Jenkins file run right here, something this like what is the best practice best approach in creating this Jenkins on your side yeah. So then, demo time right.

A

Absolutely okay, so yeah few minutes. So let's go you have this the Jencks a repository, and if anyone wants to continue, they have extensive contributing guidelines right here, contributing a dog and in these balance you can find our steps describe, how to build and how to do common operations, and this guide is actually all around make. So there are two commands one is make prepare for building, so they build process itself is the purest and the demo is the Christ. So you can use that and if you want to run, took a Jenkins wrong.

A

I have no idea what is like. Stick look, I.

A

Guess that us might be a bit slow in, you know subsystem for Linux, okay,.

A

Okay, doesn't really matter, let's just run it so yeah. This is the common flow. You run.

A

Because my chrono basically packages your site prepares everything. It's likely to be extremely slow right now, because I should be running out of operating memory resume, but you may be in a few minutes. It will start up, so it will basically have probably development copy. You can edit this side. Example in my case, I use mostly Visual Studio code for development.

A

So why use Visual Studio code because it's convenient with what the tables using IntelliJ IDEA before the table cut down before the part was was so you can basically take whatever you want, which supports? Ask you to preview and highlighting yeah so now I'll cover when I was creating kind of a so we're. You can develop the website here and you can dynamically deploy content so, for example, when you modify asciidoc files, layouts, etc, everything automatically it's not the case for images and for some metadata example.

A

Here you can see that we have some metadata, so this sometimes needs early start of the website. It must have worked, but not always so if we talk about Jamie's file, so we had some examples so there, but Jenkins file is rather designed for maintenance integration. We had experiments with provisioning stage, encouraging Kasai or repositories, but I'm not sure whether this code is still inside. So if you develop things locally, it's but to run make- and everything is the key right, so it can run on any machine. If you use Linux say it's easy.

A

If you use motto, is you just use docker format and everything to work pretty? Well, if you use Windows, you can use doctor for Windows and, like me, you can see that much running on Windows, but with windows subsystem for denotes without an education who can develop other side, you can come and make files come on and pause and it works pretty. Well, though, yeah, it's not that fast, sometimes, but it's a problem of my laptop. It's, not the problem of the website so and yeah once it finishes.

A

I will just get a website like Jenkins IO. So let's assume that this site was built locally, we will basically get it and we will be able to develop that with the guest provision on our localhost 42:42.

A

So it's just in development environment. But right now it's not really.

E

Well and I wholeheartedly support this particular technique makes it much easier to develop to correct to readily see oh hey, how does it look when presented on the page? I can also change sizes of their web browser now very easily and say: oh, how does it look if I shrink this page just recently had some some pages that had very wide examples on them and hadn't realized just how bad an impact? A really wide example, was on the overall layout of the page, so helped a bunch to use make run to see.

E

Oh, this page isn't as good-looking as it should be. Let's fix the examples.

A

Okay, it looks like I wouldn't be able to show it creakin. So when I don't from so much future, go stuffs up in less than 1 min but yeah but like to be silly just everything could make, and you have a look it's right for this. For.

F

Yeah thanks thanks very much for sharing colleague I just was wondering how to use jenkins file and to you clarify this perfectly that you are saying it is used for continuous integration, which is.

F

A

So any other comments or questions before we close down.

E

So so run Shah asked a question on how do you test a PR I like that question, because it hides a lots of things in it? Oleg? Are you interested in talking to that one or do you do we want to? Because you've got a way to test Jenkins PRS, that's really elegant that I find just to be a beautiful thing and there's there are ways to test documentation, PRS as well that I could talk to. If that would help. Oh.

A

This is my beautiful way, but yeah by the way I stopped sharing. If you stood I built almost immediately so yeah, you can I see that so my beautiful way of testing call.

E

The core, the core PR tester or some such.

A

Oh yeah, but it's a during this court. It's not four right.

E

Right I was I was not talking about Jenkins IO I was just thinking that to test the pr2 Jenkins core, there's core PR, tester and I- think it's quite powerful to test a PR Jenkins thought I. Oh I could show a demo of that question.

J

Was about Jenkins IO testing, it's perfect, but I was wondering something as bio testing.

E

We do actually I can show it to you, but it requires installing a specific command. Okay,.

A

So if you want, you can do that yeah. Basically, we can add the same Jake say your PR tester. It's not a problem at all. Dawson I! Don't do that because it's just a few get commands to run with you report the quest rank. But yes in principle, it would be an interesting topic to Don so mark. If you want to show your flow. It's fine. She like is a just the additional remote I switch to the branch and then get to trying so nothing fascinating cattle. In my approach, right.

E

So so I'm gonna share my screen and I'll show you mine, which is is doing exactly what Oleg does, but it's doing is one command that I installed from from a github repository, so so Oleg's Oleg's technique is exactly the right technique. Let me share my screen and we'll show it to you.

E

Okay, so you should see a big ugly terminal, emulator window and if I can make the text big enough to read. Is that readable to everybody? Yes, it is okay, so first first magic is github.com, provides a command-line utility called hub hub, you install it and it gives you additional capabilities. It acts as an alias to command line get, but will also give you additional capabilities like the one I love hub, sync hub sync will bring down changes from your upstream repository, merge them to your master branch.

E

All for you automatically so Oleg said mentioned that there are a couple of commands using get to do this hub. Sync capsulate, several those commands, so that was that was now. If I look at my stab. If I look at my branch list, we should see that I'm on the master branch. Now, if I wanted to evaluate a pull request, let's say I wanted to evaluate.

E

Let's pick one like. Maybe maybe this pull request right. Let's pick here, we go number three, three, eight four. So if I click there there's this is the pull request and it's number is right in the URL. It's also there on over here so I'm gonna say hub.

E

Er checkout three three eight four: now all that does is connect the remote pull in the remote changes and give me a branch locally that I can use to do my work. So I've now got the branch that matches my next step. Usually is all I also want to see what it looks like with master, so I merged from master and now I just say make run, and it will now run a oh I've already got it running on another terminal. How embarrassing?

E

Okay, let's go back here, let's say: make run, and now it's going to start that web server and I can it's now running I'm I'm, not as capable as a leg. I, don't I run on a Windows machine all the time, but I'm not debugging, and diagnosing on my Windows machine and I'm, not running Jenkins that IO build so I have to use this tunnel. That will, let me see localhost 42:42 on my Windows computer, even though my Jenkins IO is running on a on a website or on a Linux server near me.

E

So it it is. It is a delightful experience actually to sit in this kind of development mode, because now I can I get all the benefit of the windows. Little utilities that let me change screen sizes to fit various things. Yet it's it's actually a fun experience to be able to develop this way. So I can now change this one back to a 1024. All sorts of little utilities like that that just make the development experience better rune Chad did that. Did that illustrate for you the?

E

How do you check out a PR and explore yeah.

J

Absolutely thank you, I'm, going to use help now on this one now.

E

Now, admittedly, hub is just is just can't: I can dear it-it's those again the things that hub did, you could do with a git, remote, add I, get.

E

Right and that's that was mine is oh, you know what I know the sequence of commands, but I do often forget them. So I love the hub command hub is long term will be replaced by another command called gh, but it's not been replaced yet, and it's still very much being cared for and runs great.

J

F

Take you very much mark presentation and.

A

Soul so I guess we don't have any other questions yeah thanks again to those who contributed to the hug. First I mean we have a final session on Monday, but it will be just a summary session if somebody wants to demo something on Monday. Let us know so you'll organize something and yeah have a great weekend.

A

The next weekend, nice.

J

Weekend, thanks.

A