Jenkins Infrastructure Project, 29 Jun 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2021 06 29 Jenkins Infra Meeting

Description

Jenkins infrastructure meeting June 29, 2021 with discussion topics including:

* Wednesday security releases 2.300 and 2.289.2
* Web analytics for plugins.jenkins.io
* Migration of archives.jenkins.io from Rackspace to another provider
* Improvements to status.jenkins.io

A

You permission to record.

B

So recording has started.

A

Yeah awesome thanks um hi everybody welcome for this new jenkins infrastructure meeting. We are the 29th of june. We don't. I mean how many so we have three topic two to cover today. So the first one is. We have a security release coming tomorrow, so this will be a weekly release and a stable release. So stay tuned and I mean I hope that we won't have an issue with the release environment, so yeah everything should be fine by tomorrow.

A

Just yeah just related to this. Please don't update jenkins instances tomorrow, so we don't introduce potential noise, so the next topic is about analytics. So gavin started a discussion on discourse about how we I mean if we could use google analytics or something else for our plugins that jenkins rio, we explore two options: plausible and matamo, so the first one we just because I'm already using plausible for personal projects, but I have the the small the smallest subscription.

A

um We just did an experiment for plugin sites, so yeah we just have access to basic information.

A

We just stopped the experiment because we consume all my credits in just several hours, and so my account is not big enough to to cover plugins such as the io, and so I don't want to pay right now so without to explore. I just want to be sure that we want to use placebo or matamo before paying or finding sponsors. So if you have an experience here, that would be that I mean yeah feel free to share. I think the discussion can continue on this course. um It's a in in the infra category.

B

Olivier what we're seeing here is a is a a website website um statistics report that was generated for plugins. That jenkins thought I o using plausible, so you registered jenkplugins.js jenkins.io with plausible. It started collecting data, and this is this is what you got that quickly.

A

Yes, so it's quite simple because it's just a small javascript uh that you have to share in your websites, and so you downloaded that small javascript send information to plausible. So this view is public, uh so just go to possible.you, slash, plugin searching in the layout.

A

You see a small peak, because if you just look at what happened since um seven days, we you have a small peak because gavin enabled that service yesterday, um this time and I disabled this morning when I realized that um iu, we used two thousand uh twenty twenty two thousand page views and I have a limit on ten thousand. So um so that's why I disable it for now but yeah. The kind of information that we have is page visited sources countries.

A

So it's really basic information. It's not the kind of information that gavin was looking for, because giving was more interested about understanding the behavior of users on the website. We could use google analytics, but I would like to avoid, if possible, so I think that giving as an action intent to explore matumoto, which is another option here, but I don't have any experience with this. One matamo sounds more like um you get a good analytic replacement.

A

So yeah, if you have an insight, feel free to share my only concer, so yeah in both cases, plausible and matamo are open source, so we could deploy the services ourselves, but my concern is in for that kind of service in order to have them useful for the project. You want to create data on the long term, and so that means that um we will have to be sure that we I mean yeah. We have to be sure that we back up data and so on.

A

So that would just put extra pressure on the changing surface team and we already have a lot of things to do so. That's why I'm not really confident to host the the service ourself and also, more importantly, as soon as you provide a service with analytics, if the data are incomplete, people take the wrong decision. I mean people take the wrong conclusion based on the data, so I'm always feeling them for uncomfortable. If I cannot share a service that it's 100 reliable when you want to collect data and analyze them.

A

So that's why I'm the tree yeah! I would like to do it to explore the sponsoring or the beta approach.

A

So that's a small project. um Another the next topic is about me creating archive touching kids, so we discovered last week that rackspace stopped sponsoring the project two months ago, and so now we receive invoices.

A

Those invoices were sent to kk's email address and he forgot to share them with us, so we'll have to pay the invoices, so at the moment is around 600 per month.

A

So we have two to pay and we have a third coming. So the idea is to migrate as soon as possible. um So we are now exploring. So archive is a copy of another machine, so we could deploy that on amazon, but I would like to have it deploy on another cloud provider. So we have some redundancy there, so we have either the option to deploy an azure, but we are already trying to decrease the cost of azure accounts.

A

So I would like to devote that option, and so we have two options here: either deploying that on oracle clouds or on scale way. um We I mean those two accounts um offers uh low cost infrastructure.

A

So so that's what we are exploring right now, because daemon is not available at the moment and he has access to the skateway, because that's a new project that we are exploring there. I would be more interested to look at oracle this week, um but yeah we're creating our archives at jenkins. Io to a different location is quite simple because that machine is papertized, so we just have to be sure that the data is transferred from one location to the other, one which is a one-time, rsync command.

A

So that's that's the current state for archive. Otherwise I don't really have any other topic. um Last week was pretty busy with silicon and um contributors submit. So we've reduced our time here during that time. So do you have do you want to break any topics?

A

B

Well so aditya had aditya had paired with damian on some efforts. Last week uh you and I have a plan to do work on archives.jenkins.io.

B

Are there sensitive things there that we could we offer to let aditya pair with us as well on that one sure or is, is.

A

B

Is nothing critical.

A

I mean we, we don't have secrets, I would say so. We won't share a secret in the video, so I mean everybody's free to join.

B

After the budget, so aditya, if, if you're interested I'll, include you in the invitation for our session tomorrow, I.

A

Think it will be more dif yeah, no yeah. No, maybe it's that's possible, the actual yeah. Sorry. What.

B

What do you think maybe more different? No! I was just thinking in time, but the time he's fine foreign, oh well, it's it's as bad as this one right. It's it's a terrible time for aditya, because it's late in late in his evening, but it's it's! It will be right now, aditya your time, I assume it's roughly 10 p.m.

C

Yesterday, 10.

B

C

It's roughly 9 30 p.m.

B

Okay, so so it would be about 7 30 p.m. Tomorrow, your time that we would be I'll I'll include you on the invitation you're welcome to attend. If you can't attend, don't worry, that's that's perfectly okay to if you're not available. It's just for me. It's a it's! It's great to have other other people involved as we're doing these things to to help us and assess what we're doing.

A

B

Information if.

A

You want to, if you want to move it later, um yeah feel free to ask and we'll see if we can adapt.

C

I think I will be available so yeah. I would be happy to join.

A

Thank you great.

C

Just is it okay, if I suggest something so yeah, can we please go back to the docs actually sure so now, when you brought up the topic for a plausible and matamo, you were referring that uh someone, I I I forgot the name. Actually they were looking for something like user analytics and user behavior right and we would like to avoid the google analytics so there's uh there's another tool, I'm aware of that's called aws start. I p w s start. I, if you want again link, will give you the link as well. It's.

A

C

Yes, I'm putting the link in the chat. uh Only bad part about it, I see is its ui is very old-fashioned, so the ui part is not great, but it gives the a lot of data about number of visitors, unique visitors, their duration and rush hours and etc. So that might be something interesting for uh someone to look into and I think it is open source, so we can build on it as well. If maybe.

A

Interesting thanks for sharing. I was not aware of that tool. Oh yes, I'll definitely explore.

A

Sorry yeah sure I'll look at it. I was not aware, thanks for.

C

A

There is one I mean we are. There is one last topic that I can bring. I'm not sure if I shared that information during the last status, um the last infrastructure meeting, but I made several changes to the status page. Do you want me to so so I'm going to to share them again. um Sorry, if I showed them two weeks ago, so what I changed in the status page is, I removed all the iframes.

A

So it's way faster now to display this page when you go to status or jenkins audio, but instead what I've did is I added two different um tabs. The first one is services, and so, if you click on it, you have because I'm in a dark mode, you don't see the link correctly, but at the moment we list three services and the plan is to add more so we just have to work on the documentation.

A

But if you click on a specific get dodging and let's get genquisario, we now have access to a description of the service. The iframe is loaded here um because we only load one iframe, it's just faster. We don't have to wait five minutes to load the full page and then we put some links to um various locations.

A

So in this case it's get that jenkins that I use so I'm providing links to the home charts to the service beyond and so on, and so, if you're curious about what this loop page looks like you just go to the git repository status, page.

A

So you go to the content um services. Let's say get a jenkins that I own, let's show the rule of view.

A

And it's just an add-on file with few parameters, so we just provide a parameter to the to the file and that will render so we have the title of the service. uh You'll have description, the monitor views, if you want to let's say, include an iframe, so we have a title for the iframe and so on.

A

So we use um the go templating to generate the page, and so the plan is to add more so we have right now for one for ghetto jenkins or io, and the idea is to provide essay for um the main website, changes that are your own plugins and so on. So that's how white changes the status page, um I'm currently working on upgrading some cs states, so it just changed the way we visualize.

A

We have access to the time and that should clarify, and so, if I go back to the to the root of the service, I also provided another view which is monitoring information and so from here we also have links to other pages, and so, for instance, there is links now to that adult directly. So there is one view for um every website response time.

A

Http response time, and so the plan is to just provide the links to the front public dashboard that we have on data page of duty or whatever, um I'm just trying to revisit how we deploy and manage the status page. I know that we are putting a lot more information about the different services on the status page, because yeah, the goal of a statist page is just to tell you if a service is down or not. The the goal here is.

A

My goal here is to provide enough information for every services, so people can look into the different location to understand what's wrong and maybe provide some yeah understand what's wrong. Basically, so right now we only have to get the jinkins that I own um pacquiao and update search engines. That are you, but the plan is to get so nice to have more.

A

um That was the last point, um any other suggestions. Otherwise I propose that we, we would love the meeting here.

B

And from me, thanks for showing status.jenkins.io and marvelous work, I love it.

A

Yeah, I'm really I'm I'm really happy with that. um You got them, so that's working very well! So then, thanks for your time, everybody and I'll see you tomorrow during the work with archaic, dutch inquisition and otherwise see you on rc goodbye thanks goodbye. Thank you.