Jenkins Hacksgiving 2015, 2 Dec 2015

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Hacksgiving: Workflow Q&A / Demo

Description

This video was an impromptu Workflow Q&A and Demo session

See also:

https://github.com/jenkinsci/workflow-plugin

A

All right, I'm gonna go ahead and kill the music, which is what I've been streaming through in between sessions. um So I'm are Tyler just in case anyone comes on I'm, not mr. Jenkins. This is not what he sounds like, but I wanted to sort of have an ad hoc session. um Jesse I, don't know if you've met Martin before um Martin's been you know, working quite a bit with workflow um I've, also been playing a lot with workflow I thought it would be.

A

um You know, really nice to have a 30 minute discussion about you know: what's there right now, what's working well, it's not working well, etc. So Martin do you want to just you know, talk about kind of some of the stuff you're doing.

B

um Hello, yes, yes, my name is Matteo Jew and I've been using Jenkins for maybe three or four years and recently I was doing more complex job setups and I on on IRC people recommended that I use the workflow, so I've been learning it since the beginning of the summer and as I'm learning it. You know, I I try many different things that end up, not working or being the wrong thing to try and so that in the end I have you know a couple of questions and and that's that's it that's pretty much.

B

It I'm not building anything Java or a software related, but I'm building code. So hmm I guess that's the background. Information hey.

A

Jessie, would you mind introducing yourself just for the for the group as well? It's.

C

Not sure my name is Jessie, quick I've been I've been somehow involved in Hudson or Jenkins almost from the start, although not all that actively um I've been working at cloudbees since mid-2012, and during that time they've been working heavily on all sorts of things related to Jenkins core in various plugins and with respect to workflow. This is a project that whiskey and I started.

C

Did we start this March of 2014? You know they've been spending a lot of my time working on it. Since then,.

C

D

C

Enough, if you, if you want to start talking about specifics,.

A

It's a one question that um I know Martin and I've seen a couple. Others ask is kind of like how you know how much groovy can we use in workflow like I know, Martin was defining classes I've seen some other people start defining classes inside of workflow scripts and things like that I'm curious. What the intention like helpful featured of a groovy environment is workflow supposed to be yeah.

C

That's a good question and something that's not really documented, very clearly at the moment, I think in general you can use Ruby syntax, there's no there's no particular white list of things that are allowed, since we're close, it does embed the full movie. Runtime he'll use the regular groovy compiler, so in principle it would support whatever stuff groovy itself supports. There are them, and that does include things like defining your own classes, sort of using closures and that sort of thing there are specific gotcha.

C

So the the main, the main thing that people run into is that any anything that's stored, even as local variable state in your flow needs to be serializable, and the reason for that is that workflow builds are intended to keep on running even after Jenkins gets restarted so potentially days or weeks long, and for that to happen, everything that happens throughout the course of the script has to be able to be saved to disk and then reload it again.

C

So you can use custom classes if you want to you, just have to mark them serializable, and basically that means that you can store data structures in them, but you can't store things like open network sockets or something like that generally, any kind of heavy duty, computation or or things that would do I owe or things like that. Those are things that should happen as forked processes slavish, so you'd use the SH or bat steps to run those things.

C

So the idea is that the groovy script itself would just be for orchestration of things that Jenkins itself needs to know without it's, not a replacement for doing scripting or running built rules, or something like when probably the other most commonly encountered issue that we don't yet have a fix for is that if you call methods that take a closure and the method definition is part of groovy itself rather than your program, it won't work.

C

We haven't figured out how to solve that, yet so groovy idioms, that are something of the form, collection, dot, H or collapse, or something like that would just have to be re-written into the you know. So boring see style loop rather than using more closure. Sometimes does that start to answer your question.

A

For me, yeah um Martin might have more more. That is curious about her or anybody else on the call I just wanted to I figured. That would be a good icebreaker. So anybody else that wants to talk about workflow feel free to jump in.

A

And one other in the in the chat group chat thing I put a link to this etherpad, so I'll be taking some notes from this and other sessions with links in this etherpad and then afterwards. I'll try to make sure that anything that needs to get updated as far as documentation goes does get get updated.

A

C

Were there other kinds of issues that you ran into, that seems like stumbling blocks or that documentation was missing.

A

A

You're there still Martin.

A

Alexander would said demo, let me um them I, don't actually have a demo ready and you know Patrick's on the call as well. If either you know, Jesse, you or patrick has a quick workflow demo I'll go pick up the issues that Martin posted this morning from the dev list. I.

C

Think it'd probably start up like the the stock demo. That's bundled in the system. If people haven't seen it, I can sort of walk through.

B

C

Important elements of it, if it's useful, let me see if I can get that started, I, don't have it prepared right away, but I can get it really.

A

Ok, I'm also I'll put in the notes. Jesse has done a good YouTube session or two and I'll put those in the notes. After I dig them up.

A

C

I'm just trying to get a demo store until they take a couple of minutes for it to the fire up, since it looks like my doctor, demon is cold and needs to be worked up.

A

um So Martin's having some microphone trouble, um one of the questions that he did have that got posted to the mailing list um was about and they, if I can summarize for you Martin since you and I have been talking a lot about this and a lot of what Martin's been been working on Orient's itself around the load step. So like loading, another groovy script into the workflow.

A

The one issue that he linked from this mailing list post in the group chat, is about jobs getting and our workflows getting into an unkillable steak, and then I know the other. One was questions about using workflow from SCM with the load script and like where things should be sourced from when using workflow from sem and write.

D

A good summer, I correctly, okay,.

C

I, don't know about those things going into an unkillable state. I mean that's a bug somewhere, but I mean if there's, if there's some known way to reproduce that then I can fix whatever the problem in spy. Don't know if him, okay, I.

A

Think I think Martin's use case in the in the Jenkins death list. I think that is a reproducible thing. I'll take a note from this and I'll make sure that this gets filed as a bug been and that the repro steps works. Yeah.

C

Anything with the easy steps to reproduce utterly something: that's fixable pastry forward.

C

Martin says they did not know if the problem is because classes were not allowed or because I made a mistake, yeah without words.

C

D

C

You in this case, defining a class. Probably it needs to be marked, implements serializable. That's one possible problem with that script and not sure if them has anything to do with the actual problem that was encountered or not again. If that's reproducible do something either make it work or make the if the bill fail cleanly at some point, they don't know. If you have, the fusion would.

B

C

So, let's see so as far as loading scripts from SCM, there are a few different choices, depending on exactly how you want to work. Things are available now we have some plans for extensions for this in the future, so so the simplest mode is just that your script is types entirely into the Jenkins job configuration screen.

C

There is another option that sort of gives a simple convenience mode for a common case, which is that you want to load the script from a particular source code repository and run it from there. So that's the the script from SCM option.

C

So if you select that, then every time the build runs, it's going to check out the latest version of that source code repository load the script from there and run it as is so- that's that's suitable for, for some cases, um I think for most for most common cases, the best option is probably what was introduced recently, which is multi-branch support, and that means that you check in a script called Jenkins file as part of your source code.

C

Repository Jenkins automatically built any appropriate branches from that repository and you can use a one-line can I'll check out SCM that checks out the rest of the sources from that repository at the same revision as your workflow script. So, if most of what you're doing are all what you're doing is contained in this one repository, then this is the most straightforward way to define the script for it and to have access to the corresponding the other sources as part of the repository.

C

So this is available with the workflow multi-branch again and I can actually get screen sharing to work. I can actually show this running here.

C

See so that should have so that should be showing a Jenkins screen. Let me make that a little bit bigger this about that.

C

So in this case we have a job called CD and the configuration for it just says that I want to look for any branches in the following git repository and there's some other there's my other items on the config forum, but that's really that everything that Jenkins really needs to know, and so we have this. This git repository here as part of the demo that it has a maven project. Rly has a couple of maven projects and various kinds of source code and Miss in that, and the workflow script is called Jenkins file.

C

So this is both the identification of a buildable branch in the actual instructions for building a bridge. So this is the complete workflow script for building sources from it, and you can see that one of the first things it does is it grabs a slave called node. So that's this node block here. Everything that runs inside this block runs on a slave and check out.

C

Scm here means that you would like Jenkins to check out this complete repository at the same revision that that the Jenkins file itself is loaded from so that's sort of the typical configuration. If you browse to the CD Projekt, it sort of looks like a folder, then you get one child project for active branch in the repository so right now we just have a master branch because we have a lemonade, ranching development, and so the master branch is a complete job with its own history, and in this case we have one build that started here.

C

So it's it's been running her. This is sort of boilerplate stuff at the at the top, where workflow is just finding the Jenkins file that's supposed to build, and then it starts running your worthless scripts. It goes straight into a development stage.

C

It says that we're getting a new slave and we're getting work space on that slave to run on and then the checkout step is where we check out our project sources on to the slave and an accessible location where you can do things like run built on them here, I'm most of all, I'm doing is running the maven build tool.

C

And this mrs. run for a while and right now it's it's actually paused for input, so you can see that's asking for interaction as part of the console log. This is also available from the bill itself. You can see that's asking you whether you want to proceed or report the current stage version of the map um and there's also a is possible to see a list of all of the workflow steps that have been run this part of this bill. So it's not a HS.

A

C

Different things yep when.

A

When things are paused for that input like that, that proceed button thing, what's what's executing like what resources I'm I mean I kind of know where to find this for for documentation. But could you talk a little bit about how like this actually consumes resources or allocates resources on the Jenkins cluster? Sure.

C

So, while it's paused for input, it's not consuming anything on the Jenkins semester, it's not it's really just paused. It's not doing anything else. So we can see if we M, if we schedule another build of the master branch. So we'll just do it. Emanuel rebuild without source code changes.

B

C

You go to the Jenkins dashboard you'll, sometimes you'll see some things appear under master. This is when it's actually running some groovy code. Most of the time, you'll only see this actual executor, for this is real slave machine, with a numbered executor slot only when it has this this stuff running on the slave. That means it's actually using an executor slot on a slave that, as that workspace locked and this potentially running some external commands or doing something doing.

D

C

Real work, so you can see right now. It's um it's running maven, so it's going through some some maven tests at the moment. It's actually it's actually running two parallel branches, quicker tests and longer tests, and it's using two distinct slaves to run. Here. We have a mock slave 89, it's using two slaves to run tests simultaneously.

C

So we can see that we have the same. Workflow build is running on two slaves right.

D

C

They're, one of them just dropped off. That means one set of tests just finished. Well, it's paused for input. You should see nothing here, because it will basically no longer be using a slave for anything while it's waiting for input, and so that means that all of the executors will drop off of the executor widget. So.

A

Now it's just a question from from Owen and the side roads. Just you mentioned that um there's sort of a project that's going to be set up for each active branch in the source repository. What like what defines active branch here.

C

Just anything that would be listed in the if you type the gift branch command, for example, that's a assuming that you use the default configuration for this gift branch sore, so you can also ask it to you only pick branches with certain day or something like that by default. It just looks for any open branches. So if you, if you merge a branch and then delete it, then it it's gone from the list of the corresponding french project goes away automatically.

C

It's also possible newly introduced features that I think they have it in a bit move in here who do not just have it installed currently. But if you go to the available tab.

C

And install branch source plugins that should be.

C

Trinity asking for credentials plugging update that probably doesn't actually better. um If you did that, you might need to restart this to work. Actually you did that. Then you also get another option which is creating a single folder that automatically creates multi-branch projects for each matching, repository and whole github organization. So there is a there's, a general API for defining kinds of SCM jsem repositories, so we have get subversion and mercurial at least or currently supported. There might be some others and then there's also an API for automatically discovering repositories that could know.

C

So, that's if you, if you click on github organization, that would that would allow you to like that. I. Don't actually have this set up at the moment, I think because I would have to enter some github credentials or something but I have a separate webinar. Where I show this this system, but essentially you would add your github credentials and then it would automatically create a multi-branch project for each.

B

C

That had a Jenkins file.

C

A

C

A

And it certainly did for me as curious, I I, don't know if you've got to run in eight minutes, Jesse as curious, if you could, if you also had something you wanted to ask people here like as like the dude who's really responsible for workflow. um If there's stuff that you want to get feedback on or ideas that we could help you with. Maybe.

C

Yeah I think I, don't have a heart cut off by them. um Yeah, what's what's most valuable I think is just information on what kinds of things people are doing with it ends, and especially what parts of the documentation or missing or updated or misleading in various ways. So we haven't, we haven't done a very good job yet on introductory documentation, there's a tutorial which goes over certain aspects of of setting up basic workflows, step by step with examples of each stage. But there are a lot of different use cases that that doesn't cover.

C

So we'd really like to know what kinds of things people would would like to know more about.

A

C

For example, one thing some people use the build step very heavily, which is used to build other jobs in the same Jenkin system, usually waiting for the result or whatever and that's not currently covered by the tutorial. So there's there's some documentation or.

C

As part of the product itself, but it's fairly low-level, it doesn't sort of tell you what to do with that step in contact me in general. If you click on snippet generator, um you can get serve an inline reference for how to how to do particular kinds of things.

A

So Jessie one of the the problems that Martin and I have been working through I'd, say towards the end of last week. Is you know when you, when you use workflow, and you just have work flow from SCM to setting aside the multi-branch stuff for now, and you have work flow from SCM? When you know, if your job doesn't check out, you know, do a node block and then check out SCM or you know, do something to get source code inside of the context of the workflow.

A

It doesn't have access to that source code and when you start to add like the the global commons library or whatever, whatever that's called for workflow steps, it starts to become very confusing. We're like how many different source repositories one might need in a more advanced setup like martin to have you know, workflows that are pulling in.

A

You know doing work flow from SCM and then your commons library thing, which would have presumably right now it would be backed by sem as well, and then you know, where else you might wanna be loading work floats steps from. um I think it's just a little confusing, I'm probably totally butchering your question marks, um but it's very confusing which or how many SCM repositories one needs to use like all of workflow in concert together for a project, if that makes sense, yeah.

C

It depends on whether you have the main question is whether you have pieces that you want to use across projects. So if the, if your workflow script is basically one script, that you can just write, then the most straight for thing is just make a multi-branch project write it in the Jenkins file and your time. If you want to reuse some pieces of logic from different places. So there is a there is a global library plugin that you can use that lets.

C

You define some pieces that you can basically install in Jenkins globally, that's the name and reuse from various scripts. You can't there's not really a good way of versioning the contents of that, so you can keep it in your own, get repository and periodically deploy it to Jenkins, that's sort of the limit of it. If you really want everything to be taken directly from your own source control systems, then you would usually use load steps to check things out and and load the pieces that you need from particular places.

C

There's also a workflow remote loader plugin, that sort of automate some of the boilerplate of getting a slave node to check out get sources and load a workflow definition from that and make it available to your main script, so it serve the gives you a little higher level step. So Martin is asking why can't we use the load step from the workflow script from sem check out?

C

A

Think what Martin was running into- and this may be related to his post on the the Jenkins user list- is just getting getting the load step and his Jenkins final thing working properly together. So I think there might just be a quick demo update that you know. I need to do or you need to do to make it clear how things work with that is. If correct me, if I'm wrong, Martin you're, not using multi-branch, workflows right now, you're working with just the normal workflow to.

D

Detect a single.

C

Branch is this.

A

Single branch ham, you.

C

Know whether you're using work of the script or workflow script from this, it doesn't matter at any point. If you, if you run the load staff, it it loads, the named file and an runza, then that that file could have their top level statements that immediately do something or usually it has a bunch of I.

A

C

About the definitions- and you can use them I.

A

Think, where the confusion might be is when, when you say that to me I think of just putting in a workflow script load but I'm I must I think that might be wrong. In that you mean a load step inside of a node block where the sem like there's a check out sem or a get step already defined. Correct, like load, is not just going to know what to take to take the file from outside. Of that node closure right.

C

Yeah load is just a step that looks for a file that you name in the current workspace and load. So that's green hat. Okay. I.

A

C

Becca finally, getting the.

A

Workspace yeah.

C

So you have to get that file from somewhere to begin so the of the Simplot. So the tutorial gets a few, a few idioms that that you can use this visible.

C

So this idiom you can use to grab a workspace just long enough to load to check out and load a particular groovy file, and then you can reuse the definition later and so on. But there is, there is a plug-in that makes this easier, which I should probably linked to from here.

C

So that's the workflow remote load or plugin, which basically does this boilerplate for you, so that you just say: I want to load workflow function, definitions from the following get repository, then it does them as the check out of that workspace and loading for you is.

A

The remote loader plugin been released to the update center, yet.

C

As far as I know,.

C

If it's on I think it's not sure if it's using pure I think it's low rebuilt, lip plugin, remember right: yeah you're, not file loader plugin, so this gives some some basic usage. It doesn't do anything you can do already with the load step, but it provides the serve a higher level syntax for it.

C

You can say by a loader from get give it some get location and credentials and them, then you have a function ready, so we would like to provide some provide something that works a little bit more like the global library plug in at some point in the future that can also work with external SCMS.

C

You just have to come up with the rights right design for letting a workflow specify sort of in a abstract terms which library it wants to use in which version and then have jenkins know how to concretely get that file and load it. That's within.

C

Martin is asking there has to be two checkouts.

C

There doesn't have to be that's common, so a tutorial. For example, you can, you can see that you could do all of the I mean the the load step will actually run the script that it loads. So if you're mean, if you're happy working on in that same workspace, then you can have it run stuff in line. But if you have something that's shared between multiple repositories, you would probably want to just have it load that library segment and then use it in another workspace.

C

Emergen says we don't have access to the internal workspace that uses to check out workflow from sem yeah. That's correct, so we're flow from SCM option is basically just a shortcut.

C

All it does is the same thing you would. You would do using this kind of idiom with the load. Step basically just creates a a temporary throwaway workspace and does a SCM check out long enough to load a script from it and then continues with you.

A

Well, aside from Martin and occasionally Owen, it's a mostly quiet room. Oh.

A

I'm glad you had the the workflow demo ready to go.

C

C

Yeah by the way, so right now, you can see that there's nothing in the executor. Cuso Jenkins is idle, even though in fact masterbuilt number two is the flow. Build is running, but it's just cause you're waiting for input. So at this point it's not consuming in the executor consuming a thread or thing I'm Jenkins, it's just Jenkins. It's recording that it's paused here, but that's about it and you can restart Aikens.

C

That's some that whatever point you like during this flow, and it should come back to the same spot that is out does.

A

One of these one of these workflows- you have the multi-branch workflows, have multiple branches that you could go to AA.

C

So, let's so this is it doesn't great now, but if I um me see, if I can mean a clone.

A

I'm not sure what you're expecting it's, it's actually pretty straightforward, but yeah.

C

Here I'll just make a control.

C

I'm just going to create a new branch in this repository and be cool edit to the Jenkins file or something no. We have to check out Dutch be feature. You think it.

A

Is the bill district like when the multi-branch plugins really going and you've got multiple branches? The multi-branch workflow just appears as a folder in the UI, and then each branch just looks like a separate job except you didn't have to be bothered with creating that separate job, which is quite handy. So here I've pushed.

C

A new branch- this is just a plain old git branch source and it doesn't have any kind of web hooks or any anything like that, set up. It's just a actually just a local. The super dumb get server so I'm going to manually reindex it. Otherwise you can now that's a bug on 169.

D

C

One do that on 1609, not to if you look at the log file, you see that it reran branch indexing, and so it it loaded this repo and local host. It says that it found this. This new branch, I pushed called feature, and it said it met criteria. The criteria was just that it have a file called Jenkins file in it. So that's enough for it to be considered. Buildable master branch soul meets ax so that automatically created this new.

C

This new project called feature, and this will run for a minute and the only thing once.

C

So the only thing that I changed in this was that I added one line to the Jenkins file, so I've changed how my workflow script runs in this branch. So that's a in a minute or two. This will finish running you'll, see it that extra message at the end of it.

A

So jesse is there a way with the multi-branch right now you mentioned earlier that when you delete a branch, the project goes away. What happens to the build and test history from that branch? Does that just go away entirely as well? Yeah.

C

That just gets deleted now, if you want to keep the branches branch projects around for a while, then you can edit this stuff.

C

So it's a lot like it's a lot like the artifact and build rotator for build history, so you can say they want to keep branches around for one week or or I want to keep the last three closed branches around or something like that, so that, if you, if you want them, retain for a little while you can do that or of course you can just uncheck that and then they'll just stay in room.

C

So the default is just to delete them as soon as as soon as they disappear from the repository, that's customizable.

C

So if I seed with feature branch, then in a minute you should see a little message at the end of the script and.

C

So and says: if they need Jenkins history for 90 days, you know so you could just set them at the branch to stick around for 90 days. So.

D

C

All I've done is I've added echo statement to the end of the workflow in this branch. So when we run this branch project, it will run this extra see. The useful thing here is that you can make changes to your Jenkins file that match changes to the rest of your source code. So if you, if you want a prototype, turning on ionno cobertura as part of your project, if the cobertura publisher is available or something like that, then you can make that change to your projects.

C

Build script actually run the covert or a tool as part of its build lifecycle and make the change to the Jenkins file to publish that report into Jenkins as part of the same commit and do them both on a topic branch thing that you run so your masters. So the configuration of your master branch is not touched. Well, you do this, so that's a good way of basically prototyping changes to your taken straub configuration without committing yourself to them. If something goes wrong, then just that branch project is broken.

C

Your master branch is still group is easy, chap their own distinct, build histories.

A

Should Jessie Martin's asking has got some questions about how staging works, particularly with preemption? um Is the documentation says that older builds will simply exit early if they are preempted but as their config to never preempt a stage.

C

A

C

State so specifically, when you have the concurrency on the stage, that means that, if that only one build can be running age at a given time, so if there are newer, builds that come in well, the build is already in this stage, then they're just going to wait for the original one.

C

To finish and preemption means that if you've got two new builds that come in while you're still waiting for the first one to finish, then the second one gets automatically imported, the idea being that you only want you only care about the most recent build anyway. So it's only going to let the most recent eligible one through the gate. There are some RF ease open for alternate behaviors. For then yeah I mean yeah. It kills the older building. It marks it visible. It's right.

D

C

Are some RF ease open for alternate behaviors of stage concurrency?

C

So probably the the main request is um that's a little bit to summarize quickly here, but basically to allow the other will allow the other builds to come in, but be aborted only when we exit the stage so another related our fee is to be able to just lock a critical resource like some test database or something that you only have one of to be able to walk that so that only one build at a time can get access to that without really paying attention to where in the build you are.

C

So if you, if you don't care about the the sequence of stages or anything like that, you just want to prevent two builds from clobbering one another. That's an RF II and the for workflow compatibility and the locks and watch it. Locks and latches, plug-in I, think they're, lockable resources, plugin or something like that. That's a well-known, are fe in the list. So it's locked Rick flow support for resource, locking, lockable resources, plug-in people frequently one.

A

So ever everybody is aware: there's 15 minutes before Stevens plug-in development workshop, and so, if you've got last, questions for Jesse it'd be good to take or not just Jesse I. Guess anybody else around workflow and feel free to chime in the.

C

Martin was asking for a list of all of the RF ease and bug reports, so maybe there's too many to walk through them or anything like that. These, this particular JIRA query, is linked to from the workflow home page. So this link here chiara. This gives all the pumping issues are either in workflow plug-in itself or in other plugins, but they're marked with the workflow label.

C

So that's just the special signal that it's you know either our Fe for integration of that other plug-in and to workflow or some kind of issue that particularly or only affects workflow, builds the people using workflow and wanted over them.

C

A

Managed to open source to open source the workflow stagevu plugin. This might be a good patrick question, as opposed to a Jessie question. If you're paying attention Patrick.

C

Yeah it's. There is actually.

C

So there is an issue for this: okay.

B

C

If you go to use filed against Jenkins 20, um then there's yeah provide better work flow visualization out of the box, so currently cloudbees sells a graphical stagevu. So this is a view that appears where the job as a whole and shows up shows a sequence of builds going through particular stages and has more quick links to to do things like get artifacts or respond to input or something like that and there's a proposal on the table to open source. This I include this in room in the OSS portal, offering so.

A

For the for the youtube, video and patrick said that that, yes, this should be open source as part of jenkins 20 believe that coast k talked about it in his initial jenkins to toe to toe presentation. um And if you just go to jenkins, see I dot org, slash content, jenkin, / jenkins 20. That proposals there's a link to all of the proposals and I'll put that in the sidebar and the notes and for posterity.

C

Martin's asking for the two JIRA's on the stage: preemption enhancement somebody.

C

So there was a lockable resources plugin.

C

So, let's see, where is that.

C

You're that guy- and there is also.

C

This one is frequently requested, there's actually sleeping there. Pontoon yep there's actually a patch for this, but without tests, and so it's installed at that point they haven't gotten the chance to work on.

C

Those are the two major ones on the topic.

A

This has been I, don't know about everybody else Jesse. This has been awesome thanks for taking the time absolutely.

C

Any rifle the final questions or anything that we missed in the sidebar.

A

Quick question about 270 39.

A

C

A

C

We're sort of a long discussion here you can skip.

C

Skip down to this part of the discussion.

C

So to prevent waiting jobs from being preempted um yeah- that's that's another sub R Fe lurking in here, although most of the time when people- yes, all in Cuba, execute most of the time when people ask for this they're actually asking for the lockable resources are Fe, so the 30 to 60, but there are potentially some use cases for another mode. It's that's discussed here.

C

Want to have all of them run and run in sequence, without premature, also potentially scary,.

A

Yeah good, so if you, if you're experimenting with the workflow plug-in and you go to the issues accused I Jacobs, get on board, the component that you should file tickets under is just workflow dash, plug-in and Jessie. Do you think it's better for for people to post feedback and further questions on the users mailing list or on the dev mailing list.

C

They don't play on have a strong opinion. They usually follow the stack overflow tag, work for surf, concrete how-to questions, try to make notes, but doesn't work or is there a way to do such-and-such usually stuck over and.

A

In the, if you just go to github com / drink and see I / workflow dash, plugin, there's links to the stack overflow there's links to jira the change log and the users list um that you see on Jessie screen right now. I.

D

A

Yeah this is this has been phenomenal thanks a lot Jesse sure.

C

My pleasure, thank you. Everyone for attending.