 Am I, today you are Mike, for some reason, I have, I have us recording, we're recording now, welcome to the UX. Okay, um, do you do you think it's better I keep record because I'm going to stay for more time. Because you need to live in 10 minutes and I will just, I will just assign you as the, as the, what do you call it as the host before if I have to leave early. Right. So, I will, we'll repeat it this later but Mike and I, Mark and I will probably leave earlier today. So we, I can only do an hour. Hi, the man. Welcome to the UX meeting. Happy to have you here. So I don't think we should, we don't further ado I think we should start. Hopefully, hopefully, we'll be able to join us. And what we are here. Okay, so, and right. Agenda review. So we are here. Can you give a short introduction of yourself and you're interested in this group. Yes. So I'm, I'm part of the Jenkins community team with Mark, wait and review for now. And I'm, I'm here not as a member of the infrastructure team but as a Jenkins user, because I'm interested in the, where the UX and UI is going. I'm interested to take knowledge and maybe try to participate in the force in future. Okay, great. I'm going to go ahead and if we have time, I will because we need this may we will be having a hurry. You were interested in talking about pipeline visualization. Yes, that is correct. I think we can get through all of this material quickly enough so that's any other agenda issues items somebody wants to include. Okay, so let's go ahead and first item health check for the Marshall DS we are here. We are releasing I'm really excited for it. Is there anything we should worry about any but we should look at or anything. Do you have any idea or something we should be paying attention to. I think everything's merged. We've got a few fixes merged recently. Just need to create their release candidate. So today tomorrow. Yeah, at least need to need to do the back porting. Okay, holding off just waiting for the last fixes to get merged yesterday. So, so Tim the invalidate the site, the data on site upgrade was was wonderful that you got that into 2.2 80. So this my assumption is that will be included in the in the back ports as well. Yeah, that's why I waited to do the back morning. Otherwise it would have done it last week. I just wanted to get that and Excellent thanks. Yeah, thank you very much. I see an entry for change. Just a reminder that I've got to create it and the sooner I created the help there we all are because it gets more reviews, more time to think about it and more time to clarify and correct it. Yeah, these ones. I'm hoping to get the release candidate out. But Tim, your thinking was release candidate is probably still a day or two away. So that's, that's likely much faster than I can do the upgrade guide and the change log that'll be like mid next week before I'm ready with it. Yeah, I'm hoping to have the back porting PR today. Hopefully. Yeah, so I'll say it's just whenever it's due next week, but Great. I definitely won't if if I'm if I'm on the if I'm at speed, I will have the change log ready before next Wednesday. And that's that's my goal. Great. That would be great. Okay. Yeah, it's going to be a tough change because of the extreme as a security. They also the it's going to be a tough one. So, Yeah, so a number of open issues tables to these. Let's open these here. I'm going to say that we are proudies are working on fixing some plugins that some of the very high profile plugins that were left such as groovy parameter. For example, rebuild. I think I also mentioned groovy. So, several of these we are plus plugin, several of these high profile plugins and we are working to fix them. I'm going to update Jira because I know that Dario has done a PR for the which fixes plot. We got to get that updated and sync back. And there's seen a few PRs go out. Yeah, I mean, Yeah, maybe we should. We can reenable the deleted tests. I don't know. The problem with plot is it's not really, it's not maintained. Okay, and it's not a huge percentage of people using it and there's no one maintaining it. Well, there is, but it applies every few months. And that was part of the reason for removing it as well. It needs. Okay, I think. Can you just follow up on multiple scms and TFS plugins because they think I think they are maintaining at the moment. Multiple scms is deprecated. It's got a big if you're still let you get a big warning and your Jenkins I don't know if it's worth. I mean there is a PR for it, but it was already broken partially broken before attached to it. Multiple scms is deprecated because pipeline is just a better way to do multiple scms we, and we've had a better way to do it for years now. So I'm not concerned about multiple scms. Okay. Okay, great. So any more triaging we want to do. So next, next topic. A great guide should have pointed for custom plugins. Do you need any help for the, for this mark. I'll need reviewers once I've got it written, but it's usually most efficient if I do the writing first try my best to have a good writing, and then we let the reviewers help make it even better. We will help you just fingers. Other critical plugins that needed me to release and not a maintainer. So sorry, sorry, sorry, sorry. I sent a proposal for that didn't get a lot of feedback on it. I'm not sure that we've got the traction for it yet, but I still think it would be helpful. A week or two prior to the release to do a meetup, but I'm okay if, if, as a UX, we say now I'm not really worth it. I don't know to be honest, I don't know when what when is the middle. It's not been scheduled yet I just put out a proposal for it and was looking for feedback. So I don't think I've seen that proposal, just I will bring you after this. I'll embed a link to it into the into the notes. Okay, great. Yeah, we can talk about this offline. So critical plans that lack a maintainer. So TFS suspended by still has users as that's multiple as the answers, as much as it pains us. Publish over. This is a tough pattern, the maintainership. Yeah. Any, any comments on this any solution. That's the jinx of my made up. Okay, I'm not sure. Okay, so can we are we done talking tables today's. So actually on the plug in we have an adopter now or we've got somebody who's learning towards getting a release so I think it's the previous nine tiner is trying to do a release just to unblock it. Right. Mark, he said to step back. Okay. Yeah, oh and Megan. So, so there's, there's progress there, and the progress is, is positive. I think that's one of the bigger ones that does need releasing, but there could be more. Yeah, I tried, I tried to leave Jara was in review until it got released rather than doing the resolved thing because I didn't think resolving them was very useful until they're actually released. Checking through some of them. And I don't think it's too bad at the moment. Okay, so I will, I will move on if you don't mind. So. Yeah, I cannot review the material is right. So, I have you month month or two ago we talked about material icons and basically to use updates to everybody. We, a year ago, when I started working on the UI revamp, we, I sort of, we, well, we sort of chose material icons, because they feel nice. And we were using them as materials as is really just rights, because basically for our purposes, there are two techniques that we can basically use to are usable which are as we just price on an icon font. I was looking for, we have been using them for a while in quite some of you icons, but I was looking yesterday at material icons repository and I don't see the spreads anymore. I don't see the raw sbgs, but building a sprite with all material icons. It's feasible for us to. If we want to continue using these icons to build a to create a spread for us as bright as basic as the files that contains definitions for many sbgs right. It's feasible for us to start creating that spread on demand, for example, I need a bell icon like I added to the sprite, but not having the holes. If we continue the same technique, it will be very difficult to have the whole material icons available, which would be hell. But if we could tell blogging developers, okay, you just use the some go to the material icons repository and look for an icon and use it. Another way would be using an icon font or just which would be consist of some little work. And because for what we are going to do next and or just change to something like bull stuff. I don't know. So I want to raise this as a risk. This is a risk that the spirits are are have been retired. And if we want a generic solution, for example, saying we have this list of icons look for them in this place. We should consider moving on from the material is we just write some either creating our own sprites or use an icon font. I don't like that, but it's an alternative, or just use a good stuff right. I want to raise this risk. I don't have the best idea for this office. Yeah, yeah, sorry. Only happened to have suggested many, many times to use bull stuff here. So I think he would have told this if he was here. So that's why it was pretty interesting here. So yes, sorry. Yeah, so I was going to say I tracked back where it was removed from the material icons repo back in August. It's been removed with a comment saying that this to build exactly what you need. So they're not saying don't use sprites anymore but they're not providing pre built sprite sheets. Yeah, the problem of pre building a sprite is that if we were if we want all of the material icons is going to be tough, basically, and require lots of maintenance. Do we want all of them live. I don't know. When we just include what we need. I mean, if you, if we want to allow client developers to have to use the icons, if not, I will have absolutely no problem in building our own sprites, I will happily set up the tool team. I have done it before and created a sprite before, and it's easy to do with Webpack. Yeah, I mean it's fairly common for our developers to provide their own icons as they need currently. I mean, if there's an appropriate one and set they can use it, but I think it should be documented how they can add their own ones, either to core for general or to their own plugin. But I don't see any problem with include what you need. So works for me. Right. What else. I agree with you there I will try to explore this option. And this leads me so that we can use these icons on the next topic ongoing iconographic work. I mean say Felix team but the full credit goes to team. This amazing PR. I don't know what this is a hyperlink so basically teams in, I think we're really close to taking it out of draft status. Basically, right now we have lots of changes for status icons with really nice animations and weather icons. Yeah, it's. Yeah, we are getting it there. It's getting there. I see that. The market dropped. So I just wanted to give an update on that iconography. And yeah, the man, the Damian Damian, I don't know how to pronounce it. So, wait, sorry, I got to thinking of myself team is there anything you would like to mention about the iconography. What's left on apps. I think right now we have a few icons. We have a few of the icons migrated to the new ones, for example, these ones, but we don't have folders we don't have some of the others. And we have the weather and build icons and the status icons, which I think is the most important. It depends what we want to get matched, not necessarily for the young release, because for the young release we have time to replace all the icons in yet this in time for the for the young release. But what do we want in time for the for the for the to get the PR match was the minimum support of iconography we want to get the PR going. I think it'd be good to try one plugin with it and just make sure that everything works. I can't see why it wouldn't work, but it'd be just good to try update like the credentials plug in or something. It's a great credentials and warnings and G, what is it you provide uses bootstrap, sorry, 1000 plugins, 1000 icons. But credential does provide lots of custom microns in the end, whichever one's easy if, if warnings and G's already got icons that just need to change to SVG or. What is the uses the I think I think that's good to see that it works nice with plugins and print their own icons but credentials is definitely the one that I think may be affected. But I'm not sure if it's absolutely essential, at least on day one we can always enhance that. But do you want one thing, do you want to have for example icons for all of these options, or are you happy to just go with for example up the magnifying glass, and the people one and then progressively at the others. Progressive absolutely I don't think I think we've got more than we need for the first marriage to be honest. I think you're right. So I will help you unblock this, and let's see if we can get this out of that status next week. Maybe then we need to take a step back and work on the creating our setting up a tool chain for the material specs. And that's, and that will sort of be the end of the main moment here. Maybe on my free time I will be able to invest more time from this one. Okay. Sorry, Damian. What did you want to share about pipeline visualization. So, it's not something I want to share. It's more me trying to fill my knowledge. As a Jenkins user, I've been using blue shown for sometimes now, and I would have wanted to know I see that it's the rate of changes and feature is very, very low since one year. I wanted to know, given that the UX and UI effort and the community Jenkins have been done on the classical UI, like the table to give immense amount of work. It looks like that the classic way is going to be is going to stay or going to be the main system. So what would be the project to visualize a pipeline since blue shown as some nice feature that the classic UI don't have. And also there are some things missing so that I don't know what what is the official direction if there are involvement require required from from computer and know what is the status. There is an item on the road map for road map for pipeline visualizations but it's up to us as consumers basically right at the moment that I know of. There's a proof of concept for a pipeline graph. Don't like leave Myers issue the graphic self. And so I went to separate here two things okay list of builds, which I don't think there's a plan at the moment open source. In the OS community, and pipeline and long visualization, which is the, the, the, the chart, the nice graph, the graph is, is not difficult to migrate the graph. Jenkins, just I mean, and with the graph, I mean the graph itself, the JavaScript code. The problem is that we like a there's a lack of a single unified API that allows me for example I did try it. I did spend quite some time working with it and I couldn't find a way to have to look what API do I need to see to get the feed of steps to get a for example, as file stream for the log for a scene for a new step. So I think right now API support is the block on the front end front end expertise or something expertise could be done a little by little but without the work on the API. Okay, so what does it mean is it is it that the work is in progress and it's just a matter of time is it there might need some involvement from we should need to search for contributors. And we need to search for contributors right now as far as I know that nobody has been working on it other than the other than on Cliff Myers working on the POC for the background graph. It is on the gentis road map. It is on the road. So I am assuming once other items get tackled that are first with the tackle on there will be community involvement in that. That's why I said it's on us. Yeah, I might have read the roadmap to quickly. Because I wasn't able to find it on the roadmap. That's why I asked the ones here to ask. By monitoring by planning. I was not able to find information about this online on my own. So maybe I missed it. But I had a question from let's say, at least 14 different persons that are Jenkins user that I know in Europe, that all asked me the same question and they were not able to find any information. So maybe the information it's somewhere and it could be only pointing it. Yeah, I think it's not on the roadmap and it's only been in get a chance. Okay, I thought it was on the roadmap that created a year or so. Look and feel updates. Nothing really maps. UI interface rework. No, nothing really maps to it on the road. I thought it was something. I really think there was something. Okay, I was mistaken. So, any other questions? No, no, no. Is there anything I can do to help this topic? I don't know, to be honest, look for contributors. Okay, I because it's a very, very. People work needs quite some time consuming so. Yeah, I can understand my. I'm a multi CI system user and a lot of the people are asking me that question of the same profile, meaning that they use both get the back shuns. Most of the time they use githlap CI, they use Jenkins, and maybe a fourth CI system and each case. They must all the other CI system they use, they now have catch cooked already cooked a train and they provide nice graph visualization. The last one being githlap last month. So now Jenkins is back to be the, let's say the last wagon of the train, because the current visualization is not complete and Russian is quite buggy. I'm also really interested on searching for contributors and helping here, because there is a really high value on the open source system to be sure that we can provide a nice, nice to can feel to avoid people changing towards the system. Having to rewrite all their pipeline and workflow just because they cannot access such a feature. That's why it's really important for me as a user. I think a team just based it on the chat link to the to the PO concept by Cliff Myers. I'm going to put in the meetings. Okay. That's cool. And I have a few, I have a branch on this to expand on it, but the blocker for was API. Okay, if there's anything, if there's nothing I like as I would need to stop recording and stop sharing because I need to, I need to wait. Okay. Anything else we want to mention. That's okay. Thanks for the clarification in the meeting. Okay. That link, you might find some more discussion. There was some discussion around the time, but I can't figure out how to search and get a Yeah, you if you look at Google just Google for not making history and you will see a screenshot or even Okay, if I can retrieve some of this information, I will try to put the question on the web map then. Okay. Thanks. Okay. Bye. Bye bye. Thank you.