Jenkins Online Meetup, 20 Jul 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Online Meetup: Pipeline as YAML Plugin Introduction

Description

In this session, Aytunc Beken will demonstrate Pipeline As YAML plugin usage starting with basic to advanced Pipelines. The plugin allows defining Jenkins Pipelines in a declarative form, using YAML files. This is an incubating project, any feedback and contributions would be welcome!

Agenda:
* Introduction to the plugin
* Basic Pipeline
* Environment Variables / Options / Agent definitions / Post Actions
* Complex Stages ( Inner / Parallel Stages )
* Steps/Scripts Examples with Pipeline Libraries

References:
* Slides: https://docs.google.com/presentation/d/1J3EMR88K1hHY9zUjTWfiLq2Zcs1G4yaxKo1bwau_0ac/edit?usp=sharing
* Plugin page: https://plugins.jenkins.io/pipeline-as-yaml/
* Demo repo: https://github.com/aytuncbeken/pipeline-as-yaml-tutorials
* Meetup page: https://www.meetup.com/Jenkins-online-meetup/events/271691294/

About the speaker: Aytunc works as an Expert DevOps Engineer. He likes to contribute to Jenkins Community in his free time.

A

Hello, uh welcome to jenkins online meetup today is july 20th, and we will have a pipeline with yaml plugin introduction by twitch uh bachmann on the call um and uh this one uh webinar.

A

We will mostly focus on demos and after that we will have a long q a session, and if you are interested to know more or to discuss something after they meet up, you can stay online. We will grant everyone voice permissions and we will be able to have more discussion.

A

uh Could you please switch to the next slide? Okay, uh just to quickly introduce uh jenkins online the job? This is a community driven uh event. Basically, we organize uh meet up uh to speak about various aspects of jenkins, including using jenkins developing jenkins. We focus mostly on various key studies, success stories and we invite everyone to participate during this meetup.

A

So please uh use pony to ask questions and uh please share your feedback, because one of the main goals for these meetups is to actually get your opinion and your inputs about uh how we could improve um example. In this case, a pipeline is employing game or how we are going to improve junkies in general, and we will appreciate all your participation uh in this meetup um again. The main focus uh is to do hands-on demos uh today so the recipient for a lot of live presentations, and we are always looking for speakers.

A

So if you want to present something about jenkins, there is a link uh jenkins, slash events online without speaking, and if you want to share anything about your use cases about your plugins, please you're welcome to do so. Thanks to our sponsors, secondary delivery foundation and cloudbees, they help us to run the infrastructure and recover for running this method, and I guess that's it from me so.

B

A

B

Yeah, thank you very much for the introduction. So uh thank you all for joining this session. I am my teacher can so I have been working the devops engineer and also I have been using jenkins for the last 10 years, so I can say that I am at devops and jenkins interesting.

B

uh You can just contact me if you need about the details of the plugin from these uh social medias. So during the meetup, you can always ask your questions with the zoom q a session and also after the meetup. You can check the pipeline authority authoring seek website for the for like weekly events and also decisions on the pipelines and also after the session. You can use this feedback phone to provide your feedback for the session. It will be appreciated.

B

So today is uh I'm going to introduce uh the pipeline as yaml plugin today. So our agenda is that I'm going to provide some details, how it works, uh completed, features and the plan features for the future and also I'm going to switch to the hands-on still with some of the practices that we can. All you can use your in your pipelines so uh python. As you know, uh there's one important situation that currently this plugin is in the incubation stage. So what does it mean?

B

A the changes on this plugin may rely in time or can affect the usage of the uh plugin. So that's why we always encourage people to use this plugin in not in mission critical or production like environments, but mostly uh please use it in like development or stage ones for that uh we do not want to affect anyone, uh pipelines or working and once so pipeline is zimmer, enables defining jenkins pipelines in yaml format.

B

Vmware is very well known for mapping these days, so this plugin can be used in multi branch pipeline jobs and also it can be used in the pipeline job as a scm or in a c clip in the editor itself, I'm going to demonstrate how it will be used.

B

Also from the link you can reach to the website of the plugin itself, so how it works. uh Plugin converts your mobile definitions into directory pipeline format in the runtime to provide more details.

B

Conversion happens after you check out the yaml definition from scm and it converts to the declarative format and it injects into the flow of execution before running the pipeline itself. So you can think this plug-in as a uh runtime converter of yaml definitions into the declarative pipeline formats.

B

uh This is, of course, uh also same in the when you define your pipeline in the editor, so it is uh again converted into declarative pipeline formats in the line time itself uh completed features so until the latest release uh dictative pipeline directives that are listed below is completed, which means that you can use these directives in the pipeline and xiaomi plugin, and also uh in the other concept.

B

There is a converter for converting pipeline example, definitions into declarative pipeline and also validating this converted take the two pipelines. The reason behind this conversion is to provide some.

B

Validation before going for the real implementation of the pipeline smooth, so you can easily convert your yaml definitions, take the pipeline and see how it's going to be worked in the real pipeline.

B

So this conversion helps us to use all the predefined steps or directives in the plugin itself, so for other plugin developers or for all the other custom steps. You do not need to define something special in your plugin, so every step is defined on the pipeline syntax helper page, which I'm going to show that can be used in the plugin itself.

B

Plant features for the future, so uh currently only matrix directive is not supported yet, but it is in the plan. So probably in the few next releases, we are going to support it and also another design feature. Is that converted from declarative pipeline to pipeline azimu? uh So I believe this will be uh so helpful for the people who wants to use the pipeline azimu with the children dictating pipelines.

B

So it can be easily converted to yaml formats and also I'm planning to develop some intellij idea plugins, which will make it more uh useful for the defining pipeline, specific attributes and keys in the intrigue itself.

C

I don't see if I could uh jump in real quick. This is liam, um so the uh plug-in for the intel json is awesome. The question I have here is about matrix, why? Why is it not uh in yet just kind of what was, if you're, going to talk about that at school? I just want to was wondering if that's a.

B

So uh especially, the reason is that I never use matrix so first, I need to use it in the deck by trying to understand well uh sure I had no experience with the metrics usage in the dictative pipeline. Okay, so that's why I didn't do it yet, but of course, as oleg mentioned previously, uh all contributions are welcome. So if you have some uh experience with the metrics like the pipelines, you can always contribute to this plugin. Also excellent.

C

Just I was just wondering matrix is also the most recent edition, so it's kind of I would understand why it wouldn't uh you wouldn't have exposure to it yet so.

B

Yeah thanks uh so yeah, uh so I'm going to switch from the hands-on tutorials uh before that. If you have some questions, you can ask uh what I'm going to on the hands on tells that basic pipeline uh usage of mine variables, options or agent definitions, and also I'm going to show some complex stages like in and parallel stages, and also some steps and secrets examples.

B

I also defined a hello world repository in the below link, so you can always visit this repository and see the uh all included pipeline tutorial in that repository. So you can always reference that.

C

So I yeah there is one question from the channel um about uh what the motivations are for using yaml before we move on to the demos. Just um what are the benefits and motivations for using uh yaml as opposed to just declarative pipeline as it exists in groovy.

B

Yeah, of course, like I mean uh I just like the yama definition, because you just wrote.

B

How can I say less and also like yaml definitions are very widely used in the devops world, so I believe it will be much more easier for everyone to understand the email definitions, because the data syntax has its own decorative format, but of course it is optional. So I just love yammu.

B

C

Familiarity you're saying at least in one sense: it's familiar familiarity for people that are already in this world yeah using yammer.

B

Yeah, definitely I mean: is there any application that do not support yemen in the world's world?.

C

Apparently, just jenkins there you go.

A

Well, not only jenkins uh yeah, we use coffin and other things in other cd platforms, but actually it's a good time to launch the poll, because we would like to get feedback from audience about what languages would you prefer to use and yeah? Well, the pole runs. We can actually start switching to them as part yeah. Again, if you have questions, uh please uh don't hesitate to ask in zomcoin a um and yep. Maybe we could answer a couple of more because before we switch to demos, okay, so the first one is about contributing.

A

This is the open source? uh Is the plugin open source so that people can contribute to their project? If so, how to do that.

B

Yeah, of course, I'm sorry so like, of course, this is like open source plugin, so everyone can easily contribute on it. Also, you can create issues on the uh python xml plugin github page, uh so every feedback is appreciated. Also, uh we will resolve that if you can also provide your usage feedbacks, because we try to keep it as much as useful for the other one so feel free to ask your questions or create issues or contribute.

C

And there is one other issue when it's a little bit of a detailed question. But when you go to replay a build when you're using a yaml pipeline, does it show yaml or does it show the transform declarative, uh groovy version of the pipeline.

B

Wow, that's a good question. I never checked that. Oh.

C

We haven't checked it: okay, good yeah,.

B

C

That's uh that's a feature to go. Take a look at all right.

B

Yeah, I need to note it.

C

I'll I'll keep I'll keep track for you go ahead.

B

Okay, thank you very much. Okay. So now I'm going to switch to hands-on experience to solid tutorials, so.

B

Okay, so I have just started an jenkins instance and I also installed the python xml plugin into my jenkins itself. So what I'm going to show today, I'm going to start using the sorry.

B

Let's say tutorial1 and I'm going to start using with the pipeline job. So after a few examples, I'm going to show or demonstrate how to you can just define in the multiple branch. So that will be easy. uh Okay. So when you install the plugin and when you create your pipeline job, you will see that there's a definition.

B

Of course you can use the pipeline cpu for secret from scm as usual, but there are two other options which is pipelines yaml and the other one is pipeline is yellow from scm, so pipeline is yaml from scm is similar to what we had had before pipeline secret from sem. So you can define your uh any type of uh scm repository and you can just provide the path of the jenkinsfile.yaml and you can use it, but for the easiness of the uh usage, I'm going to use the clip panel for today's tutorial.

B

So just I want to start with some simple uh definition of checking out the code from the repository and to maybe some steps. So what we do is that we just define our pipeline. Then we use this uh yaml syntax. Then we need to define, of course, agent uh sorry uh for that dimension. So it's quite important.

B

uh If you visit the webpage of the plugin, you will see one example of each directive in delete page, but also you can just easily go to the links and see all the different variations of the uh implementations.

B

For example, if you want to go to, if you want to see the other implementations of agent definitions, you can easily go to the link and you can check the different variations of agent definition. So all these files are installed in the test resources directly uh so uh also, for example, we I'm going to demonstrate environment options and other different types. So let's do together. So I'm going to use this agent any definition, so it is similar to direct the declarative syntax, which we define agent as any.

B

So I'm going to use any definition after I defined my agent, I'm going to define my stages. So what I'm going to do, I'm just going to use stages key and then I'm going to define my stage, let's say checkout so for the stages. Also, as I said, you can just check here and see all the different kind of stage definitions.

B

I try to implement every possible scenario of these stages, so you can easily find, I think, what you are looking for. So let's use the pipeline syntax, which I want, which I mentioned before so using the children's test, is possible in the pipeline.

B

So what I'm going to do, I'm going to find the checkout command and I'm going to so leave this one?

B

Not this one, not this one, ah this one! Okay! So I'm going to check out my code yep, I'm going to check the master. Everything is fine. So what I'm going to do is that I'm going to copy this step, then I'm going to define as a step under here. So what I'm going to do is that I need to define my steps.

B

Steps definition are used as las, so you can easily define every step by defining as its yaml array. So I define my steps and just I wrote my git checkout step in here, so I'm going to apply and I'm going to run it. So the expected behavior is to check out the episode.

B

Let's run, it check the console.

B

As success, so we just did, I will first check out with the pipeline so.

C

Quick questions, usually in declarative, the the checkout just uh is part of uh the stage is that is that not the case in general, for this or yeah.

A

Oh excuse me the.

C

Way, we've done this, that's only in multi-branch pipelines, my bad.

B

C

B

Always forget continue, I'm sorry, I'm going to show that no problem, so I'm going to define my second stage will be something uh uh I want to build my code. So I'm going to define my step again and I'm going to time. Sh maven clean, install, also sh another step defined in syntax.

B

So, as you can see, you can use the le step here.

B

B

So let's run our.

B

B

So that's a good example, so uh what I need I need to get to maven. So before uh the presentation I prepared my uh maven 2 installation, so I need to check the name of it. So, let's see yeah, I have a maven installation here called default.

B

So what I'm going to do is that is in declarative pipeline. I need to get my tool as defined in deck data. So what I'm going to do is that I'm going to use tools and the tools section. I can easily define my uh tools section uh so, but before that I want to also show something. So if you are not sure about the declaration of the tool, you can just easily go to the pipeline syntax helper and you can just get your main one yeah, that's it maven and default.

B

So what we are going to do, we are going to convert it into the yaml format.

B

Ok, so it should work.

B

So it finished successfully, so it was just hello application.

B

Okay, so I next in the next example, I can demonstrate the inner stages.

B

So what we can do is that normally we just divide the stages into some sub stages, so what we can do is that maybe uh build and test or lace, let's say maven, so I'm going to delete this section and I'm going to demonstrate how we are going to define sub stages in our stage. So especially, it is very similar to declarative usage and also, as I mentioned before, you can easily see all the usages in here. So this is the example for using inner status.

B

So, under my stage definition, I also again defined stages, and after that I'm going to define my other sub uh substage, which will be built. Then I'm going to write this c clip or step as a c clip so also you can always use the similar cyclip tech, which is similar in the deck delta pipeline. So I can just easily write min clean, compile and also I would like to show one example about this.

B

So if you want to write some more complicated uh steps or c clips, what you can do is that you can use this secret multi line. Then you can just easily write your blue sections here. So that's another way of usage.

B

So, okay, I will compile my code and then I'm going to define another stage which will be test, I'm going to use it as a step stage and even test.

B

I hope I didn't oh.

B

So, let's go for.

B

It uh when you check the pipeline uh flow, of course you cannot see, but if you are using the uh blue ocean plugin, you can easily see that this build and test is the sub stages of the neighbor.

B

uh Let me check my examples. Okay, just a second.

C

Okay, so can you make it the font just a little larger, just do a command plus or something to.

B

Just a tiny bit yeah.

C

Cool that's great, just a little bit larger, but great thanks. Okay,.

B

So all that yeah.

A

B

You uh I'm going, I want to demonstrate the options or the maybe the environment uh definitions in the pipeline declarative. So what we can do is that, of course, we can just set some options for our jobs, which also can be fined here in the decorative directory generator. So what I'm going to do? I just want to set this job as disable concurrent builds. So you can use any definitions here, so I'm going just going to demonstrate this one, which will be just simple, so I clicked- and I generated my dictionary.

B

So what we need to do is to convert this into yaml format. So I'm just copying this function here then I'm going to define here options.

B

Disable content pills, so you can always define other options under the options key with yaml arraylist and also you can find the other options definitions here so yeah. I just want to disable the content field. So I'm going to apply it, I'm going to end yeah, it's quite picky.

B

So it's running everything seems fine, so I'm going to check if it is set or not- and yes, so it is not allowed to run. Concurrent builds. Okay, that's cool.

B

So what I can do, I can just get some maybe credentials and pass it to my uh maven command or something else so like you can just think about as a deployment to somewhere else. So my examples, maybe won't make sense now, but it is all about showing the usage. So I need to.

B

So before the presentation.

B

So before the presentation I just created my credentials here so so you can go to my credentials so assume that you defined some credentials or yes, so you have some credentials to use so yeah. My custom credentials is just basic, username and password credentials, so I'm going to demonstrate how to use it. uh Of course, anytime. We can just get the help from the pipeline syntax, so oops.

B

Okay, so what I'm going to do is that I'm going to use with cadasha step to use or get the card actions from the financial store. So I'm going to.

B

Use a name password and yeah this credentials so generally, so the tricky part is here that you need to use this uh part between the commas. So what I'm going to do is that I just want to use my credentials, so I will come here with financials.

B

I will pass it.

B

Yep and then I'm going to uh pass this credentials as usual to my maven commands, so I know there's no need for that, but I just want to demonstrate it.

B

So I assume that we are passing some username and password parameters for compiling or testing or deploying your artifact into somewhere else. So, let's run it.

B

Again, okay, let me check using the password.

B

Oh sorry, my bad for that the finest so as you will remember the in the declarative syntax of uh pipeline, when you use the with credentials step, you need to open a code block. So for that to be implemented, we need to write here secret and we need to define our sh commands here. So unclean compile username, I'm just going to use the username.

B

B

So you will see that this parameter is passed as a secret into my command. Also, another similar step, which we can use or mostly use, is that uh with emv section. So what I can do is that I can just easily use vtmv so to be sure, I'm going to use the in one of the level definitions. So maybe I can do something like that, like yellow.

B

Okay, so what I'm going to do, I'm just going to take this part, is again and I'm going to define it in my pipeline so with emv. Yes, okay,.

B

Again, I need to define its own scripts part to make it one so.

C

A question there for you do those does that need to be script or can it just be steps.

B

uh It needs to be secret because, uh as I remember in these step definitions, the code block accepts also gurubi syntax or google language. So that's why I implement it as a secret, but of course we can always change step, but I believe secret will make more sense, which I thought, okay, uh so, okay, I'm going to run it.

B

B

See, oh, what I couldn't dissolve: okay, okay!

B

We can just okay, so for next tutorial I can show you the um maybe parameters, part or, let's define with one yeah uh so as you might should be. So let me.

C

Just jump in here for a second at least one other question um related to the you're using the script. uh The declarative uh directive generator in this, uh the snippet generator is. Is there some plan to make this uh generate yaml as well or is? uh Is that yes? Okay? So that's that's on the list somewhere at least is something you'd like to do.

B

Yeah definitely I I'm planning to do that, but uh it's just a bit uh blue part for me. I don't know how to generate this. So probably it will be just in the next next next releases. Sure.

C

I don't know what.

B

But of course it will be very useful because I know that this kind of conversion is not very useful.

C

B

You're welcome uh so, okay, I'm just going to move out this. I don't want to get alice okay, so I just want to demonstrate on the also the run definitions. So, let's go to the old part time page and you can see that we can always define the run definitions in the under the stage like it's in the decorative pipeline.

B

So I just want to use it in here. Let's make another stage here, so let's do deploy one.

B

Punch master and also, I would like to do something steps and then maybe deploy something.

B

So I'm going to measure it okay. So now, when I run it, this will be skipped because we are not using the multi-branch pipeline, but this is a demonstration how to use the run conditions in the pipeline itself, but uh I'm going to also demonstrate how to define this in the multiple edge pipeline. So yeah, you will see that this stage deploy is skipped to the development condition. So that's another usage for it, and also we can just define some other environment variables, which is quite similar to other technical definitions.

B

So I'm going to define some environment, and I will let's say that my server and.

B

B

So I just want to, like I don't know, kill my myself.

B

Okay, so as still we didn't see the change on the deploy section, but we are going to see it in a minute. So what I'm going to do? I'm going to uh commit this, or maybe I can just use the the one that I already defined in the repository so in the store repository there's a pipeline directly. So this is two different uh zinc, nufile yamas, so one of them is about a very similar usage of the things that I showed before you can just reference these usages.

B

Then you always want to see some examples uh and also there is another jenkins file, definition in the multivillage part, which I want to demonstrate it. So, uh as you said before so in this yellow file, as you see, we don't have any git checkout sections, because multiple edge pipeline will do it itself and also in the multiple dash pipeline. We are going to use this one condition and we will see that this deploy stage will be locked. So I just want to get my code depository, so I'm going to define a new job.

B

Let's say w 2, it will be multi-block job.

B

B

Yeah, this goes all the branches.

C

B

What I'm going to do is that I'm going to search the select the genquil file as ml and I'm going to provide the path of the jenkins simo file. So it will be pipelines, multiblanche and jenkins.

B

Fire I'm going to save it, so it's going to find the branches. Yes, we found the file. So when you go back to your job, you can see that master is already start working and we will see the blocks.

B

At the end of this job, you are also going to see the deploy section is running, so it is all about the line condition. So yes, as we can see from here sorry also deploy section, is working.

B

Maybe just one just one last example, so the usage is also same in the pipeline itself, so you can just easily configure your pipeline from the pipeline as you from scm, which is very similar to multiple launch, um so you can use it.

C

That would get you the automatic checkout and some of the other behaviors that you get there right.

B

Yeah definitely, and also one last thing I want to show that is the converter part, so you can just go to the pipeline syntax and you will see the uh pipeline is example converted. So, as I said, uh currently, it is working one direction, so it converts pipeline and gmo into the technology format. So if you just paste your yaml definition, you will get the dictative definition of your pipeline.

B

So if you are not sure of the some definitions in your enamel, you can just easily check it from here and see if it's going to make sense or not, and also after uh defining your technique or sorry. After converting your pipeline, you can just validate it and very detailed uh response, so it's valid. So this is just for like preventing adults before running the pipeline. So and, as I said in the future implementations I'm going to implement the bidirectional way of the conversion, so uh very.

C

Cool very cool I.

B

I think I demonstrated lots of things I mentioned. uh As I said, you can always find more and more and more details about the usage in the pipeline as yaml plugin web page, and also I'm going to keep this repository also for reference. So you can just easily check the cml definitions for your requirements, so that's all from my site.

B

Thank you for all listening to me and also I'm happy to answer your questions.

A

Really, we've got uh quite a number of them, so liam, would you like to drive the connie.

C

uh I can I can at least do some of that. um Let's see here so uh now, go ahead, keep it for now. We might need to show some things if you want to switch back to the slides. um If you have links there for uh the the uh example uh yeah.

A

That'd be great to have.

C

That up there, while we talk for a minute um so there's a question. First of all, I'm sure everyone's very excited about this. uh When will this plug-in be ready for for production.

B

uh Thank you. uh So we are looking for hot for that. uh We are going to do some. Maybe major changes in the next weeks, but I believe uh also it depends on the jenkins community itself. uh I believe it will be online in maybe one month or two months. I don't know, but we will trying to do it as much as fast.

C

Basically, but this is a volunteer organization right, so it depends on how much participation we get right. Yeah.

B

Yeah, and also like we are, we will be very hap grateful if someone also can help us contributing to the change to the plug-in and like applying changes with us. So that will be also great.

C

Great okay, um the other question, at least one of the other question was: um let's see here: do you? Is there any performance difference for using yaml that you've that you've been able to measure.

B

I haven't experienced any problems about the performance itself, but I didn't do any performance tests. Okay,.

C

B

I believe you won't have any performance issues, because the conversion is really quite uh simple, so it is just about passing yemo and converting into declarative. But it's a nice question. I will do some performance checks and try to find out some values.

C

Okay, so okay good good! What about um so? You showed um uh the agent any there. uh Do you I'm? Assuming also that that docker docker agents and such.

B

C

Supported whatever the usual agent uh blocks,.

B

Definitely yeah also, let me show it please here. So if you check the the page of the plugin, you will see that there are different definitions of agents. So, in the current release we have the agent packet and decker file implementations, so you can just easily define your deck using the keys necessary for defining this stacker image usage and also you can just use the docker file also and also other default users, just like label note, and none is also possible.

A

B

One related.

A

Question in the list about kubernetes plugin, because plugin is famous for its complex configuration so.

B

Why it would be supported, uh let's edit, into the planned features? Yeah, okay, okay, so.

C

I'll do another thing to add for the feedback cool.

A

C

A

Plugin will work this if you define it as cloud configuration right now, so the only problem is is a more complicated definition. When you define container and basically put a yaml configuration right inside configuration, so it would be yaml and yaml and uh yeah. I don't think that current syntax parser would support it correctly. Well, you can put the mls string, but it has a lot of limitations.

B

Yeah- let's see I don't know how to implement, but I will check it definitely.

C

Okay, uh does this does does? Does this? Do the yaml uh pipelines work with the configuration as code.

B

Yes, so if you install the python xml plugin, you can easily use it, but I need to check if there's a special definition, I'm not so much familiar with the configuration scored, but I will check definitely okay. So we need to look at that all right.

A

So yeah right now it will work well because pipeline is yaml, basically has no global configuration, so you install the plugin and it just works and you can benefit from our features. For example, you can define secrets, you can define agents, clouds etc using configurations code and just consume them in yaml.

A

So definitely there is a lot of uh coexistence between these features and maybe eventually we will be able to put yaml job configurations right inside jkusk. So right now it supports the job they say, but in principle we could put yaml but yeah. It's an implementation detail so.

C

Right yeah cause, so you have you have job dsl in you can have job dsl inside of there and then define a pipeline inside the job. Dsl.

A

C

Which is a little it's a long way around to it, but that's that's really just.

A

Yeah I'll paste the link to the chat uh to what I'm talking about. So there is a way to create seed jobs and define jobs. Basically right inside jks configuration right and yeah later. When we have uh pipeline with yaml, it would be great to have support so that people put yellows there.

C

So, let's see here um underneath the covers, though do you have? um Is there a schema, that's like pre-generated for the the yamo or that someone could go and pull out or is that something that uh that we're still working on.

B

uh The the schema will be available, after probably defining the intellij plugin, so I'm just planning to define a schema for the pipeline definition and also use it in the intellij and also use it in the uh the jenkins itself.

C

Okay, so it's still in progress all right, yeah, um let's see someone that was asking about whether or not this solves problems with the in with uh escaping characters and quotes, and I I would assume that's.

B

C

B

But uh it's uh you need to be a little bit careful about that. So maybe I can show something so okay, so let me just remove some parts.

B

Come on, let me find a good example for that. Just a second, let me check. Okay, uh maybe I can demonstrate something: okay, with crashes will be fine. Okay, so uh you need to use double quotes if you are using some steps with spatial yaml syntax like here like right.

C

B

So uh we're using these, uh you need to use this thing. Double quotes at the beginning and at the end, so that's the only escape that maybe you need to use in the other parts. You can just also use like uh double coils if you want to define, but also you can just leave them as alone, but uh this is the only situation that I experienced.

B

So if you experience any problems with escaping collectors, please definitely open an issue and let us check it. Okay,.

A

One of the advantages of yaml format is basically you're not limited only to quotes, because you have an opportunity to use multi-line syntax yeah to work around using too many quotes. In some cases.

B

Yeah like, for example, here in the steps definitions, you can just use this multi-line definition like here.

C

Wow, neat, okay, very cool, um and that's all the questions that I see on the list in that were uh that we haven't already answered so.

A

uh There are a few questions which we could still ask were they were they in the um the chat, as opposed to the key. The q.

C

A or questions.

A

And answers so, for example, one of the questions is about canon group with slm. Yaml definitions uh coexist in the same folder.

C

Oh right, sorry, I I was asking ask them for a clarification that was. I was a little unclear about what that was basically.

A

Whether it would be possible to put jenkins file and the yaml definition in the same directory.

B

Yeah, I don't think it will. I don't think it will cause any problems so yeah. Why not? It is just two files.

C

And I guess one of the other questions was: what are the? How does this work with shared libraries.

B

Oh, that's very good question, so yeah. Maybe I can just show the example because we you may need to define library, but so, okay, here's the louder usage. So after you define your library in the jenkins configuration, you can just easily use this library definition in here and also you can also check the other definitions yeah. But the usage is very simple: just define your library in the beginning of the pipeline and also the definition uh string is very similar already exactly.

B

Similarly, what we have in the declarative pipeline, syntax 0, so you can also easily define two libraries something else. So it's all up to you.

C

And I noticed that you have the uh the script uh directive there as well, um and that's it so that we can call out to so that you end up using the groovy syntax.

B

Right, okay, so, like uh maybe I can show it from here. Please give me a moment so there's a test for it.

B

I think it's here yeah, so it is oops.

C

B

Yeah, not the resources.

B

C

Did you want the resources to show it or no? No, okay, cool.

B

There are lots of just okay- I don't waste time for that, but.

C

It is supported, yeah.

B

Yeah, as you said, you can just use your custom steps in the secret definition. Okay, steps, yeah all right.

C

Okey dokey and their question: what about uh variable: interpolation, um doing dollar, sign, curly, curly, brackets, etc that that works? Fine right.

B

Yeah, like as I showed in the example, so you can just easily use this double sign with bracelets, so you can just use this valuables, which you defined in the environment or in the input section. So you can easily use.

C

This okey dokey.

C

um Let's see, does that make sense: okay, yeah now, if there were problems in the in terms of the the interpolation stuff like that, this wouldn't fix those, though right. That was what someone's kind of asking about.

B

C

It's probably worth uh this is the like. If the if the username there had a dollar sign in it, for example, or something like that, where there's.

A

A uh yeah that's right, there's those are.

C

I think you'd end up most likely running into the same issues right where you would, as you would in groovy,.

B

Yeah, definitely so especially it will, it will throw the glue exceptions because, as I said like in the conversion part, it just converges into data to pipe time. So you will experience the same problem all right.

C

This doesn't this isn't fixed if someone's having a difficulty stating something in declarative it. This won't necessarily make that that better.

B

C

Won't fix that problem for them.

B

C

That's fine! That's fine! uh Let's see here.

A

Yeah one question we had in the beginning of meetup is about uh the replay feature right.

C

A

C

Did ask about that already we that it's not, we haven't, actually checked it yet, but I put on the list to to that. We would definitely want to want to try it out yeah other portfolio. Can we actually can you do it right now? Can you just try taking one of the things that you ran and just do a do, a rebuild on it.

B

C

Take one of the jobs down the left, click on the number.

C

And then do uh what is it? Yeah replay uh looks like we get declarative, yeah.

B

We get the declarative, so what would you prefer? So I don't know well.

C

If someone wrote something in yaml, they'd probably want to see.

B

It on the animal.

C

Yeah, okay, so yeah that that might be a little bit harder to do. But um it's an interesting feature.

B

Yeah, let's see.

C

A

Okay, there are some limitations with that. I reported back on uh sunday because I hit a regression and a jinx file runner when I was implementing pipeline with yaml support. So there might be some issues with the extension points between replay and pipeline with yaml.

A

It's yet to be seen.

C

Right, okay! Well, uh I don't see any further questions that we can answer. Oh and uh I assume you'll have the link to the slides when we uh post this.

B

Yeah: okay, great.

C

Well, I can hand this back to you for for closing this out. I'm not sure where okay.

A

So yeah I stopped the show yeah.

A

So thanks to everyone who joined the meetup again after the recording uh you're welcome to stay online, so we can discuss uh more questions and topics of the record, and uh if you want to share any feedback with the speaker or the organizers, we ask you to join the feedback form I'll post them today or you can just stay online so that we keep talking about. It.

A

Meanwhile, say thanks to itunes, for the great presentation and personally, I'm looking forward to see this plugin in production as well. uh Well, just simply a big fan of group videos, but at the same time I think that having a yaml option is a great addition to the pipeline ecosystem and to the jenkins project in general. So thanks a lot for your hard work on this topic.

A

Thanks and again, we will appreciate any feedback, so try out the plugin if you hit something submit the issues, join the chats and share the feedback, because any contributions matter and good feedback is also a great contribution to the project.

B

Yes, also, it is important for us before going to the production version or like the released version, because we need to we want to cover as much as possible for from the community feedbacks. So please feel free to like.

A

Yeah thanks so and see you at the next meet up.

A

We are planning to announce it up to the beginning of august later this week, so stay tuned for the announcements and, of course the videos will be published soon. Thanks all thank you.

A