Hello everybody. Welcome to this installment of understanding the Magdalene, our playlist, understanding Magdalene where we're going through Return of the Divine Sophia. This episode 100% for sure viewer discretion is advised. Because of the topics spoken about in this episode, it has to be played on our other platform. So please follow the link below to go directly to our other platform to view the full episode. Also, if you have small children around you, I would suggest putting your headphones on. There is talk of body parts in this episode, in the act of creating a baby in this episode.  Alright you guys, thank you so much for being very, very patient with us having to go back and forth between two different platforms. We are just doing what we got to do in this time. If you live in France or a country that does not have access to our other platform, email me at esotericatlanta.com and I will send you this episode, the footage of this episode in the hopes that you will then share it with your fellow countrymen.


all yours. Okay. So I'm sharing my screen. So for today's meeting, the first, the first point of discussion is authentication with git to chooser. So, so I've been working. So I was on on priority. I was working on completing the GitHub Brand Source Plugin extension implementation, but that is currently blocked on tests. I, I think Liam is busy right now. So we could not have a conversation after the last, the previous thing we've had. So I, I, I tried. So the issue I have there is that I'm not able to use a mob GitHub server API server to stop data and mock calls so that I can write test cases. So I have written the test cases and I am using the already they have a, they have a class, a utility class, which provides a mock server for such purposes. But despite extending them, my, the API, the API that I've created for the extension, they are still trying to contact the GitHub server API. So that's creating an issue. And I'm not able to figure out why that is happening. So I would need his help for that. So, so meanwhile, I started working on how I could do the same thing for GitLab. And I have created the extension. And while testing it, I've, I've seen some issues which might be, might be of concern for us. The first is for, for GitLab, so for GitHub, sending the repository URL. If you're not talking about credentials right now, just a method to get the size URL was enough for us sending that information was enough for us to get the size of the repository. But in case of GitLab, so for GitLab, there is a concept of a GitLab server. And we need to configure that a user need to configure that before trying to open a create a GitLab project, organization for project or multi branch project. So the problem with, so there is no problem with configuring it, we, we don't have. So the problem with this configuration is that GitLab branch source plugin is expecting that we know the server name. Instead of the server URL to instantiate the API instance. So to create an API, it would expect the server name instead of the server URL, which I could not understand first, because I thought that there should be a way since internally, it would use the server URL to connect. Why would it not expose the server, a method to provide us a method where we could just enter the service URL and connect to the API, but I could not find one. So that is something of a concern for us because the Git plugin would not be aware of the server name for GitLab for this configuration. And so that's, that's something we have to think about also with GitLab, what I've seen in terms of now, let's come to authentication. With authentication, we don't have to worry in GitLab, they do that themselves. So what happens is if we provide the server name, if you can see in the configuration here, let me zoom a little bit, the user would add the credentials and a secret token. So it requires a personal token, a GitLab personal token. So all of that the user would enter here and all of that is managed by GitLab itself. We just need to provide it the server name, it will look and scan for those credentials. So that's a great thing in terms of sending when we were confused how to send the credentials. And then I went back to GitHub Brand Source plugin to see if, since GitHub Brand Source plugin maybe not, we don't have to configure, I think in the same way, create a configuration in the same way, we would have a user stored configuration for the project in the GitHub Brand Source plugin as well. So the GitHub Brand Source plugin would have the credentials, it should, it may have a method where it would not need the credentials to create an API instance. I haven't found one. I will look more and I'll ask Liam if there's a way. But since it's possible in GitLab, I'm just wondering if it's, if it's something which is also possible with GitHub Brand Source plugin or not. I was checking but I could not find the method. With the name thing, what I want to ask is that since this is a global configurations page, how can we access this if we were, if we were to send the name instead of the URL? How would we access this information? Is this stored? So this is, this is captured by the descriptor class of the particular plugin or is this stored in the environment variable? Well, one second though, like, are you thinking the secret token is going to manage how you would talk to the API? Because that's just for web folks. No, no, Justin, I'm talking about, so the GitHub, so the GitLab Brand Source plugin expects that we know the server name of the GitLab server when we're asking for any details. So, so we would know the server URL that we can extract from the repository URL. But the server name is something which is ideal, which is unique for this configuration used by the plugin. So, yes, yes, Mark. I think we should take advantage of a previous mentor and ask Parichet Barpanda. He wrote this code, because I don't know how you're going to do it. It's got me completely perplexed. It's that I agree with your observation. The URL to a repository is clearly the way to identify a repository. Why should I have to know a display name that a user assigned to one of potentially many GitLab servers that are connected to this Jenkins instance? But Parichet probably will give very good reasons why. And I just don't know how you're going to fit it into the API, because a GitLab server name probably isn't needed for Giddy or for BitBucket or for GitHub. So, yeah, no, it is. Oh, is it? Yeah, because you can have a personal server. That's what that's for. You can run a server on your in your enterprise or at your house. Same thing for GitHub. Right, right. And no dispute that you can run it. And BitBucket. Right, no dispute that I could have multiple Giddy servers and multiple, multiple of any server, right? Absolutely. It's that even if I have multiple of them, the server, the URL to the repository is still the unique identifier for the repository. And so needing to know the name of now, maybe there is such a concept in GitHub as well, and we should gather it everywhere. I haven't, let me look at my installation. I don't think that I've defined one. Yeah, let me look at one, too. But I mean, I think the GitHub branch source plugin should know this for that item, though. It should have a Giddy name as well. Well, it already knows which server these are selected for that pipeline. Like you have to configure that. Like that particular multi-branch project has to be configured with the server. So you've got a hook there. I was a mentor on the GitLab branch source plugin. Oh, that's right. That's right. We have your benefit as well. You were mentoring Potty J. I didn't write the code, though. No, but you were going to thank Potty J. That's right. Yeah, yeah. But Potty J rocked that. So like, and I had some other stuff going on personally. So there may be things that we do need to hit him up on. So I'm totally. OK, so that was a point of information. Not a let's not talk about it. Well, and and I see that GitHub servers also have a display name. Yeah. So so and it's exactly for that because you might want to connect GitHub and then you might also want to connect something else. But your multi-branch. Your multi-branch project needs to be set up with one of those endpoints. And that helps with the scanning and all that kind of stuff. Because Jenkins needs to do like org scanning to see if it's got like a new Jenkins file, if it's got any changes, if it even qualifies, if it even has a Jenkins file or a config driven pipeline. Marker file. Sorry, I'm marketing my own little plug in. But that's kind of why does that kind of make sense? Yes. My question is that if I have the repository URL, even if it's a private server and the user has entered the repository URL, that should be enough to get me that information, right? Why would I need to know the server name for for to to get the size of the repository if I have the repository URL? So the branch source plugins have those as two separate pieces of information. You don't just plug in the repo URL. What you do is you plug in which GitHub server you want and then what owner that is. If you've got like if you're trying to do it on an org level, you do what owner it is. And then it's going to scan everything underneath that org or like a GitHub org, find all the repositories that qualify. Create projects for those and then those each have things. Actually, maybe in under the projects, there might be a little bit more semblance of that, but that's not something you can figure at the at the lower level repository level. So isn't isn't the challenge then for for Rishabh is that in the context where he's running, how does how does he communicate back to GitLab or how does he determine which API endpoint or which which GitLab name is being used because I assume you're you've got an item context, right, Rishabh. There is an item context and that thing could therefore be part of a job or is a job that is running inside of a multi branch pipeline or inside of an organization folder. But now you need you need information to pass to the GitLab server, which is somehow all the way up at that organization folder, right, that you need to know which GitLab API endpoint they should use. And one way of identifying the API endpoint is by this display name. So my my sense, my sense still is it justifies a conversation with Parichet. Yeah, I did ask him this question, I think, and I'll back on the Gitter channel. But I think we if we can have a conversation with him and that would be great. Well, and it may be that we need to do some if if Parichet doesn't respond by say Monday, we can probably ask questions to the maintainer of the GITI plugin, Stephen Connolly, or to the maintainers of the SCM API, like Jesse Glick and Devin Nussbaum and Liam Newman. Because I think each of those people at Devin, maybe not, but Jesse Glick certainly knows the SCM API and Stephen created the SCM API. OK, so. So I think what's interesting is that the GitHub plug in the GitHub plug in is what has your repository URL in a GitHub branch source. Yes, and if you go to that repository thing, that's where you have that. But I guess you're trying to find out where how to get the connection back and forth. So what I'm not able to understand is that how am I how am I able to do this in GitHub branch source plug in without even checking or knowing about the server name? I wonder if this needs to be done in the GitHub plug in. OK, the GitHub plug in which wraps on the Java API is for GitHub. Yeah. Well, so the GitHub, remember, the GitHub branch source plug in depends on the GitHub plug in, which depends on the get plug in. And then if you look at a repo view, you don't see like that project doesn't have any awareness that it's part of a branch source. It has a GitHub. Well, it does know that. Sorry, as a branch sources portion, you can kind of see some of this stuff in the UI, like how plugins work together. Because they'll have their own like jelly labels and stuff like that. It's kind of interesting, but anyways, you can tell that the GitHub is a GitHub configuration that has credentials. It has the repository, HTTPS URL. And then that is what is invoking get plug in, I think. For GitHub, I don't know, we can look at GitHub, too, but I can I can also try and see if I can find some time to look into this a little deeper, too. But yeah, some of those other folks might know it off the top of their head. I'm a little rusty on some of it, so. So I think from my side, I have why I haven't explored this idea that I've always tried to, when I'm interactively testing the extensions, I've always done it with just installing these modified plugins, the GitHub or the GitLab plugin, not configuring a multi-branch project, just running a freestyle job for Git plugin and seeing if those extensions are able to provide the size. So that is why I haven't completely, I would say, ignored that site that if we have a multi-branch source, let's say a GitHub organization project or a GitLab organization project, in that case, how, so in GitLab, I was forced to go to the global configurations and add a server, add a server name, add those details. In GitHub, I did not have to do anything. I, my plugin was able to adjust the repository URL, was able to communicate the size to me. So when I started to explain GitLab, that is when I understood, okay, there's, there's a layer which I did not look at. But isn't, isn't that hinting that it may be that some of the branch source implementations may not be usable outside of a branch source context? So this, the GitLab condition you see may hint that, okay, the GitHub plugin is structured so that we can ask this question. But the GitLab plugin is not. And maybe it's time to say, ask the question to Padache and then say, I'm going to go try another one or, or focus elsewhere just because it may be that, that the GitLab plugin isn't ready to answer the question that we want to ask in the context where we want to ask it. I hadn't even thought of the, the, the, you described it very, very well, a freestyle project doesn't have an organization folder or a multi-branch context to, to be able to provide. It's very good insight. Yes, Mark. So, so I think since, I think we have what two weeks now to, if you want to release this, like these features with the new version. So, so I don't want to be blogged. I, I think I can explore from my side by creating a multi-branch project. And then, so the best way for me personally is I debug, I try to debug the local instance by attaching a Maven debugger. So if I'm able to understand how the interactions are working there. So I'll, I'll try that personally, but I, I think I've asked Parichay if he's able to respond, if we are to get that answer for the weekend, it's okay. So, so my question is that should I move on to the GITI brand source plugin? Either GITI or Bitbucket, no objections from me. Bitbucket is probably more popular than, than GITI. It's, it's on the flip side probably also much has a much longer history and many more authors in it. So it'll be more complicated than the GITI plugin. But, but I, I, I just remember that Fran Francisco told me that the Bitbucket brand source plugin is not, is abandoned right now. I think that's the right term for it. Then, then that's another good reason to you to consider GITI instead. Yes, that's, that's what Fran told me. And, and it's this thing I forgot actually throughout this discussion. I, I remember that is it absolutely necessary for us to look at the brand source plugins to get this information for an example, right now, we're seeing that the Github plugin might be able to provide us this information as well. So, so is it for, so for the other plugins as well, do we absolutely need a brand source plugin to get this, because when I was thinking about GIT2 chooser and getting the size, I was not thinking about the, the, the layers upon which these brand source plugins depend. So now, as I've seen the code, I understand that these brand source plugins are implementing another plugin, which wraps around the Java APIs with for the REST APIs, it says the Java code for the REST APIs for maybe GIT lab or for Github, we have the Github plugin. I've seen that. So do we need the brand source plugin? Because we just need, we need the size. We're, we're looking at brand source because I just, I, I, I did not know that we could do the same thing with the Github plugin. But if we can do the same thing with the Github plugin, why would we need to ask that question to the brand source plugin? Or. Yeah. So this is actually clearing up some cobwebs in my mind. Um, so what you're doing is actually a great test. This freestyle project approach is actually the proper way because you actually don't care about multi a branch projects because that already gives you the cash, right? Um, so between what you've already done, like the great work you've already done, and then that, like, I think your test is going well in terms of like freestyle project. Um, a branch source plugin generally just sets up a project for you and sets up a branch source with that provider's plugin stuff. So I think you're going to be able to accomplish this in and, and I, I do recall that in the GitLab project, we were also trying to kind of take advantage of a lot of the success that the Github branch source plugin and Github plugin suite in general was doing. So I think that pattern is going to be fairly consistent across the way. And I do remember that we, I think, Parichet had worked with, um, Jesse and some other folks and probably Stephen, all, yeah, I think Stephen and Jesse on some of those. So yeah, you might look at Github and GitLab plugins to see what you can get there, what you can get there. So, so I think the direct answer to your question, Rishabh, is no, we don't need a branch source. What we need is some, some component, any component that implements a REST API to a Git provider could potentially be an extension implementer in this case. It just happens that the branch sources always have to do a REST API implementation and therefore they are a likely candidate to have a REST API implementation. So, but, but you're absolutely right. If there's a, if there's a plugin that provides an API to a provider that would answer the question about size, then that plugin is a candidate to implement this extension. Yes. And, okay, so I think, um, I will, and, um, what I also want to ask is that, so it's not necessary that each branch source plugin would have a plugin depending on a plugin which is implementing the APIs. It, it may be possible that those APIs are implemented within the branch source plugin. That is exactly the pattern that the GIDI plugin uses. It's all inside the plugin called GIDI and the GIDI plugin is a branch source plugin and it, it implements. So now that, but it's also a branch source plugin. Exactly. Yeah. But, but it's different for GitHub branch source, right? Where I believe GitHub branch source depends on another plugin that provides a GitHub API. Yes. So, so the, there are distinct differences and I, I don't know on the BitBucket plugin or the GitLab plugin, but I assume some, some variant of that exists there. Yeah. The GitHub plugin is definitely that way. I'm not sure about BitBucket. So Justin, when you say that way, GitLab plugin relies on a separate API plugin or it's, it's got a bundle inside. So there was already a GitLab plugin itself. There was, there were several plugins for GitLab and this was also like cleaning up a little bit of that, but there is a, let me double check, but GIDI.com, GIDI, GitLab plugin, I think is the, is the implementer and so the GitLab branch source plugin sets up GitLab. Okay. So there is a GitLab API plugin. Okay. Got it. Uh, there may not be an API plugin, but there's a GitLab plugin itself, which made you like, sometimes they split those out too. Okay. But, uh, yeah, there's a GitLab plugin too, which you should definitely take a look at that. And that has a lot of information in it. In the reading and stuff. Uh, I, I, I will look at this and, um, I think the summary is, I think you're going to see this pattern, uh, across the branch source plugins, across, across things that also have a branch source plugin, or maybe have that branch source stuff embedded in their plugin. And you'll probably be able to take advantage of the same pattern across because those APIs are all kind of snipping off of SEM API also. Hmm. I had to do that myself in my own place. Okay. So, uh, okay, I'll do that. So I think the next, the next concern for me is I want to discuss was, um, we have a similar technique. I, we have discussed that. Because of server name, we've discussed it. I, I had one more thing in my mind. I don't know what to remember. Oh, yes. So with GitLab, one more thing that I've seen is that, so, um, GitLab for GitLab repository, if we get up, we have repositories and in GitLab, I think the equivalent is a project. And, um, so for a project, we have, uh, the code base in it. And, uh, and I think the CI CD is, it has multiple things. It's, it's a broader definition and repositories. So, so to get the size of the, of, of the code base of the objects we have, it, it, uh, it uses a separate extension of the API, which is called, which basically adds a statistics, um, boolean to it, the, the whole API to get that information. And what I'm seeing, uh, so we have roles in the GitLab, right? For permissions, we have roles. We have the owner, we have developed developers. I, I, I think I have opened it. We have guest reporter, developer, maintainer and owner. So one worrying thing that I've seen is that to see those statistics, the, the user, which is trying to, um, get that information that is the size of the repository, the user should be the owner of that repository, which then seems, uh, I think we cannot do anything about it. If GitLab has decided that, but then it, um, narrows down our scope. I think in a, in a huge way, because our, our developer, developer maintain a reporter or at any less, we'll not be able to get that information, but for a certain type of role, which, which, which is, I think is an issue. So I, I did check, uh, if, if this is true or not, you project statistics. So here it does say that the developer, the maintainer and the owner, all, uh, those three can see this, but strangely enough, when I go to, um, the project API, which is, uh, the GitLab Danso's, um, um, I think this is the GitLab plugin only where the instances, the GitLab API instance is being created using, uh, this, um, class. So there it says that to get a specific project, which is owned by the authenticated user, that is how we can get the project statistics. And, uh, this is how we can get the size. So, um, so with GitLab, I haven't tested, I wrote the extension. I, um, and I could not test it, test it in the sense that I did not, uh, put it in a local instance, I did put it in a local instance, but I was not able to get the size. I was having some issues with it. So, um, I, I think I need to make sure that, make sure that, um, that we may not be able to, and not everyone may be able to get the size of, uh, the project or the repository. So, and if it's, if it's just the owner, then that might be, that might limit our use case, but it, I, I don't think there is something we can do about it. Yeah, that might be something that you need to, and documenting or something like that, um, if it's, if it's a specific permission that needs to be set up for that token that you wouldn't already get by just simply setting up a GitLab project. Hmm. Okay. Okay. Actually, uh, so to go back to the caching thing, if you have a branch source, no matter what you have a cache, right? Yes. So I guess that maybe doubles down on the fact that you should probably just use the GitHub or GitLab plugins rather than the branch source because then you set up a freestyle project with a GitHub setup or GitLab setup. That makes sense. That does make sense. We don't need those branch source plugins because if we have a branch source plugin, that means that we would have a branch source project, multi branch project. And if we have a multi branch project, then we have the cache. Um, Mark, is there, is there an issue with that statement? I'm just trying to understand how we communicate. How does the user, uh, who's, how does the user who defines a freestyle job tell us, tell, tell the plugin which GitLab server is being used behind this URL. And I think right now the answer is they don't. There's no facility for you. What do you mean they do? They actually, instead of setting up a Git project, you set up a GitLab project. You just, you just described a condition which is multi branch or organization folder, I think. I can't define a freestyle project that uses GitLab as an SCM as far as I know. I've never seen it anyway. Let me just check. But I'm fairly certain you can set up a GitHub source. I've seen that we have Git or we have Subversion. Yeah, I don't think that I don't think those higher level providers implement at the freestyle project level. Oh, yeah, you're right. But, but so, so we're back to the, it may be that the only fallback for a freestyle user is if they're lucky. And they've got a job to find elsewhere that causes them to have the cash for that. Because we freestyle has no way to say I want to use this GitLab server or I want to use this. And I don't, it feels like that would be huge, a huge scope creep for me. If you said, ooh, I'm going to add that so that anytime you add a Git project, you need to also optionally choose or add Git as the immediate option to choose the higher level provider. That just that I, that's, that's an awful lot of addition in a spot where we're just trying to get a guess of how big the repository is. Yeah, I mean, I think what you're, what we started with, I think at the beginning is probably the best you can do is try and detect it from the descriptors. In the instance, and that also assumes that you have access to do that. Yes. Okay, so, okay, I think that's what I have to do right now. And the last thing I wanted to discuss with the release plan for what we, so how do we want to, so with the Git to choose PR, I think we mark up senior comments and I just have to fix the test, the test case which was failing on Windows. And so I think after that, what all do we need for the Git to choose it? Or maybe should, okay, we have to wait till we do not find a consolidated way to communicate with the extension part of it, I think, right, we will not be able to finalize Git to choose it until and unless we know that how are we going to exactly communicate with the extension, extensions across the plugins. So I think then the Git to choose it is blocked until as we, so I have to look at the GitHub plugin and the GitLab plugin, the API plugins first, I think. Well, although I, yes, Mark. You've got a working implementation for GitHub plugin right now, right? We've got something that, so for me, I think that's already an indication that we should press forward using that except that, okay, for now, GitLab, we don't know how GitLab will provide that information, but we do know how GitHub can provide it. That already addresses, I guess, 50% or more of the cases right there. GitHub is a dominant provider and therefore that will be, there will be a lot of people very happy with that. Okay, so in that case, if we're, so if you're looking, so we have the GitHub, GitHub branch source plugin implementation and once the test cases that problem is fixed, we would have that PR merged and once we have that, so I want to understand how would we do this? Would we merge GitToolChooser first or would we wait for the GitHub branch source plugin to do that so that we know that, okay, one, there is one plugin which is supporting the tool chooser, now we can merge it inside the Git plugin or it's not necessary for us. I think we could merge the GitToolChooser first and let others arrive as they can. Do you see any reason why we shouldn't do it that way? No, I don't. I think we might not be able to address all the use cases. For all the users, we might not be able to get the size, but at least we have something which might do. So we have the cache estimation at least. So I think we can do it, but I haven't, so I haven't added the instantiations. I haven't added the GitToolChooser at every point because I've always, I'm stuck the authentication part or the extension. So what I want to ask is do I, should I add that within this PR or first should we add GitToolChooser as a separate independent class within the Git plugin? And then we add GitToolChooser in a separate PR. We add the GitToolChooser at places where we would need to make the decision of recommending an implementation. I'm more prone personally to the second style of add it in the current PR so that you've got a testable PR and I can be testing it then after you've committed and others can test it. Unless that's objectionable to you, that would be great for me because the sooner we get it to testability, the better the better others can assist us. Okay, so, okay, so, so I have done, so I have instantiated the GitToolChooser in the Git SCM, the checkout step in this PR, the PR 937, which is a branch taken from the current GitToolChooser branch is it supports the unsupported command functionality to give a better recommendation in terms of JGIT. So I think I would add all of those in this PR and then we could merge it with GitToolChooser or I'm not sure how should I do this? Well, it looked, as I was reading 937, it looked like a super set of 931 or at least a parallel of 931. Would you be comfortable integrating all the changes that are in 931 into 937 so that we could merge 937? Yes, yes, yes. Effectively, 931 has been a great experiment, but so long as all of its content is in 937, you could close 931 and we could then focus our evaluation on 937. Yes, I can definitely do that. And I'll, okay, I'll do that. I'll merge all of the contents of 931, 937. If I remember right, there were more tests in 931 and I don't want to lose those tests, right? I would add those tests. Yes, we have more tests in 931. We don't have those in 937. So 937 was just to, I created it for just the unsupported command feature and I thought that we would merge it and then go forward. It's just create more confusion for me. And we could do that as well. It's whatever works for you, right? There's nothing sacred about a pull request. We can open and close them all we want. Yes. So I think the point is that we want a single PR where we have the workable get to choose it for the get back type. Right. Now, now you could, you could optionally take everything, take the things that you've learned from 937 and pull them into 931, whichever one you feel is it just, as I was reviewing the two of them last night, I saw common code between them and thought, ah, he's been working one off the other. That's great. I assume we merge one of the two and you get to pick which one is better for you. Okay. I think since 931 has the latest design changes, 937 doesn't. So I would copy all the additions of 937 to 931. Yeah. Yeah. And I'll do that. You might be able to just rebase too, if you're, but yeah, it works for you. That's the best answer. There are all sorts of get power tools to help you reach up. There's cherry pick, there's rebase. There are all sorts of great things that and, and every one of those could be a terror cause you terrible wounds that are nearly fatal to your repository. So yes, get is a great power tool. And there are times it would be happy to cut your foot off. Oh, it's just rainbows and unicorns. Right. It's all rainbows and unicorns. Absolutely. I think this is it then for us. For us to release the tool chooser, I, we, we need to merge this one single PR with the workable solution. And apparently I will be, I am working on looking on the extensions. And I think that's, that's it for now. And then I need a mark. We need to figure out a way to either profile the instance where you have a lot of jobs or we could, you were talking about adding a timestamp, which could get. So if profiling is not possible, then we could do it, but. Is can we do that? Can we profile those in your instance? You are welcome to attempt it. I am happy to give you full access. I have never tried to profile inside a Docker image that is running something as large as my, there are only 4,000 jobs on my, on my CI instance. And of those 4,000 jobs, there's a reason that the computer that hosts, it has 32 gigabytes of memory. And so, so I worry that, that the profiler may, may cause you surprises that you didn't really want to have to manage. Whereas timestamps reporting to a file, to the log file are, are pretty predictable. They are, they are certainly aren't as fine-grained or as accurate as, as profiling, but they can give us course enough for this kind of, these kind of assessment. Okay. So, okay. So I think that we can take that approach of time stamping. So we timestamp the builds, right? It puts a timestamp on each line in the, in the job output. Okay. Okay. So we can calculate the difference. Right. Right. So if when it's, when it starts the JGIT fetch, there will be a timestamp. The next step after the JGIT fetch should have a timestamp line as well. Okay. Okay. So I guess I would have to do that. Before get to choose it and after get to choose it to understand the differences. Right. Right. Or, or what we would do is create two parallel jobs that clone the same repository. One with. Chooser enabled and one with chooser disabled things like that. Yeah. Yeah. Okay. Okay. Thank you everyone. I, I think I'll, I'll contact for a chance. See, I have to contact him and for a chair, both. I'll see if I can get those extensions working. All right. And, and so let, let us know. It sounds like you decided 931 is likely your primary focus and you'll backport into 931. Is that correct? Yes. Yes. So I will, I will keep my, I will put my intense focus on 931. Assuming that you'll bring things from 937 into it. Yes. That is what I'm going to. Excellent. Thanks for job. Thank you everyone. Thanks. Thanks.


Good morning, ladies and gentlemen. On behalf of Colonel Jesse L. Schobert, the commander of Western Sector United States Military Entrance Processing Command, welcome to the change of responsibility ceremony in which command sergeant major Michael Jackson will relinquish responsibility of his position as the senior illicit advisor of Western Sector United States Military Entrance Processing Command. At this time, we would like to welcome distinguished guests, family members, and those joining us virtually. Thank you. The presiding officer for today's ceremony is Colonel Jesse Schobert, United States Marine Corps Commander, Western Sector United States Military Entrance Processing Command. Will the guests please rise for the arrival of the official party and remain standing for the plan of the National Anthem and in the giving of the invocation, which is warranted as your choice. Lord, I come to you to just say thank you for this day you have created. On this day, Lord, we lift command sergeant major Jackson up to you and give thanks for the blessing of his leadership, kindness and calmness as he led your people and supported this command. Lord, I ask that you continue to bless him and his family as they continue to serve and support the troops in this nation. Lord, I ask that you lift up command sergeant major Rendon and give him guidance and clarity as he leads your people in this command. Bless him and his family as they lead and support him in commitment to continue service. In all of these things and more we say thank you and bless your name. Amen, amen, and amen. You may take your seat. On behalf of the Commander Western Sector United States Military Entrance Processing Command, I would like to recognize our distinguished guests. Ms. Stephanie Miller, Director, Office of the Secretary of Defense for Military Assessions Policy. Colonel Megan Stallings, Commander, United States Military Entrance Processing Command. Captain Nathan King, Chief Intelligence Resources Division, United States Southern Command and former Western Sector Commander, Command Sergeant Major Lorenzo Woodson, United States Military Entrance Processing Command, Command Sergeant Major. Command Sergeant Major McAdoon, Command Sergeant Major Human Resources Command, Chief of Staff, United States Military Entrance Processing Command, Dr. Donovan Phillips, the Eastern Sector Commander, Colonel Janelle Carter, and Eastern Sector Senior List Advisor Chief Master Sergeant Michael Page. I would also like to recognize Command Sergeant Major Rendon's daughters, Sarah and Isabelle, who could not attend the ceremony. At this time, Master Sergeant Rios will present tokens of appreciation to Command Sergeant Major Jackson's family. For Command Sergeant Major Jackson, his wife Angie is receiving a bouquet of red roses. These red roses stand as a symbol of the deep respect and never-ending affection which has grown for her during her 32 months with the command. She is also presenting gifts of support to his daughter Elena and his son, adorable Austin. At this time, Master Sergeant Tabor is presenting Mrs. Rendon a bouquet of mixed roses, symbolizing a new beginning of service to the command and the community. She is also presenting flowers to his daughter Sophia. USMEPCOM is responsible for processing individuals for enlisted, enlistment, or induction into the armed services based on Department of Defense peacetime and mobilization standards. This mission places USMEPCOM in support of the recruiting efforts of the Army, Navy, Marine Corps, Air Force, Space Force, Coast Guard, and National Guard. USMEPCOM is comprised of two geographical sectors, Eastern Sector and Western Sector, 12 battalions, 65 maps, and two remote processing stations which are located nationwide to include Hawaii, Alaska, and Puerto Rico. USMEPCOM sectors, battalions, and maps are staffed with and commanded by personnel from military services. Western Sector consists of a headquarters in North Chicago, Illinois, six battalions, 31 maps located in the continental United States west of the Mississippi River, including one station each in Alaska and Hawaii, and two remote processing stations in California and Nevada. Ladies and gentlemen, we are about to observe a change of responsibility for the Western Sector United States Military Entrance Processing Command. The change of responsibility is a traditional event that is rich with symbolism and heritage. The key to ceremony is the passing of the organizational colors. The colors represent not only the heritage and history of the command, but also the unity and loyalty of its service members. The keepers of the colors is the senior listed advisor. As the senior listed advisor, members in the organization, the senior listed advisor is both the spoke person for the concerns of service members and principal advisor to the commander on matters affecting the service members and civilians morale, welfare, quality of life, and well-being. Command Sergeant Major Jackson, you have executed your duties of your position with dignity, dedication, and devotion. Your leadership of the soldiers, Marines, sailors, airmen, space professionals, coast guardsmen, and the Department of Defense civilians, as well as your sound guidance to the command have been of the finest quality. Having fulfilled your duties as the senior listed advisor with honor, it is with great respect and utmost gratitude that we say thank you as you pass on those standards and responsibilities to Command Sergeant Major Rendon. Ladies and gentlemen, you will now witness the passing of the colors. The passing of the colors signifies the change of responsibility to ceremony which entails the transfer of accountability, authority, and responsibility. Demonstrating to the command that the mantle of NCO leadership has been passed from one leader to the other. At this time, Sergeant First Class Davis will pass the colors to Command Sergeant Major Jackson. Command Sergeant Major Jackson will pass the colors to Kona Schober, symbolizing the fulfillment of his duties as the senior enlisted advisor. Kona Schober now passes the colors to the incoming senior enlisted advisor, Command Sergeant Major Rendon, entrusting him to carry out the duties and responsibilities of this position. Command Sergeant Major Rendon accepts the colors symbolizing the full acceptance of the duties and responsibilities inherent to his new position. Command Sergeant Major Rendon returns the colors to Sergeant First Class Davis. Ladies and gentlemen, the commander of western sector United States military entrance processing command, Colonel Jesse Schober. Well, good morning, ladies and gentlemen, family and friends, invited guests. I see a few party crashers, some interested bystanders, and people who showed up because they were told to. And for the record, I count myself as one of those because whereas it's always exciting to welcome a new teammate, it's never fun to say goodbye to a tried and true battle buddy. Miss Miller, Colonel Stallings, Dr. Phillips, Command Sergeant Major McAdoo, Command Sergeant Major Woodson. I especially like to thank you for being here and honoring us today with your presence. But no matter who you are or why you are here, thank you one and all for joining us today as part of this time-honored tradition. Today, I see family and friends, mentors and colleagues, headquarters staff and western sector team members, distinguished guests one and all who have gathered from across great distances as well as online to bear witness to this important ceremony. And the gathering of such an august audience, the pomp and circumstance, the playing of the national anthem, the passing of the unit's colors all speak volumes to the solemnity and importance of such an occasion. Indeed, it is days like today, days where we take a step back from the hustle and bustle of our daily activities that can remind us of what makes serving in our military so very special. Which brings to mind a story. It's the story of young Martin Treptow, a young patriot born not too far from here in the town of Eagle Point, Wisconsin. And who in the summer of 1917 found himself working as a barber in a small shop in the town of Cherokee, Iowa, which for anyone who's keeping track is on the western side. And as you all know, World War I was in progress at that time. And when the call went out for volunteers, young Martin listed in the National Guard on 15 July 1917. Quickly called to act of duty as America entered the war, Private Treptow found himself serving with Company M of the 168th Infantry in the famed and storied Rainbow Division. So nicknamed by then Major Douglas MacArthur, because it consisted of National Guard units that stretched like a rainbow across America. Having landed in France on December of 1917, the 42nd Division found itself fighting in the second battle of the Marne, a battle we Marines know all too well for it was there at Bellow Wood that we earned our nickname Devil Dogs. The Rainbow Division had been in the thick of the fight from the outset. And 104 years ago on this very day, 29 July 1918, the Division would find itself engaged in what would be one of the most important battles of the Great War. Tasked to save Paris from capture and stop what would end up being the last major German offensive of the war, the Division was attempting to take a key hill on the battlefield and was incurring heavy casualties. As the battle raged on, a call went out for a runner to deliver an important message to one of the forward platoons of Company M. In spite of heavy machine gun fire and constant artillery bombardment, Private Trepto, only 24 years of age that day, volunteered for the mission, grabbed the message in hand and ran out into that hellscape. But as he neared the platoon leader, Trepto was killed by a hail of bullets. And on this day, 104 years ago today, this American soldier, this humble dough boy from the Midwest, gave his life on foreign soil in service to this nation. Later in policing up his personal effects, his fellow soldiers found a diary in the pocket of his bloodstained blouse. There, written in Trepto's own hands on the very first page of the book, he had written the words, America must win this war. Therefore, I will work, I will save, I will sacrifice, I will endure, I will fight cheerfully and do my utmost as if the issue of the whole struggle depended on me alone. And I don't know about you, but when I hear stories like this, it makes me ask, what compels a person to feel this way? What motivates someone to struggle so much against even their own personal interest at times? And I think these are questions that only words like honor, courage, commitment, duty, loyalty, service and sacrifice can answer. These are words that live in the hearts and minds of the men and women who are called to serve our nation. And when awoken, they create an unbreakable will. Private Trepto has no stranger to these words. He represents what makes America and everything we sacrifice for so very, very special. The history of the Army and the other services can be defined by people like Martin Trepto. He may have put pen to paper in writing his pledge, but the words that he believed in have been honored by countless others throughout our history. Having been fortunate enough to travel all over the Western sector for the past year, I see this spirit alive and well every single day. Not only in the amazing teams working in the meps, but I see it vividly in the applicants who come through our doors every day. I truly believe it is the lifeblood of democracy that flows through our meps, and that our teams in the meps are the heartbeat that keep that lifeblood flowing. It is truly an amazing thing to witness. The idealism and aspiration of the young applicants who grace our floors every day, who seek to become the best versions of themselves while helping our nation live up to its best ideals, are the very same that inspired young Martin Trepto. They and he were cut from the same cloth. When they raised their right hands in our ceremony rooms and swear to support and defend the Constitution of the United States against all enemies foreign and domestic, and bear true faith and allegiance to the same, when they grace our doors with their enthusiasm and their excitement, they are saying by their actions, I will work, I will save, I will sacrifice, I will endure, I will fight cheerfully and do my utmost. And after spending the better part of 52 weeks traveling and visiting 24 states, 31 meps, two remote processing stations, several of them multiple times, and spending 117,849 miles in the air plus countless road miles together, not to include the time I tried to shove you in the front of a Jeep Liberty, I can positively state that those words are embodied in Command Star Major Jackson as well. We have literally been joined at the hip since the first day I arrived at the Western sector, when I suddenly found myself on a four-hour flight to Boise within hours of checking into the command, not of assuming command, just checking in. And truth be told, though, I relished that flight because it gave Sergeant Major Jackson and me a chance to jumpstart the all-important mind-melt between a unit's commander and senior enlisted leader. That relationship is so special and so important, and I was instantly aware of just how lucky I and the Western sector were. What I didn't realize at that time was that Command Star Major Jackson has such a high-level travel status with all the airlines, because of all the travel he'd already done in the job, that he had to actually make special arrangements with the airlines to sit way back in steerage with me. But that's our Major Jackson, always taking one for the team. We converse the entire four hours, and in retrospect, I also didn't realize at that time how uncommon that would be. Not that we don't talk, and we talk all the time, rather how uncommon it would be that he was only talking to me. Because often, you know, one of the first things people observe about Sergeant Major Jackson is, you know, after the obligatory joke about his name and the obligatory comment about his height is that he has a quiet demeanor. Trust me, having a quiet demeanor doesn't mean that he doesn't have something to say. In fact, once he starts talking, he has a lot to say, and trust me, when he starts talking, you want to listen, because his advice is well worth the price of admission. In all our traveling together, I quickly learned that whether we were driving to the airport, waiting for a flight, boarding a flight, disembarking a flight, waiting for our bags to arrive in the same state, driving to a hotel, he was always on the damn phone. I almost couldn't get a word in edgewise sometimes. So who was he talking to, you ask? Well, typically it's one of the six battalion senior enlisted advisors, but it was just as likely that he was talking to someone from a meps or someone back in our office, or any number of other people from the Joint Force, Army Human Resources Command, our recruiting partners, he was always in the fight, always working to serve our teammates and partners in western sector, helping them iron out issues, address difficult challenges, or otherwise ensure they had what they needed to succeed. Whatever people needed, Sergeant Major Jackson was going to do his utmost and work tirelessly to ensure they had whatever they required to accomplish their mission. Instead of relashing on a flight, I've seen him spend three hours on his little bitty work iPhone, thumbing away at a three page email, just so he could send it once we got back into cell phone coverage. And although he was constantly working behind the scenes to solve problems, Sergeant Major Jackson always leads from the front, setting a tremendous example for others to follow. He plays senior enlisted advisors where they would learn and perform well, and then gave them the most precious resource any of us has to give, his time and energy to ensure that they would succeed. He allowed C's to lead within their battalions and meps, upholding the highest of standards and his interaction with all of them. All of those he took under his wing as coach, mentor, father figure at times, resulted in an incredible amount of growth and development and tremendous success. But Command Sergeant Major would tell you it's not about him. And his proudest moments were always when his people succeeded. Indeed, success for a leader is defined by our lasting impact upon those we developed. And believe me, for Sergeant Major Jackson, it's a long list. There is no doubt that he has left an indelible mark on the Western sector, on the lives of the leaders he developed, and on the service members those leaders will go on to develop. If I could sum up Command Sergeant Major Jackson in one word, it would be servant leader. And for the record, I know that's two words, but no one ever accused Marines of counting so good. It's our major. I could cite chapter and verse, quote, any number of statistics to quantify your impact here in the Western sector. But you have had an incalculable impact upon me, upon the few of us on the command deck, upon the few dozen of us in the Western sector staff, upon the dozens upon dozens of senior enlisted advisors you've mentored and grown, not to mention the 1400 plus teammates of the Western sector. You took advantage of an opportunity rarely afforded someone to exert great leverage and create a lasting impact. As something we often discussed as a canvassing recruiter, 73 patriots joined the Army under your care. And as a drill sergeant, you impacted hundreds more by forging new recruits into soldiers. And now here in Western sector, over 133,000 soldier, sailors, airmen, Marines, guardians, guardsmen have joined in service to their nation under your watchful eye and ever-present influence. Truly, you have lived up to the spirit of young Martin Treptow. And I want to thank you for your work, your sacrifice, your endurance, and for fighting cheerfully to do your utmost. I want to thank you for bringing, for what you brought to the fight each and every day. Thanks for helping make Western sector U.S. MAPCOM the Department of Defense in our nation and the world a better place. It has been my honor and privilege to serve alongside you and try to keep up as best I could. Angie, thanks for letting us borrow your husband for the past 32 months. Especially during COVID and all that entailed. I tried to get him home to you as much as I could, but I know there were challenges caused by our incessant travel schedule. In this business, we know that military members cannot do what they do without their family's love and support. So thank you, Angie, Elena, Austin, for all of your service and your sacrifice. We could not do what we do without you. And I know for a fact that as important as everything is that your husband and father has done for the Army, for MAPCOM, for Western sector, and for me. That as meaningful as his impact has been upon those he's led and mentored and developed.  As Team Jackson heads off to Fort Bragg in your next big adventure with the 18th Airborne Corps, I wish you all, as we say in the Marine Corps, fair winds and following seas. And now, with that said, I'm sorry, Major Rendon, as you step into the breach, I hope you are ready to work, to save, to sacrifice, and to endure because this job demands no less. And I know that you're ready. You know, it's always with a sense of trepidation that a commander welcomes a new partner into their lives. And because we so often do unto others, as has been done unto us, within a few short hours of his own arrival, we had Command Sergeant Major Rendon on a plane with us for his very own four-hour flight to kick-start his orientation and turnover. And after that opportunity to get to know him personally and professionally, well, I'm happy to report that apparently lightning can strike twice. So I feel very lucky to have Command Sergeant Major Rendon joining the Western Sector Team, and Susie and Sophia, and Sarah and Isabel, who are watching on the interwebs. Not only are we thrilled to have you as part of the Western Sector Team, but Jackie and I are very excited to have you as neighbors down the street as well. And for everyone else, Command Sergeant Major Rendon arrives here after most recently serving as the G3 Sergeant Major at the Army Human Resources Command, Fort Knox, Kentucky. There, he provided direct staff support to the commanding general, chief of staff, G3, and the Command Sergeant Major. And most importantly for us, it means he knows where all the skeletons are buried. And he is no stranger to MEPCOM, or to the Western Sector, having served as the Los Angeles MEPPS First Sergeant from 2011 to 2013. So in a sense, this is much less of a welcome and much more of a welcome back. In either event, Sergeant Major, like they tell us every time we have to fly Southwest Airlines, sit down, strap in, and hang on, because it's going to be one heck of a ride. Our mission never stops and the sun barely sets on the Western Sector. So we're about to hit the road to support our teammates who work each and every day to ensure that those young patriots who choose to become tomorrow's soldiers, sailors, airmen, marine, coast guardsmen, national guardsmen, and guardians have the requisite mental, moral, and physical qualities to join us as uniform members of the armed forces of this great nation. I know they like to unleash the beast next door on the east side, but here on the west side, no matter what anyone else says, we ride and die on the best side. So welcome aboard. Now let's get to work. Ladies and gentlemen, the outgoing senior enlisted advisor for Western Sector, U.S. military entrance processing command, command Sergeant Major Michael Jackson. All right, so for those of you that know me know, I'm not usually a man in many words, but when you give us our major microphone, all that goes out the window. So I'm not responsible for what happens after that. All right, distinguished guests, Ms. Miller, Colonel Stallings, Captain King, Colonel Cutter, fellow Sergeant Major's families, friends, service members, and civilians of U.S. MEPCOM. Good day to you all. And thanks for taking the time out of your busy schedules to attend today's ceremony. Your presence is truly appreciated. First and foremost, I would like to thank God for all of these continued blessings. I would also like to thank my family who is here with me today for their love and sacrifice. I look forward to our next chapter of the journey, and I hope I have enough energy to keep up with my son over the next few days because I know he's going to try to run me in the ground. Ms. Miller, thank you for spending a few minutes here with us today. We truly appreciate that. I truly appreciate the support you have provided us up in this session's policy, and I know you will continue to advocate for us as you continue to serve as your next role. So thank you for spending time. Colonel Stallings, thank you for your continued support of the sector as we transitioned into the Ramirez 1.1, and Ms. Genesis, all the medical modernization, and all the challenges that have come along with them. You've been a great boss to have, and I look forward to support, and I thank you for your support and understanding as it is greatly appreciated and has given us the ability to do our mission. Captain King, thanks for showing up for your old battle buddy today. And thank you for laying the groundwork for me as I transitioned into Western sector nearly three years ago now. I clearly recall our first interaction as it set the tone for what our working relationship would form into. So I drove into North Chicago on a Saturday morning in mid-October and naturally was snowing already. But by the next afternoon, I was in the airport on my way to the first of many MEPS visits. And I met it with my predecessor just prior to boarding, and he informed me that Captain King was already on the plane. As I entered the boarding door to the airplane, there sits Captain King in the first seat in first class with this huge grin on his face. So he then proceeds to tell me, Sergeant Major, make sure you keep the noise down as you make your way to the back of the plane. I looked at him and said, OK, that's what we're going to do, OK, all right. So I knew at that moment that we were going to get along just fine. So, sir, thank you for your leadership and your continued support, and I'm a better leader for having served with you. I know you're down in Miami, living a J-Fresh life, shining brightly as only you can. To my commander, Colonel Showbird, sir, thank you for your kind words.   You jumped in headfirst with no knowledge of what it is we do in MEPCOM, and you totally immerse yourself in the culture. You listen to my advice, you have my back at all times, and we work break together to run the sector within your intent. Thank you for your leadership, dedication to our mission, and the latitude you gave me to get after your priorities. You finally come into your own, and now I can no longer send you to the back of the plane. The Western sector will continue to excel under your command, the new Jackie and the family, fair winds and following seas, that's that jointness rubbing off on me, as you continue to lead the Western sector team through medical modernization and beyond. Commander Midnass, you are here back in the back. Appreciate you coming. Couldn't have asked for two better deputies to go to battle with on a daily basis, first with now Captain Mack and then Commander Midnass, who are also known as D-1 and D-2. As I always say, all roles lead to the deputy, because the deputy is a heartbeat who runs the sector, juggling all the chain saws while the commander and I are out on the road. There was never any loss of continuity and never a hint of concern that you didn't have everything under control here at the headquarters. I know you will continue to crush it in your next job in Millington. Finally, the Navy got something right this year. To my U-9 counterparts, Commander Sergeant Major Woodson and Chief Page, the team we built helped keep each other sane when things got hectic. Thanks for being great teammates and wingmen who always had my back if I ever needed anything. I will miss the camaraderie we shared and I'm always a phone call away. Most importantly, Chief Page, thanks for always being there to be second place to West Side. You might need to counsel him a couple of extra days of the week for that. The headquarters staff, thank you for your tremendous support for us here in the sector. Your dedication to the MEPS has been invaluable as they work tirelessly to execute their role in the sessions mission. The MEPS commanders and senior elicit advisors, past and present, you are the leaders. You are the engine that powers the machine and you are the standard bearers. Continue to stay at the tip of the spear. Continue to develop our junior service members and keep showing them that MEPCOM is not the place that their careers will come to die. Be the positive example for them as well as the applicants who walk in your MEPS. They aspire to be a part of something greater than themselves and you are the first example that they see of that. I look forward to seeing great things in the future from every single one of you. To our civilian workforce, you are the continuity that keeps us operating at the highest level every single day. Our military personnel come and go every few years and your professionalism is the main reason we continue to keep operating at those high levels, even in the face of an unprecedented global pandemic. You are the fabric and the backbone that will keep this command strong. COVID-19 pandemic was and is one of the most challenging situations this organization has endured. When the SEC defamed the recruiting mission to be mission essential, that made this command to be mission essential. And our personnel answered the call in the face of this pandemic every single day and continue to deliver that exceptional service on a daily basis. Our relationship with our recruiting partners is one that is built on communication, trust and constant coordination. We must remember that we are here to support their efforts, especially during this time of uncertainty. The leadership in our meps fully understand and execute this daily with precision, balancing all requirements while taking care not to excessively overburden your teams in the process. You demonstrate the art and science of leadership in action on a daily basis and it has been a pleasure to have a front row seat to witness that. All those numbers that were mentioned earlier by Colonel Schauberg, not one single applicant comes through the doors of the headquarters in North Chicago. They walk through the meps doors every single day and you are the ones that provide that world-class support. The great Michael Jordan once said, talent wins games, but teamwork and intelligence wins championships. I'm truly proud to have been on our winning team, the West Side, not East Side. And I try my best to be intelligent enough to not get in the way of our great teammates to execute the mission. I truly enjoyed my time here in Western Sector. It's been awesome to see our joint community up close in action and it's been honored to serve as a senior leadership advisor alongside the great members of this sector. It's our major rendering. I look forward to seeing the team continue to excel under your watch as they take on the challenges ahead. You have a great commander who will always support you and you have an awesome support team around you. Let them run, take care of them and they will take care of the mission. Freedom's front door, West Side's strong side, this is West Side 7 signing off the net. Ladies and gentlemen, the incoming senior leadership advisor for Western Sector, military entrance processing command, Command Sergeant Major Roger Rendon. I put my scene eyes on. Private Tupto, man that dude was awesome. Good morning everybody, this is Miller, Command Sergeant Major McAdoo, Colonel Stallings, Command Sergeant Major Woodson, Mr. Phillips, Colonel Cutter, Chief Page, Commander Becker, and a special shout out to the members of the AG SEC watching online. She yields up. Officers, NCOs, civilians and family members here and online. Thank you for joining me and my family on this very humbling and very great occasion. We thank all members of the armed forces that are currently here in the civilian workforce present. Truly appreciate it. I know all, I and all sort of songs are what's keeping us from the reception. And in honor of National Hot Wings Day, which is today, I didn't know, we're going to have hot wings downstairs. So that's awesome, right? So we're already winning. Some cupcakes and other things, but wings rule the day. I want to thank my family, my wife Susie, daughters Sarah, Isabel and Sophia, my future son-in-law Julio, and grandson Joaquin for having the intestinal fortitude to endure another one of these jaunts. They've been in a few. I would apologize, but now right now the real apology is going to come later on sometime in December, hopefully on a beach somewhere hanging out. Guaranteed to be a great time. Being a family, I got to do this. Recently before leaving Fort Knox, and I want to do this here, my wife Susie was recognized as the South Central Kentucky Red Cross Chapter Volunteer of the Year for her work at Fort Knox Warehouse, the Warrior Warehouse and with the Mayfield and Dawson Springs Tornado Relief last year. So round of applause for you Susie. Susie and for the rest of the military spouses. Thank you is never, and I mean never going to be enough. But for now, that's all I can give. Thank you. I also want to thank Phil McCarn. So he's right up front. Phil was my paralegal specialist when I was at Second Range of Italian at Joint Base Lewis-McCord. And he's the one keeping me straight right now. So if I'm legal, I'm good. So thanks Phil for being here. I appreciate it. And shout out to Mr. Antonio. Everybody knows him as Tony Nieves. He works here obviously in, you know, the other side. It shall not be named. But Mr. Nieves was my NCOIC, my first NCOIC in the Army. And so it means a whole lot for him to be here. And I can honestly say that if it wasn't for you, I wouldn't be in the Army anymore. That's a fact. That is a straight up fact. All right, folks. I appreciate the reception and support that Western Sector and MEPCOM have given me and my family. You all opened the doors and made us feel right at home, even though we're hanging out in Navy Lodge for the next few weeks. But that's okay. So is everybody else. I got no problem with that. Thanks. And Sergeant Major Jackson, thank you for providing me with the product that you have so far. It is awesome. I truly appreciate everything that you've done for not only Western Sector, but honestly, for all of DOD. I mean, think about it, folks. A lot of folks come through Western Sector a lot. Any Western Sector too, but you know. Good luck on your next assignment. You and your family are going to have a great time. But remember, feet and knees together, man. Feet and knees together. And you're with 6'4", 6'5", right now? Get ready to be like five feet something. I was six feet before. All right. So having traveled all around the best coast already, and again, yes, this is the best coast. It is, believe me. Hawaii, Guam, Alaska, California. What's not to love about that? Having gone over a few maps already, I can tell you that they are doing amazing things. Everybody knows that. So 31 maps to remote processing stations, and they are responsible for testing, processing. Everybody knows this, right? And we're processing Army and Navy Air Force Marine, Space Force, Coast Guard. They're our future. Our future, all right? So make no mistake, this will not be an easy endeavor. And I already know this. And, sir, believe me, I'm ready. We are in a war for talent right now. Everybody reads the news, you hear it. The same talent that Microsoft, Abbey, Walmart, Ford, Amazon, McDonald's, yeah, they're all throwing money at them, all right? Giving them all kinds of perks, offering all kinds of things to join their organization. So this is where we come into play. We must treat our national treasures as if they were our children, because sometimes they are, walking through freedom's front door, our kids, all right? So this is why MEPCOM exists. This is why we exist here, all right? And I don't take that lightly. Right now, a young applicant, somewhere in the United States, whether it's the West Coast or East Coast, is walking through one of those MEPs, getting ready to process whatever he or she's doing. And they're a little apprehensive, a little nervous, wondering if they made the right decision, all right? And they come from different cultures, different backgrounds, different upbringings. They look like us when we were coming through, all right? I came through LA MEPs, the old LA MEPs, not the new one, all right, on Rodeo Road. Not the Rodeo Drive, guys, all right? Wondering if this is the profession that they chose that they're choosing, if it's the right thing to do. And the first people that they see, aside from the recruiters, is us. They see civilians, they see those process NCOs, those test coordinators, they see all of us. And so guess what? We have to treat them with dignity and respect as soon as they walk in, all right? They all have one thing in common, they want to serve our nation, all right? They want to be something bigger than ourselves, than themselves. So that is the tip of the sphere that I am really looking forward to be a part of. And what a great day it's going to be. But what now, all right? Sir, I humbly and graciously take this position. I'm ready, all right? To be your battle buddy, your right-hand man, to do every single thing that needs to be done to make Westside the best side. It already is. We're just going to make it a whole lot better, all right? To the NCOs of the Western sector, we come from all brass of the service from the active reserve and guard, but we are and will continue to be the backbone of MEPCOM. We will continue to set examples for others to follow. We will be mentally alert and morally straight in our daily duties. We will be physically strong as well as never forget that we represent our respective branches of the service to the rest of Western sector. This is an organization where mutual respect and trust is paramount. And this applies to everybody. I work for you. And so I must, on a daily basis, earn your respect and trust, all right? This is not just once a day, once a week. No, every minute of every day. I am here for you. George Bernard Shaw once said, this is a true joy in life, the being used for a purpose recognized by yourself as a mighty one. And team, this, this is a mighty effort indeed. Again, thank you all very much for attending today. I truly appreciate it. Best in the West, Freedom Front Door, Army Strong. Westside 7, signing in. Please rise and remain standing for the playing of the service songs and the departure of official party.