Jenkins Evergreen, 3 Jul 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Essentials: Open Planning Meeting (2018-07-03)

Description

This is a weekly meeting to discuss the progress and plan for Jenkins Essentials, an automatically updated Jenkins distribution.

Find us on GitHub: https://github.com/jenkins-infra/evergreen

Join our Gitter chat: https://gitter.im/jenkins-infra/evergreen

Jira board: https://issues.jenkins-ci.org/secure/RapidBoard.jspa?rapidView=406

A

Really, hello, everybody, so we are having the weekly open planning meeting for Jenkins essentials. So today we are not a lot of people. There's Oleg Manley should join soon, and so there's me Oleg is kindly setting up the meeting, even if he had a lot of important things to do. You are going to try to make it short.

A

So, on my side, I have just finished and filed a PR to provide a cloud friendly installation for gentillesse essentials for AWS the PR I thought I had linked it. So yeah, it's here and I also did a video Oh. The link is bad.

A

Linking to OPR is not very useful, and so I did a video explaining everything. It's a 10-minute video demonstration. Basically, and so this is going to allow people to use in cloud formation create from the ground up an instance running in in in the cloud enable use cloud. So I think I already explained a bit last time, but basically it's going to be using both ec2 cloud plugin, but also pre-configured instance, so that you will be using the artifact manager, s3 plug-in, which basically is going to.

A

Let you store things in the cloud in s3, instead of sending binaries back to the master file system, as was usually done and is usually most often usually done, on Jenkins masters and I along the way I had to file and fix and discover a lot of issues, mainly on configuration as code project.

A

It was interesting to set that up and so I filed a few PRS in there in there, and that's mostly it and I'm, going to be switching to some internal tasks for my company and then get back to getting back to to this a bit later this week. Hopefully- and that's for me so I guess if.

A

If there's nobody else for now, I guess we can just wrap it up so I'm, going to summarize, what's going on, for mainly so Mandy is mainly me right now, working on prototyping the century, a Rollo using error logging for sending things to century, basically offering access to developers to pipeline developers, for instance, Iiro logging and she's going to be also tackling soonish, very important JIRA, which will allow to actually wrap up and I'm going to give them a cue. Mainly to summarize those and yes, that's it. For me at least.

A

Mandy are you here? Yes,.

B

I'm here, okay.

A

You want to summarize.

B

A

You're on and what you're going to do so.

B

I have been working on the prototype force in the airlocks over the century, I've been playing around with a couple different options and working on adding some tests for that and I'm almost ready for that one to be ready for review and then I am currently researching, adding the flavor in we are evaluating how to get that saved into the database that hopefully won't take too much longer. That's pretty much me.

A

Thank you so yeah, that's one is going very, very cool, because this is going to really be a critical part to actually make essentials work because for now we're forcing dhoka cloud flavor, which doesn't make sense and I actually installed everything for Ebel us even on the and the basic foundational plugins, so that I could wrap up the edible, US flavor for so far now. This is a really a critical one that is going to be yeah awesome.

A

So thank you, Mandy! Thank you. Everybody I think we are good. I, like you want to say anything before we go yeah.

C

Actually I had one question yeah, so we have Jeff 309 about Bill of Materials original. It was proposed by Carlos and we're discussing it shall be just as essential survivable, so I want to talk you. Will they do this now or is no contribution? Yes,.

A

So it's actually used, so not everything is wrapped up, but per se. For instance, if I show you the code base on the service side, it's there's that file here. That is the bomb and right now there are some code that actually resolves that bomb kind of you know like in maven world would be computing, an effective resulting poem which is not really a bomb in that case, so in jester Jason is the computed file from the essentials poem.

A

So, yes, we are using that so possibly because this is Tyler who worked Tyler, who worked on on that part, so I'm not absolutely sure he made. You know double check if everything indexed in the jet is being respected in the implementation. But basically, yes, we are using a bomb. Okay.

C

Cool yeah so sorry, the question that I want to spend some time notice too literally Jeff, either over the fence or the first defendant from the usages, because yeah so far, I was aware that we use it only in customer what packages or.

A

C

You use it in a in essentials now yeah. We.

A

Likely need to reconcile the exact format because I think they are slightly disconnected I'm, not sure it would be working. We know from 1 to n that way to the other and so on. But yes, basically, it should be very much the same. So that's why I was what I was talking about. What mandis work with may allow me to remove. That part is forcing you know: ec2 an artifact manager a3 on every single instances, even if on docker flavor, for instance, which doesn't make sense at you know in the long term,.

C

A

So, let's I think we're done so. Thank you, mandy. Thank you. A leg and see you next week.

C

A