Jenkins Online Meetup, 20 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Online Meetup: From Freestyle jobs to Pipeline, with JobDSL

Description

Recording of the Online Jenkins Meetup on May 19, 2020. Presenter: Nicolaj Græsholt, Eficode Praqma. Journey with Nicolaj, as he talks about the pains of managing a manually configured job in Jenkins; converts a Freestyle Job to JobDSL, instantly; introduces mechanisms for adding the jobs to Jenkins, as code; and ultimately converts the job to a Jenkins Pipeline!

Just like last time, in the talk “Configuration as Code of Jenkins (for Kubernetes),” you’ll see plenty of live demos and get to take home all the code and examples afterwards. Use it as the starting point for taking advantage of the Configuration as Code (CasC) that everyone is talking about, and hopefully it will save you a lot of headache in the future!

Links:
* Slides: https://github.com/figaw/freestyle-to-pipeline-jenkins/blob/master/from-freestyle-jobs-to-pipeline-with-jobdsl.pdf
* Demo repository: https://github.com/figaw/freestyle-to-pipeline-jenkins
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/270600737/

A

Okay, anyway, like thanks, everyone for joining Jenkins online meetup to these main 90s and we have Nicole I, will be presenting to the story of negation from Monell jobs to Jenks pipeline which job the SL che my screen and do some quick introductions.

A

Okay, so this my screen.

B

A

If you have never participated and drink this online it up. This is an event organized on the Jenks community, basically contributors to share different stories about Jenkins, to present the demos to show any kind of experiences and we invite everyone to participate. You can ask questions during the presentation and we also invite you to participate in the peach event thanks to or contains Liberty foundation and for us to run the platform.

A

Let's move forward, so speaking of configurations to Jenkins, so we have recently published a new page which summarizes all the contributions. So if you interested in various aspects like just change, your story is meeting people contributing to code to documentation. Please don't hesitate to so might all people participate in the project and next week you have a good opportunity to do that because we run a UI UX harvest.

A

Basically, it's an event where everybody is welcome to complete two different stories: I, believe that, during this presentation and you'll hear some runs from a nicolai about particular aspects of user experience and you're welcome to contribute and to improve the situation, and you can also get special t-shirts and other prizes. So, if you're interested please join us, it's going to be a quite a big event. Hopefully it will be fun for all the contributors, we're also looking for speakers.

A

If you're interested in projects online Meetup again any story which is related to Jenkins, including using Jenkins different environments, to engrave these tools using particular games. Everything is welcome. Recently we have hosted a new page for speakers, so you can go to Jenks online Meetup and there are some guidelines and right now we have a public call for papers proper process, so you can just send an email and video process. So everyone is welcome also just a minute of advertisement right now later today and also tomorrow, they will be copies, connect event.

A

This event they will be a number of presentations about Jenkins, specifically about troubleshooting. Jenkins process includes integrating Jenkins with different tools. So if you interested to learn more, it's a good event, you could follow and it's not too late to register and participate. If you interested ok, let's go back to our presentation and so between representation in a webinar mode. You're welcome to ask any questions in Kuni.

A

So if you open a resume panel that is Knabe a button and then you can ask any question and we will be answering some questions offline and for other questions. We will keep them until the end of the presentation so that Nikolaj can answer them. Then we deserved a lot of time to be followed for final Cooney.

A

You can adjust contact Nikolaj on Twitter and also we have a feedback form, so any feedback will be appreciated and thanks to everyone who submitted feedback, given the previous meetups, we process to that, and we will make sure to take it into account. Also- and that's it from me. So speaking, of course, it's our way to get feedback, and if you don't hesitate, I'll actually run one just see you what job month to three years, just a second and promise, it will be the only polo to be.

A

A

Okay, so, while we're on the poll I'll just stop screen sharing so that we switch to the presentation by niccolò and because I can introduce himself.

B

C

B

We go excellent. Thank you very much. Olli I want you to let you know that for the most part, my user experience with Jenkins is great, alright. So welcome to the talk from freestyle jobs to pipeline with Jacque DSL, my name is Nikolai assault. I am a DevOps consultant I work at Effie code. My help are the organization's. We help with Jenkins darker containers, kubernetes I'm, a certified kubernetes administrator as well, and I spend a lot of my spare time on just playing around with kubernetes playing around with Jenkins I.

B

Absolutely love good documentation, great examples and bring proof of concepts I like building them, I like using the ones that other people have built um so yeah I spent by a lot of my time. Fortunately, just hacking around with this and I've opened my DMS on Twitter. um Please be nice, don't ask like helpdesk e questions, but if you want to chat about Jenkins containers, kubernetes more than welcome to send me a message alright.

B

So during this presentation, there's going to be a lot of demos and I'm going to show you a lot of examples, but don't panic everything you see is what you get um so I've created. This example repository with demo resources- and these are all the examples that I'm going to do today there here you can even open them in the Google cloud shell.

B

So you don't need to have anything but a browser on your computer and um don't worry about the link either because you also get the slides in handout format, so just sit back, relax and enjoy the show all right so from freestyle jobs through naive chap to yourself or native jerk to yourself to pipeline, but so a quick disclaimer.

B

When I talk about the Freestyle jobs, I talk about manual, freestyle jobs, so I'm I'm, not like not bashing, freestyle jobs, I think they're, great I, think they've gone done a lot of great stuff for us, but it's the manual configuration of it that tedious process that I want to say bad things about in a second. So without further ado, freestyle jobs and the five stages of grief also refer to as the Crippler rust model.

B

The first stage is denial, so we think that the manual freestyle jobs are a great way of working.

B

Second stage is anger because we start to experience this configuration drift, I, don't know who's been changing my jobs, I, don't know, I can't reuse. My jobs, I could split the individual build steps up to into different parameterised jobs, and then they could call each other and I would get a tiny bit of reuse, but it's incredibly hard to manage and keep track off.

B

I don't have reconfiguration of my jobs I'm with if I lost my Jenkins or lost my jobs, I would have to manually click all of my jobs into Jenkins, again I'm, just losing I'm, losing my work and losing so much time and I'm just losing my will to continue working this way.

B

The the next stage of grief is bargaining, so I try to change the way we work. I talk to my colleagues like. Can we agree on how we make changes or it can we agree on how we create our jenkins and manage it, but this leads to my depression because it's not working. My colleagues aren't following the instructions. 100% I'm, not following the instructions 100% and that's okay, because maybe the instructions are too complex and intricate to actually work with efficiently right. So the last stage of grief, the acceptance stage may be manual, freestyle jobs.

B

Aren't that great all right, so I want I want something else. So I want pipeline I want configuration as code and I want my pipeline jobs in Jenkins, but I can't just put them into Jenkins, so I need I need to put them into Jenkins somehow, so how do I get them in there? Well, I could create a job for my pipeline and add my pipeline to it, um but then I I keep clicking in Jenkins still, but that's okay, because I have the specification of my java's code.

B

So at least it's like it's slightly better. um It doesn't scale very nicely because then, for each of my pipelines, I still have to click them into Jenkins. um So I'm it's just a pipeline job, but I'm still clicking just a pipeline job for every single job that I have so the acceptance stage. This isn't working out for me. um So I want to try something else.

B

What if I wrapped my hello world pipeline in jug, DSL I can do that and then I can add that manually to Jenkins okay, so that would actually allow me to reference all of my pipeline jobs from the job DSL and I'm not clicking as much in Jenkins anymore, which I really like so I've solved my clicking problem, but I still have this change by modification, so I'm still making changes to the hello jock dsl wrapper whenever I have a new pipeline, so this isn't actually making me like completely happy.

B

um So what about this construction with a with a pipeline wrapped in a hello world job do so wrapper wrapping the job tears of wrapper in a seek job, DSL job and then having the seek job DSL job added to Jenkins. Well, this would allow me to dynamically reference all of the chapter yourself from my one seat. Job Giselle job, so I would put them all in a git repository. My seat jumped yourself would just add all job to yourself in the repository and whenever I have a new pipeline.

B

I just add more job diesel, so the repository so I get this change by Edition, which means it's very unlikely that I'm gonna break something else that was previously working cool.

B

So this and a disclaimer about the stars thing so I'm kind of using them like a grading system like which way of working is better for the wrapping of pipelines. Job DSL is absolutely awesome, so it might as well have three stars it's just for like discerning between the two, but they are different.

B

So this is my focus goal. This is what I want to build, and this is what I'm going to show you how to wear how to get there and today so talking about Jacque diesel. Every slide shown it's a quote. So my quote comes from the job: dsl plugin, it's a groovy DSL for Jenkins jobs. Sweet DSL is just a domain-specific language, so it's not actual programming language, but it makes sense in the context of job diesel in the context of the job, diesel API.

B

So a crash course in chopped yourself, this is a hello world. Job first I have a job tech. It means that I'm creating a new job and your free style job I give the job a name so I named this one, hello world. My job has a bunch of built steps. So it's in a steps block. This job has a single build step. It's a shell step and the shell step is echo hello world and just to show you that I'm not making any of this up. You can't actually specify a job like this.

B

We are going into the first demo of the day. Yes, hands on and I like that, and so I've cloned, the repository onto my computer I've, opened it in vias code. So you can see here all the folders there's a readme will tell you about the repository. The first exercise was called hello world, so I will open the readme and get it into a kind of visual.

C

B

C

B

There and it's gonna tell me that the first step is create a new freestyle job in Jenkins I'm gonna go to my Jenkins and I'm gonna take a deep breath because the Jenkins I'm actually using is a Jenkins that I'm running in a container, and you get that as well. It's in the basic Jake asked folder. There's a docker file, there's a readme for how to build it. It's configured with Jenkins configurations code with all the plugins. You need to do the demos.

B

And, lastly, if you don't have the darker installed, you can open the entire thing in the Google cloud, shell and you can run it from there. It's specified in the in the companion repository you get all right. So the first demo.

B

So the purpose to show that we configure a Java code so create a new freestyle, Kevin Jenkins and call it demo seed, hello, so I'm going to create a new job and call that demo seed, hello, it's a freestyle job and it has a single build step. The single build step is a jump DSL step, so I'm going to process Jack to yourself and I'm going to use the provided DSL script. The DSL script is in the hello world groovy, so I'm going to open this one copy and paste this and save it.

B

Then I'm gonna run the job and when I reload I will notice that my hello welt has been created and there's a typo in my em in my companion, repository and I can build it. While I look at the configuration, so the configuration of the hello world job it should echo hello world and when I look at the result of it, I can see that it echoes hello world. So, with this code paste it into a new DSL job in Jenkins, I'm, actually able to create a job without clicking around in Jenkins.

B

That runs a shell step that echoes in the world cool.

B

B

Now I have my hello, wealth, Chuck diesel and I've created my demo seat hello job in Jenkins. It's not exactly where I wanted to be, but I'm getting there whee. We now know that I that a job DSL job can create another job.

B

um I can actually also inline this job, so I can create a seat job that creates another job. So, instead of having a shell step, I have the DSL step and then I'm actually providing the job DSL inside the job. To yourself all right, I'm gonna show you how this looks so the demo is called seat hello world in line.

B

Seat, hello well in.

C

B

And I open the readme and.

B

It's going to tell me that I should create a new job in Jenkins and call it demo seat in line so I find my Jenkins and I create a new job. Call it demo seat in line freestyle project I shall copy and paste the code from seat hello. Well in line groovy. That's the file next to it in the companion. Repository looks like this.

B

So the same as the slide reproduced here for completeness I copy and paste this into a build step, which is a jump DSL step and I'm using the provided, DSL script, I save it and I run it, and when I reload I can see that it's generated an item.

B

So this seed in line job I can run it and look at the configuration while it's running so this job actually also has a build step which is process, job t-cells, which is the inlined job to yourself that I added to the seat job the indentation is very off, but yeah it's there and when I look at when it's run, I can see that it's also generated an item.

B

So it's generated the hello world seeded and when I go into this job, I can run it while I look at the configuration I can see that it has a single build step. It's a shell step that echoes hello world and when I look at their job after its run, I can see that it echoes hello world all right so now, I have actually created a job in Jenkins.

B

That was a job DSL job that had another job DSL job wrapped inside it, so I can create job. I can create jobs that create other jobs that create other jobs.

B

Okay, um it's still not entirely where I want to be, but we're getting into the idea of jobs, generating jobs.

B

Caveat about this, so in my Jenkins that I have running I've turned a job dsl script security off you should have that on in production and only clear their scripts. That should be allowed to run on your Jenkins masters, but furthermore, purposes it's nice to just turn off. You can also fix the formatting with the strip intent of groovy, so the indentation becomes nice when, when you're, looking at the configuration and Jenkins alright so but I wanted my my job, do you sell in another file and not in lined in a job DSL file?

B

So how do I? How do I get there? Well? I can actually reference an external file so, rather than provided as a string inside the job, DSL I can reference an external file. So the idea is here that I have a repository with a couple of files. I checked them out from a git repository and then the seed external job will generate the job in the hello external file.

B

um But I told you that I was going to show you a lot of examples and of course this is not going to run because it's just like solo code, I can't just copy and paste this into Jenkins, um but there is a demo not going to show it sure to you, I'm, going to show you where to find it.

B

So it's in the companion repository, it's called hello, a seat, HelloWorld external. There is a MeetMe that takes you through the demo and the reason I'm not going to show it to. You is because I am, of course checking it out from an external repository and when you start doing demos with third-party dependencies things break and things take time. So it wouldn't be as interesting to look at, but you can do this on your own time and it works because I just did it hours ago. So it should still work.

B

B

So the cool thing about referencing referencing, an external file, is that I can actually reference files using wildcards. So I can dynamically reference a number of files. So, if I have all of these different groovy jobs in my repository, I can just use this any seed, groovy job so check them out from the repository and then just create all of them and when I want to add a new job, DSL job I, just put it in the repository I run my seed any job again and then it's gonna be added to Jenkins.

B

So I get my change by addition and not change by modification.

B

All right, so this is what it looks like when I have my external chop to yourself: reference buy a seat jump, so this could be the any seat and then I click the any seat, job into Jenkins and then I have my jobs in Jenkins awesome. It's not it's still not entirely where I want to be what I'm getting there.

B

So talking about the hello world pipeline, so I'm, assuming that you already have a number of manually, configured, freestyle jobs that you would like to have as pipeline, or maybe you already have some Chuck to yourself that you would like to have us pipeline in this talk. I'm gonna show you how to get the Freestyle jobs. Yes. Now, if jump, do yourself and afterwards, I'm gonna show you how to get the freestyle jobs as pipeline.

B

Alright, so um from the manually configured freestyle jobs, there is a number of paths I can take to get to the pipeline, but no matter which path I take I still have to get out of the manually configured Jenkins jobs in the first place. um Adding some labels to this I know that I can actually get out of a manually configured Jenkins job instantly and get into some configuration as code by just wrapping the job.

B

This is interesting. Alright. Secondly, I know that I could convert my manual job to native job diesel, but that would take me some time and I know that I can configure my freestyle jobs to pipeline, but it might take longer time- and this is the reason that I chose I- have a project that I've been working on with some Counter Strike servers running in kubernetes and I can't manage everything myself so I'm using Jenkins for this I'm clicking all my jobs and when I got tired of that.

B

I did the naive conversion, because I could do it instantly and I want to show you how that looks like so the third or fourth demo, depending on, if you're doing them doing them all chopped to yourself. I'm gonna show you that a Jenkins job is actually already as code, so it's they're an XML in Jenkins, I'm gonna show you the job to yourself to wrap the XML and I'm gonna.

B

Add it to Jenkins just for sanity checking, so we can see that it actually works and I did this last month and I meet up thinking online meet up the configuration is cut off Jenkins, but I'm going to do it again. Just show you how fast it actually is. So the demo is called job DSL, there's a readme and the purpose to show you that we can almost instantly convert a jump from a manual freestyle job. So now you've jumped yourself.

B

My prerequisites are a job in Jenkins and I should get a copy of the XML to chop DSL template from this repository, so the companion repository for the other talk because right why every query create stuff when you've already done it once I'm gonna take a copy of this and I'm going to create a new file here.

B

New file and call it XML to jump to yourself template.

B

B

Then it tells me that I should replace the XML job diesel part here with the context of contents of my config.xml file and I can get the config.xml endpoint from a job. In my browser, okay, going to Jenkins I.

B

I actually already have a hello wealth job, so I can reuse. This I can go to country, XML and I get the XML specification of it. I can do the view page source to get the raw output, so I want to copy that and then I want to edit the the template. So it also has some instructions I'm going to delete those because I've streamlined the instructions I'm replacing the XML job here lets us remove the XML header I'm, removing the XML header and lastly, I should give the job another name.

B

So I'm going to call this hello world in wrapped up gears up all right. Congratulations. You have converted your job cool, so this is Giardia so now and I can use this in Jenkins I can create a new job. You can call it hello.

B

We call this demo seeds wrapped up to yourself.

B

Software developers are great at naming things. That is a lie and a single build step.

B

It's a chop to yourself build step and using the provided job, T subscript, because I just wrote edge after you, so script I'm going to save it run it once reload and I can see that it's generated my job and I can run it while I look at the configuration so I here I can see that it's actually created a job with a single build step, which is a shell step that echoes hello world and when I look at the output from the run of the job. It's just echo hello, wealth cool.

B

So you can look at why this works on your own time. It is extensively documented, I, really like writing, documentation.

B

Yes, all right! So I.

B

Just instantly converted a manual freestyle TIA to jab yourself using this wrapper, is this cheating no I like my workflow is not like in currently through code. I can make changes to the job through the UI. I could go into configure and change it then I could take the config.xml that I generate in Jenkins and I can persist that in get again, I can just wrap the new config.xml that I get so I.

B

Have my job configuration under version control and I can easily reconfigure my Jenkins by using the dynamic C groovy if I just have the rapped config.xml in my job. Dsl repository cool but I'm also not entirely done because having to go to the UI and making changes to my job and wrapping them in XML, every time becomes a bit tedious or wrapping them, and jabbed yourself becomes the tedious, so I would like to have them as the native job DSL or the or eight Incans pipeline.

B

So um this is the story that I originally wanted to. Tell you, because now I have my naive job to yourself and I can convert that to native job DSL or I? Can convert it to pipeline um converting it to Nate's? If chapter cell looks like this I think it's super cool, because it's an XML that you're just reading with the configure block, which is a cool thing, I've chopped yourself. It allows you to interact directly with the XML, the config.xml of a job, so I can iteratively I can iteratively unfold.

B

This I can do the small iterations to change my naive job to yourself into pseudo naive jump DSL until at one point, I'm at the native jump, DSL and.

B

Then I can take the large leap of configuring reconfiguring. My native Japanese of the pipeline, which is nicer than taking the huge leap of just having my native jump DSL that I'm configuring into pipeline instead and on the topic of large versus huge. Well, it depends. If you have a hello world job, then the difference in size probably isn't that big or if you have like small jobs and Jenkins, then you can probably go directly to pipeline step without doing the iterations.

B

But I wanted to try doing the iterations I. Had this idea in my mind that by the power of the configure block I could unfold, the XML and I could iteratively convert it to DSL with using that, as my elbow grease and I tried it and it turns out, it is just crazy, tedious, it's very time-consuming, but it's a super safe way of doing the conversion, because you are taking the small steps and software developers sometimes like doing small steps to like have a safe way of refactoring.

B

But at other times you might be able to comprehend taking bigger steps at a time and getting further. At a time, so without further ado, I'm gonna show you the job, DSL iterative demo and converting six lines of chapter of XML to four lines of chopped yourself with only 20 slides and how to put an audience to sleep and no I'm I'm not going to show you this, but I have the chapter.

B

So if you want to take a look at it, you should totally it's nice to know that you can actually do this and I created the demo. It's here in the job, DSL iterative folder. You can see the different iterations, so this is say hello, world job and I'm, going through different iterations and I'm, converting it in to job DSL to the native job. To yourself, I have the animated slides. You can see I'm going here, I want to change my description and during these slides, I change the XML specification into some nice tears.

B

Oh it's nice to know that you can do it. You yeah I tried it. So why is this iterative approach? Nice like just to repeat it? If you, you only have this representation of your job, the the UI representation right, the other representation is the config.xml. So if you have a very complex job that you want to turn into job dsl, you either have to do it in one go from the UI or you can wrap it in the configure block. Then you can unfold it do it.

B

If you have to it's nice to know that it's there I'd like to show you the job diesel API, um because I think it's super cool. What they have done. So they've actually made this interactive page where you can click around through the API, so I can find the job clause. So when it's loaded it takes a second and under job I can find so I know that a job has steps, so I can find steps and I can even open here.

B

So I can see examples and I can find the shell step it's down here and I can click it. So I can see an example job that uses a shelter. This is very cool. I think that is a thing that is very, very cool. Is that it actually tells me, apart from the limited, build an API job de sel supports many more Jenkins plugins at runtime. The complete API is available in George Jenkins installation on this URL. So if I go there on the sorry under Jenkins that I am running.

B

When it's loaded after 30 seconds, smart depending on the number of plugins, you have it'll, actually show you the support it has for your plugins, and this makes it very nice to work with Jeb diesel. So um the the API browser, like the the the basic one, is great. The one that's on your Jenkins is absolutely great and very relevant for how you can for what you can do on your Jenkins, so that is very cool. So a great work on the user experience in the Jenkins community, um so I I had this I.

B

Had this thought I had this dream of of doing this, this way of working right, but- and just so so I had the naiive jump to yourself that I've wrapped in the the config.xml that I've wrapped in chapter so I do the iterations, with the configure, blog and unfolding I, get the native jump DSL and then, in the end, I have to do cells so well defined DSL for how to do work in Jenkins and I should be able to relatively easily translate one into the other in one go.

B

So it turns out that this is actually not the way I would recommend. Working rather I would recommend that if you haven't a lot of jobs, a lot of complex jobs that you can't directly translate to native jump, DSL or pipeline, do the naive conversion, wrap them and jab to yourself wrap the XML and jab to yourself just get them as code and then afterwards go back to the UI and convert them to the native job DSL or convert them to pipeline and native job DSL. It's well defined.

B

It'll work for all plugins pipeline is well defined and it'll probably work for your plugins I. Just want to elaborate on that. So it'sit's gonna work for all your plugins with native Japanese, so because of the configure block, because the configure block can interact directly with the XML. If the authors of the plugins haven't created the DSL, then you can just write the XML directly and configure the job and you can get inspired by what XML you should write by looking in the config.xml of a job.

B

You've clicked it's tedious, it's hard, but it's nice to know that you can do it, so you can get everything as code.

B

What I would recommend that you actually do is to use well supported plugins that are actively maintained that are updated and probably have support and pipeline, and that you get your things converted to pipeline but use job diesel. If you can't use pipeline, don't stay at manually, configured, freestyle jobs, alright,.

B

Yes, so the path I chose the path I did for my project is that I first converted, Cindy naive jump, DSL and, secondly, I converted it to pipeline so talking about pipeline. Why not why? Why am I talking so much about pipeline right? I've, already told you the cool things job DSL can do. You can wrap an entire job in it? You can configure any plugin that you haven't Jenkins in job geocells. Why do you want to go away from it?

B

Well pipeline can do a number of cool things so from the Jenkins documentation you get the things as code. You get better durability. You get the ability to post jobs that are running, they become more versatile, which means you can do more stuff with them in the world of continuous delivery and they are extensible, you have it as code, so you get all the benefits of software design patterns and templating and shared libraries.

B

um The things that are interesting here is the durability and the possibility so because we already have it as code with job diesel, they are versatile. We can do anything with the groovy language. They are extensible. It's a programming language. We can. We have the template, but the durability. A pipeline can be automatically restarted when a Jenkins master restarts and it can be resumed from a point so you're not actually during your. You might not even be losing jobs if your Jenkins master is going down.

B

When it comes back up, your job will continue or your job will restart. You have the possibilities. You can wait for user input, I'm, not sure that you can do that in Java, so I think you'll have to trigger some downstream drop jobs manually and then maybe reuse artifacts. You can hack it and jump to yourself, but it's nice that it's natively implemented in pipeline, that you can take this user input half way through a pipeline.

B

The documentation is here, so why do you want to go to pipeline and they, of course, at the as code as well, but it's for the durability and the possibility I want pipeline rather than jump to yourself all right. So how do we do the pipeline? Well, here's a crash course. A HelloWorld pipeline.

B

First of all, I have the pipeline tag I'm, specifying that I want a new pipeline. I, give it agent any because my pipeline doesn't have any specific requirements as to where it should run. It has a number of stages.

B

The first stage is a hello world stage. The hello world stage has a number of build steps. This one has a single build step. It's a shell step and the shell step is echo hello world all right, um so reiterating the topic large versus huge. Well here. The difference isn't that big right, um so there's two points to make here. You might want to go directly to pipeline because we're just using the shell build step, it's natively, implemented in pipeline. It's there.

B

The second point I want to make is the difference between the two, so they actually look quite similar, which means you haven't wasted your time if you are converting your jobs, to jump to your cell in the first place, because you can't go to pipeline because at a later point you should be able to make a relatively easy conversion between the two. It's two well-defined T cells.

B

B

So I know that I can get my coat as pipeline now excellent. But how do I get my pipeline into Jenkins?

B

um Well, I want to use my hello world, Chuck diesel rapper, of course, but I don't want to rap job to sell anymore. I want to wrap a pipeline so instead of creating a job, I create a pipeline job and then inside the pipeline. Job I add a definition. So that's the definition of my workflow I added from the CPS, so that means a groovy continuation passing style. It's the way, I'm writing my code in groovy and I'm supplying it with a script I'm just gonna inline it.

B

It looks like this with the Hilo well jump from before, and it totally works. I'm gonna show you the demo hello pipeline in line. I'm gonna show you that the job to yourself from the slide works so that we can actually just wrap a pipeline in jump to yourself and I have the disclaimer that script security is still off because it makes it easier to demo things.

B

So the demo was called hello pipeline in line.

B

Alright, so to show that we can configure a pipeline jumping jack diesel, it's gonna tell me to create a new freestyle job in Jenkins I call it demo seat hello pipeline in line so I'm gonna find my Jenkins and.

B

mmm I close that one I probably did because I opened the I open job to yourself, API and then I close the afterwards all right. But here we have it.

B

So I want to create a new job and I want to be called demo seat. Hello pipeline in line I'm still creating a freestyle project, because I want to have rap job to yourself.

B

And the job do you so that I want to rap is in the seed hello pipeline in line groovy file, and the last thing I did before we started today was to move all of the code into separate files, because I thought that would be easier, but in retrospect it makes it way harder to have all of the files on the same page. So yeah we learn, and while we do so, I have added the pipeline.

B

The job DSL pipeline job it has the inlined pipeline I've created the CG up and I can run it to generate my job.

B

If I reload it I can see that it generated my job, I can run it while I look at the configuration and it has a pipeline. So this one doesn't have a build step. This one has a pipeline block where it has a pipeline configuration that's because it's a pipeline job and when I look at it. After its run, it has the first first stage, so the hello world stage it has I, can click here and I can click on the locks I can see that it echoed hello world awesome.

B

Oh back into the presentation there we go so I have my hello pipeline in line job with, which is my pipeline in a job. Dsl wrapper I've edited by the demo seat, jump T cell Radford job, um but what I actually wondered was to have it in a separate file. So, of course, just like we did with chapter yourself, we can make this construction as well.

B

So this is what it looked like when I had it in line so I have my hello pipeline in line job with the pipeline code in lined in the job, but I can also reference using the CPS SCM, so I'm referencing that my Jenkins file. It comes from some git repository and then, when I check it out, the Jenkins file should be in my workspace and I can create, and I and I have the job specification from that.

B

So that's how the job will be created all right and my hello pipeline I can reference that in my hello pipeline seat, job either directly or with wildcards, to get it dynamically, but just for the construction and.

B

I'm done I have the I. Have the I have my Jenkins pipeline file? I haven't referenced from my hello pipeline job dsl wrapper I. Have my job. T is the referenced in my seat, job diesel, so I can reference a number of jobs. I add this manually to Jenkins, but that's okay, because I'm just adding one job and it's gonna add my entire platform of Jenkins jobs right. So I would like to introduce you to freestyle jobs and the five stages of configuration as code or the configuration as code model.

B

So it's a bit different than the model for grief or kubler-ross model, but please stick along so the first step is confidence. I feel confident, I know who changed what when and from which values, because it's in version control, I'm using well-defined workflows that we use for software development and my example I'm using Gibbs, so I know what changes have been made and what the current state is without having to go into Jenkins and figure it out. I feel value, I feel valued.

B

I can reuse through shared libraries with pipeline I can use software design patterns because it's groovy its programming language I, don't feel like I'm wasting my time.

B

I'm not doing tedious tasks clicking around in a UI just to try to keep up with whatever configuration I want my pipeline to be in I feel relaxation I have the automatical reconfiguration of jobs, so I don't care about my Jenkins master if I have it in pipeline, I might not even care at all what my Jenkins master is doing, because it's just gonna still gonna restart my jobs and run them. It's still, gonna have my things. I.

B

Feel collaboration, which is not an actual emotion, but it should be I'm working with my colleagues, we're not working against each other and I'm enjoying working with my colleagues, because it's not it's not like we're on a battlefield, we're actually working with each other and I feel happiness, because this is a great way of working so yeah we did it. We have. We are from from freestyle manual freestyle jobs into pipeline and we are adding our pipelines with chop DSL and we're managing our job DSL in the same way.

B

B

So does this get better? It actually does, even because so I told you about this change by addition. Change by modification um I, of course, want to use the wildcards so I, just wanna have my job. Dsl seek jobs or the sorry. The job diesel wrappers in a git repository and I want the super seat job to just reference. This repository, but give me all the job diesel in this repository and it gets better because I can put the super seat job into the repository sorry and it can reference itself.

B

So it's constantly keeping up with the current configuration of it and I have the configuration of my super seat, job under version control, and it gets better, as you saw when I accidentally clicked on the slide, because I don't have to manually configure my first super seat. Job I can add that to Jenkins, if I'm using Jenkins configuration as code, so no clicking at all just a readily configured Jenkins with all of my jobs, but that's the thing for earlier, so we actually did last month an online meetup.

B

The configuration is code of Jenkins for kubernetes, in parentheses, moral of the story being, if you just get your Jenkins jobs s pipeline job to yourself, and if you just get your Jenkins configured as code afterwards, putting it into kubernetes is trivial. So thank you. Any questions.

A

Yeah thanks for your presentation, you collide again. If you have asking. If you have any questions, please ask using coordinate featuring zoom and we already have a number of questions. Answered example: some wine.

A

Wonderful, so one question from blood: it would be interesting to see here our pros and cons of agent jobless and it was a jinx pipeline right. So.

B

The pros of using DSL is that you have everything configured as code. It's an old way of doing it, which means it's tried-and-true. It works and it's going to work for all plugins, because you have the configure block the process of doing it with pipeline. Is that you get the restart you get the resume. You get the durability of your jobs. If the Jenkins master crashes, your jobs will might even still be running and able to pick up where they left.

B

So yeah, that's the so the cons of using job to yourself. You don't get the durability of pipeline the cons of using pipeline. It might not be implemented for all the plugins that you use, but you should of course, use updated and will maintain plugins.

B

Great anything to add all ik all.

A

Right yeah person, values pipeline almost everywhere, but yeah I do appreciate job, especially in conjunction, is Jake. Ask.

A

Okay, the next question, just like concourse, that can we do all of these great pipeline right, pipeline, etc through home online.

B

That's a great question: a Jenkins has an API I know and you can fire post requests and get requests to it. So yes, but what I'd like you to do, instead of using the command line, because now you're just sort of like scripting your way out of you're, creating like long shell scripts that will create all of your pipelines. I would like you to create the pipeline in job to yourself and then reference the job diesel in the seat, job and then reference in the seat, job in your JK's configuration.

B

So when you start up your Jenkins you're, not firing off your Jenkins post-install script and waiting for that to continue you're just starting up a Jenkins, that's configured with all of your jobs and all of your plugins Oh.

A

Like you're muted, if anyone is interested in managing Kissel, I shared a link in the chat, so we're Jenkins has extensive CLI. Actually now we have two implementations, one insufficient in Java, another one is unofficial in gold, but you can take any of them and you can create a job. There sell jobs there. You can invoke them to generate final jobs. You can also watch them. So in principle, guess you can do anything using CLI.

A

Okay, let's move on: how can you change a job that is already migrated to job? They say.

B

So I think that, like you had you wanted to do another meter at some point, referencing some tools that could help you. Oh.

A

A

Second, so in Jenkins there are tools which allow drink. Some immigration, for example, has presented tools for job Basin, but also a very similar tools which allow you to make big to pipeline directly. For example, I'm showing we declare an educational system, so it was created by the MU and I am the Olie Bellamy, and this tool actually provides some engaged supported annexation. So you can generate a declarative. Pipeline code are very similar to poor scripted pipeline.

A

If you wash, and then you can glue them in which job yourself, so that you can incremental changes needed and all the changes is code, so yeah hope it answers the question all right. So, let's move on and the next question is have you played the same for mining jobs.

B

For maven jobs, so instead of having my manually configured job as a freestyle, job I would have it as a maven job. I have not tried that, but I would expect that if the job is in, if the, if the job is available in Jenkins, you could find the config.xml and you could convert it using the wrapper and I would expect job DSL the API to have the to have a maven job just like it has a job yep.

A

So in principle, moving jobs and Feustel jobs by quite close, the user, they same internal abstraction, pulled abstract project. It might be a bit more difficult if you want to meet date. For example, promotion jobs from promoting builds plug-in, though there is still some integration with job they sell, but yeah all classic jobs should be.

A

If you some heritance plug-in or something like that, yes, it's a completely different story, but for making jobs it shouldn't be a problem. So if.

B

I just quickly share my screen, then you can see here in the Jenkins job dsl api. You have a maven job on the left and if you click on it, you can see examples of what a maven job looks like.

A

Yes, all right!

A

Okay, thank you! So the next question, or would it be possible to define the denying maker to job with Drake asked and the robber without my no steps? Yes,.

B

It is, and yes it certainly is and I, even though I know the person who's asked this question, but he I didn't tell him to ask it. So I actually did this in the last presentation and if we look at so this is available on the Jenkins online meetup, as well as a previous presentation, but so this companion repository had a demo for four, also bootstrapping, a Jenkins configuration as code with the job and looking in the advanced examples of the Jenkins configurations code.

B

If we look at the Jenkins configuration s code, Yama file, you can see that you can actually supply a job, so I've supplied one job which I've called supersede this super-sick job references a URL. So this is the configuration as coach, Jenkins job T cell companion repository. It uses credentials because it clones over SSH and then it runs all of the job DSL in the repository. And if you want to see how you also medically trigger this as well, it's explained in the in the other video.

B

Thank you for that question.

A

Don't so we answered six questions if you start from six questions now, you'll have nine to go: Oh, wonderful! Okay! Let's continue here have some time. So the next question is from earlier: what testing framework can you recommend it because the Jenkins's code, its job diesel and pipelines? Oh, that.

B

Is a great question we actually talked about that internally.

B

Olek. Do you have an answer very for that.

A

Well, I have some answers because we do some testing. For example, I can probably show some examples. Oh I cannot show examples for what it works, but yeah so yeah. Let me share my screen this year. Yes, so there are, some foundation beats for testing. For example, if you want to test by plan, there is a framework called pipelining you need, so the zinc is pipeline unit. This framework basically allows adding some or a unit test and for jenkees pipelines it doesn't allow doing a job.

A

They still testing for job the self testing, for example, what I would use and what I'm planning to document in the news creation there is a framework called.

A

Jenkins Runner test harness, so please don't be afraid about the name so jinx file Runner is a completely different project. It's fast top ability for Jenkins, but good news is that if you follow full configuration s code via Jake asked this job, they say this pipeline. You can run your project not only as classic Jenkins but on also strings file. Runner. There are tools for bed and you can use of this framework for integration testing. So it's what I'm currently working for watching leveling but yeah.

A

Basically, this framework allows you to pick a show Jenkins instance to Jenks fellow runner and then run this since this is a common unit test. So it's quite handy it's under development, but if anyone wants to try it, please feel free to reach out to me and I'm happy to share some examples and I'm planning to do urging his father on our demo. Maybe next month the Jencks on my meter, so I will be happy to share it.

A

Okay, I hope it answers the question indeed, but yeah work in progress, but we are well aware that this area is important and in Bejing project we want top for better tools for it.

A

Okay, so I'll share the links afterwards and yeah. The next question is: what are the best practices that our dependency held with police yeah? If it only relates to the talk but I thought that it's important to briefly discuss this question. Yeah.

B

Sure I don't have a good question. I, don't install a lot of plugins that you don't need. There is I think there is a plugin that will tell you which jobs use which plugins and then you can export that and then you can try it try to figure out. Do I have any plugins in store that I'm, not actually using so I would recommend it use as few as possible to solve your to solve your problems.

C

I'm used to the phrase dependency hell coming from conflicting dependencies in a the simplest technique. I've ever seen was used the plug-in manager itself and let it handle worrying about satisfying the dependencies when I tried to manage dependencies outside of the plugin manager in Jenkins, I tended to have much more of a challenging problem that if I left the plugin manager do the job a.

A

Plus one and right now we're working on better plug-in management tools. So if you are following drinks online meter up last year, presenting plug-in installation manager.

A

Plug-In installation manager tool which already offers some tools for advanced diagnostics, for example, showing how able updates of security warnings and other things. So this tool is already available. You can use it, it has its own limitations, but you can try it for better plugin management. We plan to keep adopting features from that there, for example, in official docker images, so that they have better analysis of transitive dependencies, etc. It's in our plan same are, for example, if he used tools like custom work packages that I can play some happy.

A

Some features which verified compatibility of plugins, it's an advanced packaging tool, but it can be also used for incubation as cold and yeah this. What we have development for users, but we also try to address like in a management on the developer side. So, for example, yesterday there was a meet up with James North. He presented a duo of materials and new enhancements in plug-in homes for plug-in developers. So it's not something like we totally rely on users to properly verify dependencies.

A

We also invest in the junk is put in so that, like in my developers, can ensure that there is no binary conflicts and then, but we can ship most able forgets to James users. So if you're interested, you can go to the online media page and you can find the recording here, there are more tools for Jing. Is flicking developers available online makeups about that soon.

A

Okay, so yeah it's a long question, but very different tools. We shall have to check it. Ok next question is apart from Bui. It does be support any other language and this job they sell and pipeline.

B

Olek, do you know that I actually I'm, not sure I expect not I'm.

A

Happy to answer this question so yeah, it's not my first pet, but I would be happy just it on my own, so for pipeline. You may have seen the recent news so that you now have by planners Hamiltonian, which is an in the incorporated state. So it's under adoption and they give me one idea- wants to try it out.

A

Please do so and the surprisingly works defining pipelines as the mo for job they sell right now there is no such capability, but technically it would be possible to implement it and I guess you could feature requires and maybe contribute it on your own. So practically it's possible. It has a lot of potential difficulties. If you want to do that whole pipeline.

A

Welcome any user feedback, you can install it it's available and managing update Center. So you can just find it and if you get any issues that is, have wishes in this project, so please try it out, and let us know that.

B

Looks very cool actually yeah. It's.

A

A new feature coming.

B

From kubernetes, which is cool and in Yammer.

A

A

Changes in Jenkins and shipping changes okay. So we answer more questions and we still have ten questions to answer so yeah. Would you like to go to continue for another? Maybe fifteen minutes so that we have answers on the record? Sure?

A

Okay, let's do it and thanks to everyone who is still with us.

A

These questions, if you have to do so, the next question is, it will be easy to maintain Jenkins file and not the detail. Files have a should be sender but keeper all the flow and James file.

B

Yes, and no so I would like to show you, because I actually have an example of this from the last meetup that we did with how it looks like when you're wrapping these Jenkins files, so I'm sharing my screen I'm in the companion repository for the other demo, so it had two other companion repositories. So I actually had my my seat, repository with all the jab to yourself and then I have my project repository, which was a mono repo just for the purpose of the demo, so each of the folders they have a Jenkins file.

B

It doesn't matter that they are in the same repository because they are referenced individually from this job DISA repository.

B

So the job diesel repository has the supercede job, which reads all the job TSL in this folder and it has a folder for each of the pipeline's, so the auth pipeline, for example, as an author groovy, which references an auth pipeline job, it has a script path. So it's in the auth folder of the.

C

B

Repository and if I just move this to the side, you will see that if I look at the basic groovy, it's still references the pipeline repository and it uses a different script path. So sure this is. This is groovy. You could wrap this in a for loop and you could try to figure out what all the files are in the in the in the in the pipeline repositories or that was over here and then create. So you could generate the the job yourself with the job diesel, but I've found that this is easy enough.

B

So I just have my super seat job and then I have a seat. Job per pipeline.

B

I'm also not able to add multiple pipelines in the same chapter yourself job, because then it will just use the first pipeline that it finds you could use whether there are different job types in Jenkins. There's the multi-branch pipeline job, where you're actually adding an entire project. So if you're using bit burgers or something like that, then it says that for all of the projects for all of the repositories in this project, I will have a Jenkins file in the root.

B

So whenever I create a new repository, just assume that it's gonna be there and then Jenkins will automatically created for you and then, even when you start creating creating branches, feature branches, things like that, it's gonna pick it up automatically in Jenkins.

B

Yeah but then I would have my multi branch pipeline in jump to yourself, but I would then have one for the project in bitbucket or or other.

A

Okay next question: is there an easy way how to avoid is keeping characters from some advanced shell scripts, not only about general battles about pipeline.

A

C

Single quotes right, isn't the only solution, triple single quotes or triple double quotes?

C

True, even that doesn't really solve it, because it's still you're a language inside a language and.

B

Then, when you're generating jump do so that's generating chapter, so that's generating jump to yourself. You're right I've had 16 back slashes in a row, because I was nested that deep yeah. Unfortunately,.

A

There is no good way to do that: yeah Jenkins itself. It has some features which escape things properly well or sometimes properly. For example, shell step we will try to escape, they shrink, etc, but still all of it has a lot of limitations.

B

But but for the most part the multi-line string will help you a lot.

A

Okay, so the next question other process-wise: is it possible to arrange a workshop to practice such things together?

A

So, yes, organizer of Jenkins online without I, think you would be happy to host such workshop. If somebody wants such conduct, that and maybe Nicolai does, if you called Freud Martinez such workshops online.

B

Yeah, so we don't have anything like that in the pipeline, but also it would probably be a paid event. So, when I'm doing things for Fe code I'm actually on the job and I'm sort of this is borderline. What we're also helping customers with so I'm not entirely allowed to give away all of the business but but yeah. If there is interest in doing such a thing, then I can certainly ask someone if I am allowed, how much I am allowed to to do so.

A

If you're interested at least a shot to Nikolaj in Twitter, so it might be a public workshop, it might be a commercial workshop. But if you interested definitely it's a good thing to ask.

A

Okay, so the next question: when using pipeline use git checkout, we are instant to a single jenkees file located in a room to get source. How can we start our multiple pipelines in a single form.

B

That's a good question: you can create multiple pipeline jobs that reference the same repository in jabbed yourself.

A

B

You're not entirely able to reference multiple Jenkins pipelines; sorry yeah, multiple Jenkins pipelines from the same job in Jenkins.

A

But yes, it set in the open source commands. There are all options: I'm, not the trade. Oh yeah.

C

A

The way there are plugins which in simplified it, for example, remote file provider, plug-in and other things which can help you to this manager, multiple locations of objectives, files and pipeline repositories, but a multi branch is quite limited by default, I would say opinionated, but quite limited. Yeah.

C

Actually, I challenge the phrase, limited and instead say opinionated because I agree, it is opinionated it and it's intentionally so, okay, but yeah. There are plugins which allow to alter.

A

The behavior so, for example, to ensure a bacon I maintain a rock python is yellow plug-in, is also maintainer of remote file provided plugin for multi branch pipeline I mean if you ingest, you can try it out, or this case.

A

Routing so the next question can I fetch your job yourself from one normal HTTP endpoint. Instead of github I.

B

B

If you can get access to the file- and you can get it into your workspace, then you can reference it because it'll be in your workspace. So what I'm doing with the with the gift tag in the job DSL is just to clone out on a repository and then I have the files in my workspace. But if you did a thing like you, could you can, of course like create new files?

B

You can kept files, you can curl download files, which you should always do with indicators, and then you will get them in your workspace and then you could reference them as external files from the seek job diesel I.

C

Took from your earlier instruction that it's really helpful to have multiple files defining and so whatever technique, I use to get those multiple files in is great multiple files, rather than one great big monster file that defines every single job in the whole system. Yes,.

B

So change by addition, rather than change by modification, because if I have this one big job with all the customizations in it, then it's very likely very likely more likely that I break some other custom configuration when I'm adding a new custom configuration.

A

Yeah, that's right: yeah probably enjoyed this I could provide more different engines so similar to how a pipeline provides different sources, etc. Job decel could also support the additional extensibility mode, but I'm not familiar. This is a plug-in code base, so I cannot say for sure whether it's already supported or could be implemented, but if it's not supported, this is definitely something you can get to the plug-in.

B

Okay, but that's not necessarily a limitation of Jeff Diaz, although because, like once, you have it in your workspace, yet you have an external ease of which everything you can do to get there to get your specifications into your workspace like curl it from some location copy it from the disk. Anything that you could do in Jenkins before the build step. That is a process, job dsl script.

B

That will let you read any job dsl into a seat, jump ism, yeah,.

A

B

Correct: okay,.

A

So two questions at once. So the next question is: we have a little lunch number of freestyle jobs that all the D in job they said and we would like to move to pipeline jobs. What would be your strategy? I.

B

Would look at similarities in the DSL and then I would.

B

Wrap the pipelines and add them and then I would verify that they did the same thing either by looking in the configuration of the jobs which become a bit tricky because you're still like comparing a pipeline to an actual freestyle job that you have interrupted yourself.

B

A

Would you suggest a using shared libraries during this mutation process.

B

Yes, if you, whenever you have so like the first time you make something you don't know what it's gonna look like the second time. You make something, you kind of notice, a pattern and the third time you should be able to generalize. So if you have an overall way of working in your company or wherever you are that we always check out a repository, we always clean our workspace. We always end up pushing locks somewhere.

B

Then as much as the general stuff, you can put it in a shared pipeline and template the tiny parts that change and and work with that there is shared pipelines, documentation with a couple of examples that show how you can actually create quite intricate custom pipelines, I, just parameterize them and then ya create a number of different jobs, very easy, using these shared libraries and using the templated their jobs right.

A

And also it pipelines you can test them, so we partially answered the testing question before, for example, if you want to test pipeline libraries specifically, we have a repository in the Jenkins project, Genki central pipeline library, so basically it's a park line lab which we used to test Jenkins and plugins and other needs. So you can see that there is a lot of common steps.

A

Wish wish a between our pipelines, and here you can find examples of tests which have been written using Jenkins pipeline unit, specifically for building plots, which we use to me great help I plants. Well, we emigrated along to go in 2016, but still will be extend to this pipeline library and add more and more tests and tests and features for it. So you can check this repository if you just want to see a real world example of pipeline library with test coverage, and there is also a pull request for integration.

A

Testing is changeful runner not finished, but it should be some way here.

A

Okay, so we're getting close to 30 minutes for questions left. Would you like to finish that, and we can continue? Are you if we can take the four questions? Okay, so yeah, we'll just finish, exist queue and for the rest, it was follow-up, nursing channels.

B

Yeah, please continue asking questions on. There was the slack asked on Twitter like love talking about this stuff.

A

And probably next time we will go meet up for a visual presentation, just a discussion or questions session. Okay, wait growing into the presentation, yeah right, so the next question of wait when you're at a job they sell to you eat. Do you still need to manually run DC job, or can you run like it whenever the job they sell the power bit? Yes,.

B

When I add adaptive cell to my kit, repository I need to manually run this each job, but that's because I didn't configure any triggers, so it doesn't trigger the job on changes in my source code management. But if I configure the trigger I could either configure to look for changes every second minute. That's a bit expensive. Otherwise I could configure it with a web hook to my source code management and then, whenever my search code management changed, it would fire an event to Jenkins and then Jenkins would notice.

B

Oh, this job needs to run and then it would rerun my job DSL CJ. You should totally do the web hook trigger thing. But if you like me, don't have your own github or your own bit pocket running. Then you don't necessarily know where your code is actually going to be. So it gets hard to configure up front.

B

And I also don't have a Jenkins running right now. My Jenkins is like all my jobs are as code, my Jenkins. This is code. So when I leave my Jenkins I started and then I turn it off afterwards. Yeah.

A

Thank you so yeah the next one, how high how drinkers can discover parameters in jinks well without finding a job once so it's an architectural question.

A

So, firstly, it really depends on the Irish pythons and me you stripped it to the credit, because they're processed a bit differently, but yet so long didn't read. Jenkins does a best-effort of discomfort and parameters using abstract, syntax tree. It may work on my node and depending on the result, if you Pro it will definitely catch parameters after the first run. So personally, my recommendation is, if you really have to have pipelines with parameters, don't rely on the tester.

B

A

B

Can do some things where you trigger the pipeline and then you build into the pipeline that it will early exit if the parameters are not provided um but yeah there. There is no good way for Jenkins to know upfront what the job is doing, because it actually doesn't have the job before it pulls the job and reads it. So there are some edge.

A

Cases, for example, you can put parameter property in a pipeline library. You should alter dynamically using graph or whatever I'm, not sure whether I would recommend this a use case and a good conscience. But technically it's possible I.

B

Love that part, technically, it's possible know that it's there yeah.

A

Okay, so the next one out how to Clemente job the sender from the technique. My job changed Monday, since it was generated by this job of the parameters, has been added after the first run of my job, so I guess it's a follow-up of these keys.

B

Never allow anyone to make changes to the configuration of a job that you have configured in Jeff Diesel. If you need to make changes to a job, your configure to Jeff diesel you're, doing it for development purposes, and then you shouldn't do it on your production instance you shouldn't hack around on it.

B

Then you are creating the job in another place where you have rights to edit stuff and then you edit stuff and then afterwards you make the changes in version control and then you rerun the seek job and you have your changes in production right.

A

And we actually working on some arrests for that. So you can see that if you go to the change log, oh jinkies, you can I see a lot of system, read references there, don't be you I, thanks to Tim Jacob and other contributors who work on that. So I already is to have redundant system configuration job configuration and agent configuration UI.

A

There is a blog post which is stitched right now we are getting there and, if you're interested to participate again, we have online cut rest early next week and HT Lydia I did only UI is listed here. So we invite contributors to work on this story so that ensure that nobody identify configurations I, contributed by configurations.

B

Yes, because yeah the reason I want to go to configuration this code I like had it on the slide right. The configuration drift I want to know when changes are made by who and why and have it under I, don't want the rend I'm hacking around yeah.

A

Oh it's coming soon and if you use weekly releases, you can already try it out. Okay,.

A

C

Happy to deliver the good news, even even better, not just can try it out, should try it out in weekly releases, because Jenkins 2.2 30 to 35 is next LTS and so good time now to test it good time now to experiment with it. So LTS is coming with this capability. It's not here yet, but it's comical awesome.

A

Well, there will be some incremental changes, so I think it will be a fully analyzed by September, but a lot of changes are already available.

A

Okay, so the next question. Oh it's not the questions just comment, but yeah.

C

A

Think we're done yeah, so yeah thanks to everyone for asking me questions, yeah going to be a bunch of them, so we'll publish the recording, you will publish all the questions, etc. If you'll take some time to process that, but the recording should be available in 24 hours and yeah. Yes, that's it. If you are interested to share any feedback, I mean we will appreciate that because it helps us to improve our meetups. That also will also share feedback with Nikolai so that we can improve the presentations as well and yeah.

A

Thanks a lot to Nikolai for doing this presentation, it was really great a lot of content to study, and hopefully it was helpful to everyone who participated thanks.