Jenkins San Francisco JAM (July), 27 Jul 2016

Previous Meeting

⏯

youtube image

►

From YouTube: SF JAM Meet Blue Ocean

Description

James Dumay presents on the Blue Ocean project, a new user experience built on top of Jenkins.

https://jenkins.io/projects/blueocean

A

I work at cloudBees product manager for this new effort called blue ocean, which is a brand new user experience for Jenkins I've, been working in software development tools, space for probably about 10 years. He previously was a product manager at last moon for bamboo, so he's worked for the competitor and I've, come to the the side of the light and I'm hoping that the Jenkins community with user experience. For me, user experience is more than just pretty wise.

A

It's really about how you guys, the developers, all of you, you know, interact with you know all the tools that you need to use to get your jobs done, and so, while we will be showing some pretty you eyes today, I think that there's nothing better than no UI right, and so we want to get to a point where things are magic and work magically, and you don't have to think about it. You can just get back to writing code.

A

So really, if we think about why Jenkins needs user experiences like if you're a Jenkins user, you can you know the pain. You know the pain today, so you know trying to find the you know set of plugins that you need for the tools that you use to get the job done.

A

You get the right, magic mix of that and then you're, probably pretty good at that point, if you've seen Jenkins, it's been the same for about 10 years, and things have moved on quite a bit and I want to talk a little bit about why that is I. Guess like a bad thing for Jenkins and a bad thing for developers and how we can go ahead and fix that so that's kind of where we are, but really what I want to identify. Is this exponential change across the software industry?

A

That's been happening right, so you know in the last couple of years, everything's I'm sure most of you work in the cloud, so things will be moving in the cloud. The book everything's becoming simpler, faster, better and more turnkey, and that's all really great and we're kind of asking ourselves like how can Jenkins survive that onslaught of change right?

A

If we're really seeing doing you know, Jenkins does what weekly releases so we're moving quite quickly, but really the dial is not moving on the way that people use Jenkins right, so we're fixing bugs we're adding more features. We're not removing features. We're not thinking about like. Is this actually the best way to solve the problem and I think you know that comes down, you know, I I, don't think it. It comes down to any sort of complacency. I think, like Jenkins community knows what they like and through blue ocean.

A

We kind of want to expand our horizons. So we want to say people who aren't in the Jenkins community who aren't Jenkins experts. We want to invite them in so that they can get some real benefits out of it and I think what's happened over the last couple of years. Is this consumer ation consumerization of developer tools? So what I mean by that is, is that as technology changes in Sabre consumer space, the developer tool, the way that developer tools are designed in the way that people want to interact with them?

A

That has changed as the consumer space has changed right. So I've got an example here, so our dough is. We do a lot of user experience, personas and harder as our developer, a Dada I, don't know how to pronounce probably ADA. Is it our developer persona? And so, let's like take ourselves back 10 years, it's almost 10 years. It's C, 2007 I. Think you guys just elected Obama at that point around about that time or George was yeah.

A

Something like that, and you know internet memes, weren't really a thing, and so she's 12 years old and destined that unfortunate day, a fate of becoming a software engineer. And if you look at artist world from you know, 2007 and to 2017 there's been a lot of change. That's happened right. Can you remember phones before iPhone like how or Android or.

A

Wrong building.

A

Like before, like you know, you go to a restaurant, it's like download our app and pre-order and stuff so, like and I think even in 2007, some people still have CRT monitors right and yeah, which is really gross because I'm, looking at my my retina screen right now and my eyes, aren't bleeding and I'm very thankful for that, and then you know, like social net with you know, those that'd be crazy on social networks which really about like okay. We have this internet thing.

A

How do we get this internet thing into the hands of more and more and more people and help them?

A

You know communicate with their friends and family Bell right so in taking this technology to enable this change in the way that people making that technology fit sort of seamlessly into people's lives right and then you've got github who come along and go we're gonna make code like the development of code, social right and they really succeeded at that, and so now, if you're looking for any kind of software in you know of any client, you know this is your gives us your first stop and you probably use this tool.

A

That's probably that you know for a lot of people. The center of their universe right is collaborating with your team members and pull requests. You got companies like Heroku who go and say the process of deploying software. Quick is hard right. So if I'm building a rails app or a building Nijs app, why can't I just make it go, run right, it's pretty standard and why can't I? Just you know, pull a slider across and then all the scaling sort of happens.

A

So we used to have a joke with a companies to work for which was any scaling. Problem was like, let's just add, some more diamonds, that'll fix it. You know it's not. This is verily true, but they sold people on that vision of you know, move a slider and your website scales the more you pay, the more you scale right and it's such a simple, simple value proposition like for, if you're, Heroku and you're trying to sell that, but it's actually the dream for it developers. That's like you've.

A

Just taken like all of the operations you know for a certain class of apps like completely. You know, I have to do that job anymore and more recently, you know: we've got companies like slack, who had sort of improving the way that teams communicate together right and so by the time ADA. You know graduate college and computer science.

A

You know she is entering a world where some of the interactions that we're gonna have with Web Services they're gonna, be, like you know, agents on your phone like Siri or em, or you know what I don't know what Google's ones called sorry: okay, Google yeah, yeah Google, now right and so we're gonna be interacting.

A

That's the way that we're gonna be interacting with with a lot of these web services right and, if you fast forward to like, if you go back in time to 2007, that was that was science fiction right and while that's happened, you know Jenkins hasn't changed right.

A

While all of this, like mind-blowing, like if you've ever read, Charles Stross success on under, like while we're like on the acceleration curve to like where all of this impossible stuff is now possible, Jenkins hasn't adapted to that world at all. So when ADA is gonna, go out, she's, like you know what I just graduated University and my friends have just convinced me not to get that safe internship and start a company.

A

Is she gonna use Jenkins, probably not right and that's a real real threat right for the Jenkins community, because they've spent so long building the software a little labor of love- and you know in an incident can can it can just be irrelevant right? If we don't change, it I think it's a real testament to the the love that the community is put into Jenkins, that it has survived right, and so we need to figure out how to make you know: Jenkins, work, smarter and harder for people right. So I think you know with change.

A

The only way that you can approach change is to take it head-on and just embrace that things are going to change right, and so what that really means is that Jenkins is going to need to change and evolve as software the needs of software developers change right.

A

It's not this static thing so like we're, gonna, build blue ocean and we're think of what we're gonna stick a 1.0 on it, because we like Simba and all that kind of stuff, but it's like next year, Blue Ocean could could be quite different right, depending on what you guys want and what you guys decide is important. So I'll give you a good example of like this: this. What what has happened in Jenkins? You know you know. Ten years ago some people were still using CVS, that's shocking.

A

To think about, the leaper and subversion was really popular right, and this kid thing was just a twinkle and Lina's 12 volts.

A

His eye he's still using big keep up, and so we had CVS support, bundled with Jenkins, and that's a really good decision to make right at the time and then when suffered and became popular did he get bundled in Jenkins know if it was actually the first thing you have to install after you install Jenkins, which is really easy by the way, really good job on that and then a certain point later on, it should have probably been unbundled because no one uses it anymore right and maybe the community to stops maintaining it.

A

Maybe it becomes less important because it's not important anymore and only a few months ago, but Jenkins did we add git and we've all been using it for five six years right.

A

So if you want to sum up, what we're trying to do here is like blue oceans mission is to continuously improve the developer experience to meet the expectation of modern developers on Jenkins. That's our mission. So if that means today, it's pretty UI because it's kind of like a you know a good starting point. It's gonna be pretty UI. If it's the way that you do get workflows and you do get flow or there's some new thing that comes out.

A

It's going to be that right if it could all be all sorts of things right, and so today it's that tomorrow it could be something else so yeah, so I guess to kind of sum that up the tools actually play a big part in this. So, depending on what tools you're using the you see, I guess the user experience of Jenkins could change. So if to give you an example, if I'm a github user, a bitbucket user and I'm submitting pull requests, why doesn't be like code coverage information show up inside my pull request right?

A

Why isn't that there in context, while you know doing the code review, has my colleague done a good job right today? You have to switch back to Jenkins to get bad and dig through lots of UI to get that information, but why isn't it just there for you contextually? So so they're the kind of things that we want to look at with with ocean all right cool, so they give any questions before I dig into what we're actually targeting for our one. Oh no, okay, cool sweet, all right.

A

So what you can see here is the Jenkins dashboard. So this is just the list of all the Jenkins jobs on your server with blue ocean we're building we're trying to build a really excellent experience around Jenkins pipeline. So at the moment there's lots of different job types and if you've, you know, if you're going to Jenkins, is like this new item link it's like for new users. It's like! What's a new item.

A

We don't really guide people to like where the good stuff is, and so we think we think that Jenkins pipeline is sort of the future way that people will create and define their jobs. We're working on. You know new authoring tools for that, so graphical authoring tools. So if you really like that freestyle job experience, we want to give that to pipeline users. So these are all pipelines you can see here.

A

Actually, the top three of pipelines, the the voluntary of freestyle jobs you can see here, we've got like a historical health of what your master branch is like or whatever default branch you've got set the status of the branches. So we'd say you know just simply like they're all passing that he wanted passing or they were actually to failing. It doesn't really matter how many other branches there are.

A

So we try to remove sort of you know uninteresting information from the UI to to increase the clarity and how many pull requests that you're, currently merged validating so pipeline. Has this pre-existing feature where, if you've got a whole hooked up with github or bitbucket, it will merge master with your changes and test that so that you know when you hit the merge button or do it from the command line?

A

You've got that assurance that something works so there's actually quite a bit of integration, one of the lotion that we have plans around github in bitbucket in particular, because they just need to be the tools of the now for this kind of thing.

A

So, let's go have a look at a pipeline, so if you're not familiar with Jenkins pipeline, it's as fun as a pseudo script, language where you can define you, know, stages of your build and tasks like job, sorry, steps that run and if they run in parallel and not, and these get stored in urging conspire in your repo and so Jenkins is constantly as it detects. Changes is constantly reading that and that's your build configuration.

A

So what you can see here is one of these pipelines. It's been instantiated a list of the runs across all the branches I. In this example, I only have one branch called master. You can see if this was a live thing you'd and if you got a the ocean project page, we have a link to our live server, but you know to be spinning. One of the cool things is that, because there's a hot, entirely new technology stack built on to react. Jas in this new technology called server sent events.

A

We actually can update this page live without refresh and it's actually more efficient than a like a you, just your regular edit Ajax app, because the server's actually pushing state up to clients, so it's pretty cool from a fun standard. So these guys over here, but if embarrassing, these guys have been working really hard on making all that stuff just magic and, as I mentioned before, every pipeline can have a set of branches. So what we like to show on this screen is really like.

A

If you're working on a feature branch, you really just care whether or not it's working right now or not. You know too fast with the history. So if you click on one of these, you get a detail on the run. Result that pops up and I'll show that in a moment you can see the weather. For that so say. If it's a long live feature branch or something it gives you a bit of a status report over X number of historical builds. Some people find the weather thing a little car.

A

You know I got that when we released this and got on to hacking years. There was like a big fight about whether we're the icons were good or not. So that's still have to fir debate, but that's the market that we that's the thing that we have right now, but that could change to a sparkline later. If we, if we feel that sir that's what we want to do so cool and of course these are poor requests.

A

So they're, just like those branch branches that you saw before, but they link to a pull request and github or bitbucket. You can click on those and and see what you.

B

C

A

Your code is actually integrated with master, so that's a really useful tool if you're working with systems that have pull requests. So everything you see here, you can get for freestyle jobs, except for the branches and pull requests, because that's a native papaya feature so cool.

A

So, as I mentioned before, you can use pipeline to describe these steps and peril up like parallelism and and stages and and such so we've done less rendering of that there and, as you click on the you know, on each node there it actually renders out at the bottom. You know the log broken up by the steps that actually got executed and if you open up one of these failing results, it'll actually scroll you down and expand the step that fail.

A

So that's so that you don't actually have to hunt through that 10,000 line plug file, which is you know, it's a big pain, particular if you're doing something serious. So it kind of encourages you to kind of categorize and break up your euro of the steps of your build, and then you get this nice experience of you know we're pointing you to where the error is rather than you have enough fish for it.

A

So that's a good example of just some of the little productivity boost we're having the blue ocean just to make it easier for you guys to use Jenkins and of course um we don't get to see. I'm sure a lot of people don't get to see the success screen very often at least saying we don't mostly mostly these days. You know look at that when it's successful, but when you do need to give actually successful result like if you're fishing, you know, release artifacts or something off.

A

We just hired all of the information that you're not interested in. So it's really clear that there's actually nothing here that you need to do alright. So if you want to get to the logs, you can expand the step. You get the changes on the other tabs tests artifacts and we actually just landed a really nice new test. Reporting I wish is not in this slide and that's test reporting UI. So if you're outputting to a unit test results, there's a really funky way of doing that.

A

Cool so one other key feature of blue ocean is this personalization feature.

D

A

We were thinking you know like Jenkins is kind of for teens rather than for individuals, and sometimes that can be a bit of a like a broken window. Problem like if stuff is broken.

A

It's the team's problem, not your problem, and so what we wanted to do is not like lay the blame on anyone, but we wanted Jenkins to kind of surface the information that is happening around the things that you're interested in, so that you can action them right and you can find those things quicker and so, like one of the use cases I have is like. Is it safe to go to lunch right like you're sitting there? You, like you, check-in? Oh, no, it's like 11:30.

A

Is it gonna get through all the pipeline's, so we're introducing this personalization feature so using a simple favoriting system. You can favorite branches of your pipeline or, if you say, push a branch and jenkins detects that you're the author of that branch. It like favorites it for you, so that eventually, your dashboard is filled with relevant information. So, for example, if there's a pipeline that you've favorited that you were an approver for and it's waiting there for some approval, it appears at the top because you're probably blocking the deploy.

A

Okay, if you're working on a Jenkins server, that's used by many teams and you have a shared libraries, you may have committed a change that broke that library, but it's not something that you're really interested in.

A

So even though this one here, like Jenkins, is I like sometimes I commit to Jenkins, IO and Tyler gets upset because I broken something which happens frequently, that's gonna appear at the top there, even though that's something I don't want to monitor every day right and then, of course, you know the things that I favorited that aren't sort of flag. Does this special kind of thing you know running things, go at the top running and queued at the top. Failing then successful and so clicking on.

A

One of these brings up one of those result pages, which makes it very easy for you to like dive in and acts and that information, and hopefully with the things like the logs, broken up by step by step and and scrolling down to the the failing step. That's going to make it like one click and you're right there like right in you, know, you're right in diagnosis, mode, we're going to add some things as well, because it's not always that log that the log isn't always indicative of what the failure is.

A

Sometimes the you know the bill could fail because test failed, so we're kind of exploring some options where we might actually display at the bottom of that. You know, step that was producing the test. Output like these are the things that are broke in click here and go to the full test. Reporting analysis so cool all right. So that's what I've got for you so far, and so I left a little bit of time. If there was any questions that was quicker than I thought, it was gonna, be.

A

Okay, hopefully we haven't done a deploy and broke and everything so so because we are building it continuous, we're building, automation server, so we actually have zinc. We actually have Jenkins so blue oceans, actually chips as a plugin on top of Jenkins. So you don't have to get a special version of Jenkins. You can just use the LTS version and install the plug-in from the experimental update Center. We posted a blog on Jenkins IO, like yesterday on how you can do that.

A

So, if you want to try out locally in production, you can do some people were like I need to I just showed my boss. This and now it's part of my KPIs and like good luck, okay, cool! So yet do you can go play around with it? It's it's read-only. At the moment we are creating building a headed up on the projector before we are building a nice way for you to graphically build your pipeline, but we're hoping that that gets into the one. Oh there's a few dependencies that we need to sort out.

A

So the point is: is that just read only at moment? So just reads your existing: they don't so if you've got freestyle jobs which I'm sure most of you do they'll show up, but you won't get the fancy pipeline graph because pipeline you won't get branches and pour requests. So there's some really good reasons to switch the pipeline. It's just good. You always need to like to spook the pipeline, but hopefully blue ocean kind of speaks for it as well.

A

So what you can see here is that dashboard that we had if we scroll down, let's go and have a look at.

A

Jenkins design lane, which is good so actually all the UI components that would build interesting things. So we build everything in react, Jas and all of the common components like the tabs and buttons and table Styles all those sort of things like if you're familiar with bootstrap, like all of those sort of things we're in a separate library, so that people, if they want to build their own products or plugins or whatever in the blue ocean style.

A

You can just use that module and you get a whole bunch of things for free, but the main motivation there is like stat like when we have more plugin developers, writing plugins. They can more easily write plugins that look like blue ocean if you're like blue ocean and we're gonna have a style guide to say like these are the do's and the don'ts, and the component tree actually reflects the do's and the don'ts as well. So expect more consistency in you know when you install a plugin at all.

A

Actually you know you can actually use it. So in most cases, most plugin developers are very good, but there are some plugins that that you know where they've maybe done some custom stuff for some reason that it's kind of hard to keep it consistent. So what you can see here, you know, is all the act. The runs across you know our different branches, we're gonna, add a filter up here, so that you can look at the history of a specific branch.

A

So there's things like that that we just need to get around to building, but before we really sis for real but yeah, so you can scroll down to a failure open it up and it's taking me down to the bottom. So in this case, like someone's manually, terminated the build there were some changes by someone called no reply, yeah.

A

So someone in the team and Scott they get something set up incorrectly. You can note we can't do that and I thought that got fixed but yeah. It's not! Oh.

A

Oh, it's broken right, oh cool, so actually we can open that one up again, so you can kind of see like just clicking on these whoops and we need a scroll to top button some way so I'm going to design out for that.

E

A

A lot of JavaScript, so it's actually a single page app so like as we're moving around the app we're, not reloading the page at all. But you can see here that you know: we've got a shell script, that's executed! You can look through that and run a bunch of stuff. So that's there! If you need to get them a full log, that's just a click away. You can see the full Jenkins log. So that's what used to appear in the console. You know tab, but now we get.

A

We hide that away, but sometimes it's useful like if you debugging a Jenkins problem. You probably want to see some of this information, but most of time you don't and so cool.

A

You can see here, pull requests, oops nope, so we do things like. If you don't have pull requests, enabled will tell you a little bit. Why how you can do you know what to push? You pull you, as did anyone like ever watch Doctor Dolittle when they're a kid yeah, okay, so, okay, maybe not the people who were born in the last 30 years yeah, but but my mom was a big fan of Doctor Dolittle and there's like there's like a two-headed goat or something called a push.

A

You pull you so I was like and then no one gets it. So we couldn't change his coffee.

A

Didn't it didn't survive some some cultural filter, but yeah, so poor Chris will show up there out. Branches will show up here as well. Do show up here. One of the things that we talking about at the moment is: how can we organize this to be more relevant? So if we've got a favoriting system like it's, definitely like the things that you've got, favorited need to kind of go up the top because they're your things and we have Auto favoriting.

A

When you put branches and Jenkins detects that you're the author, those things are going to appear up there too, and then, when you delete the the branch from from the from gear, then it just unfavorite, because Jenkins will delete the that there's a job that represents this branch in the model that gets removed and updates. So that's kind of cool: do I, have to be locked into rotten employment, or is that okay.

A

Maybe it's these if I just go to where my other window is.

A

So the thing I wanted mo is something that we call quite lovingly the karaoke mode. We had a bit of a just the cloud these people, we have a bit of it- a team off site in in Kyoto and kind of just we just totally digging Japan. So there's this kind of follow along mode as the builds running with the pipeline. So I'll just show that in a second I'm gonna go and run that just doesn't do what you think it does.

A

Yeah so there's a few things like it's a favorite now, that's you.

A

Yeah, there's no pagination at the moment said someone's gonna do that this week.

A

So it Scrolls along you can click scroll up if I actually get deployed. If it's wet, no, oh, we don't actually have the we don't use stages in this bill.

A

We've got time.

E

A

It run long enough.

A

Just try to do this on the tiny, tiny screen.

A

And we only need to get that fixed.

A

It runs too fast, yeah. So.

A

C

A

Language has its some steps in there.

A

Yeah, there's a bug at the moment: that's preventing the server sent of banks working on through a proxy, so we need to fix that really soon yeah. Here we go so it's it's! It's following along appending to the bottom of the display.

A

We're gonna get rid of that awful jump that looks really gross so, but if I I can stop it by either like clicking or just starting to scroll and if I want to go to all the steps here like if I want to go back and have a look at that one I can and then, if I come back and click on this it'll scroll down to the bottom and continue following along. So if you're going on it's an interesting thing in the log, it's not gonna move it around on you! So yeah.

A

Plus the the engineer thought it couldn't be with us this week he really likes karaoke, like it's unhealthy.

A

So that's it! If there's anyone have any questions John since you're the.

B

A

A product manager.

B

A

So we're gonna do so beta we're aiming to do a beta at Jenkins world, probably with what you just see here in personalization and so the favoriting system and all that kind of stuff to try and get most of that working in the test reporting. So we're in really in this kind of making sure the code quality is good and we're going through and testing on browsers and just getting things safe for consumption.

A

As of the 100 I'm, hoping it'll be the first half of next year. Hopefully the closest.

E

B

E

Without too much ninja going back to classic, but there will be in the week the ability to quickly switch back to classic. So if we know on a certain page as extensions implementing I can show a little message saying: hey, you might be missing something here: here's a link to the page.

A

And we're doing some so Jenkins has a dark home like a doll home analytics thing. It kind of just reports anonymously like what plugins you're using any instances.

A

And of course that's you know when you set it up, you can enable/disable we're using that data to figure out sort of what the what sort of the most popular plugins are, and then we've got some further static analysis that we want on those plugins that figures out what extension points actually touch the classic UI, so we're trying to narrow down exactly what plugins do what and how popular they are like relative to if they have UI or not so a lot of plugins contribute. You know like for build steps.

A

We don't have a way of setting up freestyle projects, so we don't have to convert those plugins so, but we want to really target the ones that that do get used. Yeah.

E

E

Componentry have sort of protection and isolations.

E

A

We've worked very hard with blue ocean to isolate this place. I should have plugin failure, you know must read around, doesn't exploit the page, and then you have to go disabling plugins. That will tell you which plug-in broke. Sorry, you had a question. Was it.

E

A

I believe you can have fairly, you can set up fairly sophisticated forms for variables like drop down.

E

With the right access- yes, that's.

A

A picture I think you can.

A

Is definitely a part of the project.

A

So, do you mean you mean sending notifications and things yeah yeah so like any so like, as I said before, like in the beginning of the talk, it's like anything that kind of touches the tools that you use and making them work well with Jenkins it. We count as the developer experience that we want to improve. So you should be.

E

Really easy to say: look this stage of the pipeline are at the ends and notify the culprits by a slack fire email.

A

So some of those notifications at the moment leave a lot. I know some of them leave a lot to be desired, so yeah, it's definitely something that we're thinking about. That's all! So if that's something you're interested in, that's also something that we'd love to get help on more. We want to encourage more people to develop like we're only making trying to make Jenkins easier to use, but also easier to develop, for so, if you feel more of a front-end person or more of back in person, there's like a lot of work here.

A

You know you know we would love to get help.

A

So this is so. This is the editor, so you can imagine you click like new pipeline and said: I want to store this pipeline's definition in there repository. We have a flow that we're still designing that we want to get done for the the one oh about by connecting to control systems and discovering Jenkins files and then with the editor, creating Jenkins files so like we can't have a good editor without sort of like a place to hang it.

A

It's kind of like building a two-story house, and you build the second floor first, so we are doing some work to figure out what that editor looks. Like is the you know. If you look at a lot of these sort of like workflow building tools, they are really horrible to use I, don't know if there's a good one.

A

So what we're trying to do is build sort of the bit like if there are features that we can't put an editor, that we can't make sense or make usable then they're probably not going to be included, but this should be good for people who are starting out with Jenkins or people who sort of used to working in that free style way of working. So with this you can see here, like we've just created a stage for you called build using these plus buttons.

A

You can either close another sequential stage or another parallel step or set of steps within that build stage so say if I go and click on that one, it says, give me a name: it's called test.

A

It then renders out the one called test. We can then add more scripts to it. So this is some random script that I copied off Google and.

A

If I click Add step, I can search for the steps that I want.

E

Including plugins that you might have built bespoke for your company, then they will show up just the same, so you could encapsulate a whole lot of logic in you know some sort of blocks.

E

Especially if you build instead encapsulates all those and steps can.

A

Yeah so like, if you have like a retry Steph, it's five more minutes, yeah say if you have a retry step and you want to retry over and over again for five attempts of a set of steps. You can express that in the editor as well. This geo X is not final, yet we have not put it in front of users, so you guys are the first people who are seeing it outside the outside the blue Russian team, but we will post some of this on the mailing list really soon.

A

It's just it's kind of hard trying to do good design out in the open, because there's always that struggle alike. You want to get it out and get it in front of people, so they know what we're doing. At the same time, sometimes early feedback can be harmful to the process. So it's a it's. It's a balancing act that we try to get it basically out to the community as soon as we can and as soon as we I guess. The way that we feel about it is like.

A

Is it defensible if we put something out there? That looks, stupid, people are gonna, call it stupid and that kind of undermines the whole process of changing this stuff. So when we put something you know, we think is good and in a mailing list.

A

C

A

An awesome question and.

C

Actually, yes,.

A

Like 10k, a blog and because their logs.

A

And it's lazily loading those things so like, as you click on you know, a step. It's actually fetching that from the server and then displaying the first 10k.

E

A

Maven with some selenium tests, yeah yeah.

C

A

That's a very good question, so you can file, you can always file bugs on the issue tracker. It's kind of the recommended way of of getting in touch with us for problems. If you have new ideas, the best thing to do is post either on the Jenkins users or Jenkins developers.

A

Motion and we've got special filters and stuff set up to the blue ocean plugins yeah. So it's it's really easy. Just we're the team that is paid by cloud-based to work on. This is almost completely global. So there's like one day a week where, because of the dateline and all that kind of stuff, where we're not working on this, so um you can get in touch with us. It's it's really cool because and distracting on the weekend. You go out for breakfast things like reflux totally. You like check your email, yak.

D

A

Right go one last question: anyone cool all right! Thank you very much.