00:00:04.884 --> 00:00:08.808 Cool. Today we are going to be talking about the pipelines and
00:00:08.808 --> 00:00:12.670 the release pipelines and prod deployments and then I'm going
00:00:12.670 --> 00:00:16.282 to be walking through the current phase one setup. I know
00:00:16.282 --> 00:00:19.895 that we talked about Docker earlier and that could end up
00:00:19.895 --> 00:00:23.632 being part of the process, but this will kind of talk about
00:00:23.632 --> 00:00:27.556 what those deployments look like and then just kind of walking
00:00:27.556 --> 00:00:30.234 through what that phase one looks like so.
00:00:31.824 --> 00:00:34.224 Let me get set up because I was.
00:00:35.484 --> 00:00:37.894 Not ready, not paying attention. So that's good.
00:00:41.144 --> 00:00:41.484 Cool.
00:00:43.364 --> 00:00:44.414 So.
00:00:47.344 --> 00:00:51.976 Let us I'm gonna share my screen here. So the the first thing I
00:00:51.976 --> 00:00:56.173 want to talk about is the the pipelines and the different
00:00:56.173 --> 00:00:58.634 pipelines. And so the way we use.
00:01:00.024 --> 00:01:04.692 The term, like a release like we have our support release branch.
00:01:04.692 --> 00:01:04.904 Uh.
00:01:05.964 --> 00:01:10.086 Azure also has the concept of a release and a pipeline. However,
00:01:10.086 --> 00:01:13.384 they're both technically pipelines that run, so the
00:01:13.384 --> 00:01:17.126 pipelines here if you go to. If you go to Azure, this blue
00:01:17.126 --> 00:01:20.994 rocket pipelines are our PR analyzer and build pipelines and
00:01:20.994 --> 00:01:24.990 then releases are our deployment pipelines and so you can find
00:01:24.990 --> 00:01:29.048 those in both. So just kind of walking through navigation here.
00:01:29.048 --> 00:01:32.854 So in the pipelines now what's funny about this and kind of
00:01:32.854 --> 00:01:36.786 joke about it is that you can definitely tell that these were
00:01:36.786 --> 00:01:38.054 created by the same.
00:01:38.174 --> 00:01:39.514 By two different like.
00:01:41.994 --> 00:01:45.164 People like two different groups within within Microsoft because
00:01:45.164 --> 00:01:48.286 they're close and the formatting is all the same, but if you go
00:01:48.286 --> 00:01:51.212 to pipelines that has recent all and runs and you know some
00:01:51.212 --> 00:01:54.188 different different things here and you have to go to all in
00:01:54.188 --> 00:01:56.870 order to get to the folder structure. But if you go to
00:01:56.870 --> 00:01:59.845 releases, they've got a whole different UI looking thing. So
00:01:59.845 --> 00:02:02.626 it does kind of take some getting used to to see both of
00:02:02.626 --> 00:02:04.284 these. So if you go to pipelines.
00:02:05.114 --> 00:02:08.690 And then you go to all. Each version is broken down. So for
00:02:08.690 --> 00:02:12.325 example, if we go 2022.4, here are all the PR analyzers that
00:02:12.325 --> 00:02:15.901 run which these are look like they're running. Well, that's
00:02:15.901 --> 00:02:19.774 good. Just kidding. And then the releases. So these are actually
00:02:19.774 --> 00:02:22.992 the build. So when it talks about releases, we should
00:02:22.992 --> 00:02:26.866 probably say we should probably mark these as builds, but that's
00:02:26.866 --> 00:02:30.144 this is just our current naming structure for our COM.
00:02:30.214 --> 00:02:34.253 For for core, but you can see pull requests analyzer and then
00:02:34.253 --> 00:02:37.837 release is the CI. Now for clients we have changed the
00:02:37.837 --> 00:02:41.550 nomenclature to be that CI. So this is part of the C ICD
00:02:41.550 --> 00:02:45.134 process. And can anybody tell me what cicd stands for?
00:02:48.044 --> 00:02:50.404 Continuous integration and continuous deployment.
00:02:51.364 --> 00:02:55.079 Uh, yeah, I think that see the CD is it's deployment. There's
00:02:55.079 --> 00:02:58.914 also like delivery as well. Like it kind of goes back and forth
00:02:57.264 --> 00:02:57.604 Umm.
00:02:57.394 --> 00:02:57.844 Every.
00:02:58.914 --> 00:02:59.154 but.
00:02:59.354 --> 00:02:59.844 Man.
00:03:00.674 --> 00:03:03.146 I I think it's you know we we kind of say the continuous
00:03:03.146 --> 00:03:05.704 deployment is I think is fine if I say it all the time so.
00:03:06.014 --> 00:03:09.919 Umm, but pipeline is the CI part the continuous integration and
00:03:09.919 --> 00:03:13.396 then the releases is the CD part. So you can think of it
00:03:13.396 --> 00:03:17.301 like that. So we use that naming convention now for clients. So
00:03:17.301 --> 00:03:20.839 for example if I go to like region so you can see CI then
00:03:20.839 --> 00:03:24.744 the client name, the environment and then the application so we
00:03:24.744 --> 00:03:28.649 don't have a web setup. I need to set web up for this phase one
00:03:28.649 --> 00:03:32.553 setup so that people have them. But for now it's just the stuff
00:03:32.553 --> 00:03:36.397 side. So but that's the naming convention there. And if you go
00:03:36.397 --> 00:03:37.434 over to releases.
00:03:37.824 --> 00:03:39.114 You can see something similar.
00:03:40.114 --> 00:03:45.524 If you go to 2022.4 releases, so sorry clients region.
00:03:46.684 --> 00:03:49.036 Yeah, you'll see the CD and it'll be the same. Same
00:03:49.036 --> 00:03:49.624 structure so.
00:03:51.064 --> 00:03:54.505 I am actually going to walk through the Rockingham
00:03:54.505 --> 00:03:58.687 Rockingham just on boarded this week and they had their sales
00:03:58.687 --> 00:04:03.072 handoff or their sales kickoff, not sales kickoff, their project
00:04:03.072 --> 00:04:07.120 kickoff today. And so I was going to walk through the phase
00:04:07.120 --> 00:04:09.684 one setup of Rockingham on this call.
00:04:10.514 --> 00:04:13.601 I think kind of go from there. So I actually haven't done one
00:04:13.601 --> 00:04:16.787 in a couple weeks, so we'll see how resty, resty. I am and note
00:04:16.787 --> 00:04:19.824 that we're still looking at automating more of this process.
00:04:19.824 --> 00:04:23.011 Obviously, as Docker comes in, we'll have more as well. But the
00:04:23.011 --> 00:04:24.604 first part is to create the new.
00:04:26.294 --> 00:04:30.184 The create the new branch so I have it.
00:04:33.984 --> 00:04:36.234 Here new clients.
00:04:38.254 --> 00:04:38.984 Ohhh my gosh.
00:04:42.934 --> 00:04:45.684 Uh, OK, good, that's.
00:04:49.994 --> 00:04:54.814 I will go ahead and get onto the release so any new client builds
00:04:54.814 --> 00:04:59.050 off of the latest release, so we'll start. We'll start by
00:04:59.050 --> 00:04:59.854 doing that.
00:05:08.994 --> 00:05:09.784 Yeah, type today.
00:05:15.424 --> 00:05:17.894 Cool. And then we'll check out the new branch.
00:05:18.744 --> 00:05:20.474 And real quick, while I'm thinking about it.
00:05:20.914 --> 00:05:21.374 Yeah.
00:05:22.164 --> 00:05:24.614 Is it rock? Sorry. I just want to make sure it's rock.
00:05:22.634 --> 00:05:23.204 I.
00:05:25.354 --> 00:05:26.314 Yeah, rock. OK, cool.
00:05:27.434 --> 00:05:28.074 Go ahead. Sorry.
00:05:28.874 --> 00:05:32.377 Something that you might have already asked or covered and I
00:05:32.377 --> 00:05:35.765 was writing some code so it wasn't fully paying attention,
00:05:35.765 --> 00:05:39.038 but does anybody have any questions on what the value of
00:05:39.038 --> 00:05:40.474 CI CD is or why we do it?
00:05:41.414 --> 00:05:43.733 Yeah, I was gonna get into that one. So we got, once I go make
00:05:43.733 --> 00:05:45.831 the pipelines, but yeah, definitely. If anybody has that
00:05:44.764 --> 00:05:45.094 OK.
00:05:45.831 --> 00:05:46.604 now, that'd be great.
00:05:52.224 --> 00:05:56.334 We cover that here in a second. Once I start making the pipeline
00:05:53.694 --> 00:05:54.864 Go. Yeah.
00:05:55.674 --> 00:05:57.714 So it allows us to oh, sorry.
00:05:56.334 --> 00:05:56.524 OK.
00:05:57.254 --> 00:05:59.004 Yeah, no, go ahead, Tim. Go ahead.
00:05:58.454 --> 00:06:01.970 I was just gonna say it allows us to like really get in like a
00:06:01.970 --> 00:06:05.430 rhythm step with our, with our scrum development, right. Like
00:06:05.430 --> 00:06:08.388 if we if we instead of if we were using the old like
00:06:08.388 --> 00:06:11.905 waterfall method right, like it it took us six months to put a
00:06:11.905 --> 00:06:15.365 project out you know and we did one big push and then release
00:06:15.365 --> 00:06:18.881 every six months or however long it takes for the project that
00:06:18.881 --> 00:06:22.342 that would be you know something that was in step with how we
00:06:22.342 --> 00:06:25.858 develop. But we develop under scrubs with two week sprints and
00:06:25.858 --> 00:06:29.039 every two weeks we could potentially or sooner like like
00:06:29.039 --> 00:06:29.374 CI CD.
00:06:29.534 --> 00:06:34.734 Could push out a release daily, right? Like if we wanted to. So
00:06:33.634 --> 00:06:34.024 Sir.
00:06:34.734 --> 00:06:35.384 it just.
00:06:36.404 --> 00:06:40.674 It goes hand in hand with Scrum and Edge all development and
00:06:40.674 --> 00:06:42.214 helps us to push code.
00:06:43.064 --> 00:06:48.454 To the client, to the production site. Much faster, right?
00:06:49.204 --> 00:06:54.033 Yeah. Well, and for clarity it it it actually one that's 100%
00:06:54.033 --> 00:06:58.629 correct, but for clarity it's even it's it's slightly more
00:06:58.629 --> 00:07:02.134 than that because we tried to adapt to that.
00:07:02.214 --> 00:07:06.209 That you know, because we do develop off of agile and scrum
00:07:06.209 --> 00:07:10.138 that we were, we were manually deploying QA stage and prod
00:07:10.138 --> 00:07:14.266 whenever we had something ready which obviously slowed things
00:07:14.266 --> 00:07:18.195 down right. So like people didn't want to do it, we didn't
00:07:18.195 --> 00:07:22.190 want to put the time in, it would take forever. It was just
00:07:22.190 --> 00:07:26.118 one of those things where it just took a while to do these
00:07:26.118 --> 00:07:29.914 manually. And So what this process does is it takes that
00:07:29.914 --> 00:07:32.444 and automates it so that deployments.
00:07:33.014 --> 00:07:35.901 Can either happen automatically in a QA and stage environment or
00:07:35.901 --> 00:07:38.744 in a prod environment the build can happen. The artifact can be
00:07:38.744 --> 00:07:41.586 sitting there. We'll talk about what those are here in a little
00:07:41.586 --> 00:07:41.764 bit.
00:07:42.944 --> 00:07:47.417 And a deployment is a click of a button and it takes. I don't
00:07:47.417 --> 00:07:51.963 know 2-3 minutes. I think to to copy that thing down, unzip it
00:07:51.963 --> 00:07:56.725 and then turn off the app pools, turn it back on or change it and
00:07:56.725 --> 00:08:01.126 then rezip it or turn the apples back on. So right the major
00:08:01.126 --> 00:08:02.064 value is the.
00:08:03.094 --> 00:08:06.490 The fact that we can push updates more more regularly, but
00:08:06.490 --> 00:08:10.232 but what we do, you know the way we used to do it is that we can
00:08:10.232 --> 00:08:13.456 push more updates, more regularly easily without having
00:08:13.456 --> 00:08:17.026 really anybody have to have like a ticket in their Sprint. It
00:08:17.026 --> 00:08:20.480 just a PR goes in and it just does it. So but yes, and then
00:08:20.480 --> 00:08:23.934 Brendan, do you have, did you have anything to add to that?
00:08:25.054 --> 00:08:25.224 No.
00:08:25.294 --> 00:08:26.794 Well, that's pretty much all I was thinking.
00:08:26.894 --> 00:08:28.704 Uh, just.
00:08:27.524 --> 00:08:27.834 We.
00:08:30.254 --> 00:08:30.674 You know.
00:08:32.124 --> 00:08:32.884 What do you call it?
00:08:34.344 --> 00:08:38.372 The old back in my day, you know when I'm when I started, we had
00:08:36.704 --> 00:08:37.754 That's right.
00:08:38.372 --> 00:08:42.401 to do the we had to RDP into Dev Force One and get pull and then
00:08:42.401 --> 00:08:46.181 build the front of him back in manually. And if somebody had
00:08:46.181 --> 00:08:50.086 uncommitted files changed over there, we just had to hope that
00:08:50.086 --> 00:08:53.742 there were no merge conflicts when we pulled latest and if
00:08:53.742 --> 00:08:54.734 there were then.
00:08:55.664 --> 00:08:59.394 You know, figure it out, and who knows how long that takes so.
00:08:57.414 --> 00:08:57.864 Sir.
00:08:59.974 --> 00:09:00.444 There.
00:09:00.734 --> 00:09:02.844 All that crap is.
00:09:01.644 --> 00:09:02.264 Create a bit.
00:09:05.294 --> 00:09:08.084 Is no more with pipelines, which is very nice.
00:09:08.374 --> 00:09:09.444 Indeed. OK.
00:09:08.964 --> 00:09:12.014 How long ago were we talking about? Sorry to interrupt.
00:09:12.394 --> 00:09:13.374 No, you're good. You're good.
00:09:13.464 --> 00:09:17.318 Dinosaurs roamed the earth. It was, it was in a little year.
00:09:16.254 --> 00:09:16.984 OK.
00:09:17.318 --> 00:09:20.224 You might not have heard of called like 2020.
00:09:21.254 --> 00:09:21.824 Ohh jeez.
00:09:21.914 --> 00:09:22.204 OK.
00:09:22.534 --> 00:09:25.660 Well, I don't know. You're still doing 2021 too? I think so. For
00:09:25.660 --> 00:09:26.814 the most part, but yeah.
00:09:26.004 --> 00:09:28.860 Yeah, it was. Yeah, it was in. It was like, up through it was
00:09:28.860 --> 00:09:31.763 up through like, mid late 2021, I think was when we started to
00:09:31.763 --> 00:09:33.974 really getting into pipelines for client sides.
00:09:34.554 --> 00:09:38.036 Yep, indeed. OK, so now I've created the branch, at least
00:09:38.036 --> 00:09:41.939 locally, and then I just. You'll have to remember the other one.
00:09:41.939 --> 00:09:45.661 You'll have to remind me the other one that have to do, but I
00:09:45.661 --> 00:09:49.143 typically will come in and I will copy this clarity react
00:09:49.143 --> 00:09:50.524 skin for the overrides.
00:09:51.944 --> 00:09:53.474 And I will name it.
00:09:55.994 --> 00:09:56.444 Oops.
00:09:57.644 --> 00:10:00.708 The clients folder and then there was another one. Jesse.
00:10:00.708 --> 00:10:02.504 What what? What one am I missing?
00:10:03.174 --> 00:10:03.624 Well.
00:10:03.264 --> 00:10:04.284 Is it in the react?
00:10:04.424 --> 00:10:07.494 Yeah, that's for like a deal. I mean, if you need to react
00:10:07.494 --> 00:10:10.460 overrides, that's where you right. You're already there.
00:10:10.460 --> 00:10:13.583 Yeah, exactly. You know, you were also in that copied skin.
00:10:13.583 --> 00:10:16.913 There's a couple things that you know, since that's a DNN skin,
00:10:16.913 --> 00:10:20.191 right. There's a couple things that it directly references the
00:10:20.191 --> 00:10:23.366 name of the skin, like, you know, import CEF store main from
00:10:23.366 --> 00:10:26.540 slash portals, default skins, clarity react. You just made a
00:10:26.540 --> 00:10:29.610 new one and you called it something else. So you'd have to
00:10:29.610 --> 00:10:32.889 make sure you go in there and change the word clarity react to
00:10:32.889 --> 00:10:34.814 files to whatever you just named it.
00:10:35.014 --> 00:10:38.967 You know, because it's we use that with a stem link, right? So
00:10:38.967 --> 00:10:39.344 it it.
00:10:40.114 --> 00:10:42.686 DNA just needs to know where to pull the files from, but yes,
00:10:42.686 --> 00:10:45.216 this is this is where you do the overrides. Yeah, that's the
00:10:45.216 --> 00:10:45.714 other thing.
00:10:45.994 --> 00:10:47.104 So I need a copy this.
00:10:48.244 --> 00:10:48.434 Yeah.
00:10:49.384 --> 00:10:50.494 Make this rock.
00:10:52.364 --> 00:10:52.694 Well.
00:10:54.154 --> 00:10:57.124 And then I will add those and commit them.
00:11:04.284 --> 00:11:07.974 Sounds so much cooler than what it actually is the rock skin.
00:11:09.614 --> 00:11:13.094 Cool and cause I haven't put any branch policies on yet. I'm just
00:11:13.094 --> 00:11:14.254 going to push to main.
00:11:15.384 --> 00:11:18.194 OK, OK. So now that the branch is set up.
00:11:18.954 --> 00:11:21.850 Yeah, we can go set up the QA pipeline and typically once I'm
00:11:21.850 --> 00:11:24.419 done with the, once I'm done with the, the majority is
00:11:24.419 --> 00:11:27.455 process. I'll go back in and do stage. I'm not gonna do stage on
00:11:27.455 --> 00:11:30.210 the call, so we can switch to other things. I'm just gonna
00:11:30.210 --> 00:11:32.966 walk through QA, but it'll be the same process. So. OK. So
00:11:32.966 --> 00:11:34.554 then I will go through pipelines.
00:11:36.144 --> 00:11:40.914 And all and I will go to 2022.4.
00:11:41.694 --> 00:11:43.874 And I will grab the UM.
00:11:45.364 --> 00:11:49.334 The latest release pipeline and I will.
00:11:51.784 --> 00:11:54.624 At it, I think it's at it or no. I kept to click on that. Sorry.
00:11:56.164 --> 00:11:59.314 So you click on it and then you can export to Jason.
00:12:00.434 --> 00:12:04.427 Then you come back in here and you can import a pipeline. And
00:12:04.427 --> 00:12:08.484 so I will just import the exact same one that I just exported.
00:12:11.294 --> 00:12:16.920 Uh. And then basically you just change all the variables so it
00:12:16.920 --> 00:12:20.224 this is going to be CCI rock QA SEF.
00:12:21.524 --> 00:12:26.311 Umm for the build pipelines. So this is where the build servers
00:12:26.311 --> 00:12:30.425 come into come into play. So when we do builds we have
00:12:30.425 --> 00:12:34.913 dedicated build servers for the PR analyzers as well as the
00:12:34.913 --> 00:12:39.252 actual builds themselves and that his here on the default
00:12:39.252 --> 00:12:44.039 agent pools and what the agent pools basically are is a series.
00:12:44.039 --> 00:12:48.602 So an agent is it's basically just a service that lives on a
00:12:48.602 --> 00:12:51.594 server that Azure has access to and so.
00:12:51.674 --> 00:12:55.547 You go in and you that you know it tells you there's there's a
00:12:55.547 --> 00:12:56.654 procedure for for.
00:12:56.734 --> 00:13:00.828 Umm creating that server agent and then basically you can that
00:13:00.828 --> 00:13:05.051 server agent exists and then you can add it to an agent pool. So
00:13:05.051 --> 00:13:08.755 theoretically Sev one just relates to one server and one
00:13:08.755 --> 00:13:12.849 agent, but I could technically if I wanted to Add all of these
00:13:12.849 --> 00:13:16.942 agents to default and it would just use those as appropriately
00:13:16.942 --> 00:13:21.036 across those agent pool inside this agent pool. But for builds
00:13:21.036 --> 00:13:25.325 for the build pipeline we always just pick the default so that it
00:13:25.325 --> 00:13:27.924 uses the 20 build servers that we have.
00:13:29.094 --> 00:13:33.951 OK. So then we need to go change the default branch for for the
00:13:33.951 --> 00:13:38.580 scheduled builds and so we just created Rock QA. So we'll go
00:13:38.580 --> 00:13:43.134 change that. Everything else here is just we keep the same.
00:13:45.734 --> 00:13:51.553 Phase one setup, so that's good. So this is a change that we just
00:13:51.553 --> 00:13:52.964 made to fix the.
00:13:53.044 --> 00:13:57.915 The uh with terminal terminal prompt disabled error that
00:13:57.915 --> 00:14:03.469 people were getting on PR's and on builds where it was trying to
00:14:03.469 --> 00:14:08.511 pull latest self configs in previous iterations we used to
00:14:08.511 --> 00:14:13.553 use a pat, a personal access token on the server itself to
00:14:13.553 --> 00:14:14.664 grant access.
00:14:15.764 --> 00:14:19.538 To Azure for the git repo to be able to get pull those stuff
00:14:19.538 --> 00:14:23.498 configs, but they modified that so that we were getting a bunch
00:14:23.498 --> 00:14:26.654 of errors. So Wednesday night a handful of people.
00:14:28.034 --> 00:14:31.959 Went in and fixed all those to now use the Oauth token that
00:14:31.959 --> 00:14:35.884 Azure generates. So we were technically using two different
00:14:35.884 --> 00:14:39.875 ways, one to pull the support clients rock QA here. This git
00:14:39.875 --> 00:14:44.127 sources and this was using Azure Oauth token but then inside the
00:14:44.127 --> 00:14:45.174 task group here.
00:14:46.464 --> 00:14:46.934 Uh.
00:14:49.624 --> 00:14:53.342 Inside the task group is a pull. Later CEF configs and this use
00:14:53.342 --> 00:14:56.770 that say just git pull uh, but we added this authorization
00:14:56.770 --> 00:15:00.430 bearer token and basically the system access token and the way
00:15:00.430 --> 00:15:04.090 it gets this system access token is by enabling it here on the
00:15:04.090 --> 00:15:07.575 allow scripts to access the OAUTH token. So if you see that
00:15:07.575 --> 00:15:11.177 terminal that terminal prompts error again, just go check the
00:15:11.177 --> 00:15:14.779 pipeline that's running for it and see if this is checked and
00:15:14.779 --> 00:15:16.464 if it's not just click check.
00:15:17.434 --> 00:15:20.419 OK, cool. So now we've set those. Everything else is good
00:15:20.419 --> 00:15:21.654 there. We'll go in here.
00:15:23.494 --> 00:15:27.789 So this would be create Seth Artifact 2022.4. So this is just
00:15:27.789 --> 00:15:31.945 the version that it's actually deploying or that's actually
00:15:31.945 --> 00:15:36.517 creating. So this is fine to use instead of the name the artifact
00:15:36.517 --> 00:15:38.734 is going to be the same CI rock.
00:15:39.984 --> 00:15:41.354 QA Seth.
00:15:43.154 --> 00:15:45.988 Everything else is the same in here. If you want, we can go
00:15:45.988 --> 00:15:48.868 through these later or if you wanna take a look and see what
00:15:48.868 --> 00:15:51.844 they're doing, that's fine. But for the most part, these don't
00:15:51.844 --> 00:15:54.536 change across all of the builds, they're just additional
00:15:54.536 --> 00:15:57.558 information for the GULP configs and things like that. The skin
00:15:57.558 --> 00:16:00.250 we changed that to rock. So we will change that and then
00:16:00.250 --> 00:16:02.800 control options and output variables. There's nothing
00:16:02.800 --> 00:16:04.784 really set in there. So we're good to go.
00:16:06.224 --> 00:16:10.198 And then I believe that is it the only thing else is, yeah, in
00:16:10.198 --> 00:16:13.921 here for the triggers. So the trigger was what tells it to
00:16:13.921 --> 00:16:17.958 when to run this pipeline. And so this is whenever like a PR is
00:16:17.958 --> 00:16:21.618 going into right now it's 2022.4. Obviously we don't want
00:16:21.618 --> 00:16:25.529 to run this every time 2022.4 updates we want to run it every
00:16:25.529 --> 00:16:26.854 time rock QA updates.
00:16:28.414 --> 00:16:33.133 Umm, I always change the description here to just say
00:16:33.133 --> 00:16:38.464 build rock QA and then the build number format I changed to.
00:16:40.074 --> 00:16:43.837 Rock. So it would be the source branch, CI rock Seth. And that's
00:16:43.837 --> 00:16:47.079 just a just a revision number. It's not really anything
00:16:47.079 --> 00:16:49.684 specific, but I do go ahead and change that.
00:16:50.854 --> 00:16:53.024 No history and then I will save in queue.
00:16:55.564 --> 00:16:59.301 And the fun thing about the pipelines? The build pipelines
00:16:59.301 --> 00:17:02.214 versus the releases is that when you save it.
00:17:02.894 --> 00:17:07.544 You don't have a place to tell it which folder to go into.
00:17:09.644 --> 00:17:13.305 So if you go back to pipelines, it just automatically puts it
00:17:13.305 --> 00:17:16.434 under where the old one was that you copied it from.
00:17:17.994 --> 00:17:20.284 So I have to move this to.
00:17:20.984 --> 00:17:24.914 Uh clients slash rock.
00:17:28.824 --> 00:17:30.254 And there we go. OK, cool.
00:17:31.554 --> 00:17:35.905 Any questions on the build pipeline, what it does or or
00:17:35.905 --> 00:17:36.604 anything?
00:17:41.934 --> 00:17:45.034 And if there's no questions, I will be calling on somebody to
00:17:45.034 --> 00:17:45.884 tell me about it.
00:17:50.084 --> 00:17:54.154 Uh. All right. Brent Fife, are you there?
00:17:57.314 --> 00:17:58.674 I am here, yes.
00:17:58.764 --> 00:18:01.921 Awesome. Can you just give me a a brief summary of what the
00:18:01.921 --> 00:18:02.974 build pipeline does?
00:18:04.194 --> 00:18:05.124 Uh, I mean.
00:18:06.464 --> 00:18:08.124 It does what I'm.
00:18:09.224 --> 00:18:11.434 Visual Studio does it, builds it, and then.
00:18:12.824 --> 00:18:13.914 Gets ready for deployment.
00:18:14.724 --> 00:18:15.124 Is that?
00:18:15.764 --> 00:18:18.628 Yeah, pretty much. And actually I I did leave. I did leave a
00:18:15.844 --> 00:18:16.104 On.
00:18:16.904 --> 00:18:17.234 Close.
00:18:18.628 --> 00:18:21.445 section out. So technically what the build and and let's go
00:18:21.445 --> 00:18:24.450 through the let's go through the task group here so that we can
00:18:24.450 --> 00:18:26.094 cuz that's a good point, I'm glad.
00:18:28.454 --> 00:18:31.654 Glad that, uh, I asked somebody because I forgot that piece. So
00:18:31.654 --> 00:18:33.054 if I go here into the tasks.
00:18:34.494 --> 00:18:38.736 So ultimately what this does is it you're right, it it basically
00:18:38.736 --> 00:18:42.783 prepares the environment to be able to build. So it pulls the
00:18:42.783 --> 00:18:46.699 latest stuff configs, it does all the NPM installs, it does
00:18:46.699 --> 00:18:49.244 the Nuget restore builds the solution.
00:18:50.354 --> 00:18:54.696 Does the the GULP builds and the NPM build for the for react and
00:18:54.696 --> 00:18:58.638 then it does all the copies that we typically do on Visual
00:18:58.638 --> 00:19:02.580 Studio, but really what ultimate build pipeline does is it
00:19:02.580 --> 00:19:06.922 creates an artifact and So what that does is it takes all of the
00:19:06.922 --> 00:19:10.864 build output files and stores them just in a single folder
00:19:10.864 --> 00:19:15.006 that is the artifact and then zips it up and so that artifact
00:19:15.006 --> 00:19:15.474 exists.
00:19:16.564 --> 00:19:19.024 You know, I I don't know. Brendan, do you know what our
00:19:19.024 --> 00:19:20.254 our default timeout or like?
00:19:21.804 --> 00:19:25.314 Like is for storage or like artifact storage time.
00:19:22.594 --> 00:19:23.444 The artifact.
00:19:24.174 --> 00:19:24.634 I.
00:19:25.654 --> 00:19:28.097 I don't. Uh, it's probably in the Azure setting somewhere, but
00:19:28.097 --> 00:19:29.804 I don't know what it is. I'll stop my head.
00:19:30.144 --> 00:19:33.547 OK, but the cool thing about that is that it stores that
00:19:33.547 --> 00:19:37.070 artifact and it stores it historically as well. And so one
00:19:37.070 --> 00:19:40.474 of the nice things about C MC, the cicd process is that.
00:19:41.344 --> 00:19:44.761 Let's say we go deploy to prod and we're using the CI CD
00:19:44.761 --> 00:19:47.998 pipeline and it deploys the pipeline and something is
00:19:47.998 --> 00:19:51.774 broken. We didn't catch it in UAT. Maybe it is specific to the
00:19:51.774 --> 00:19:55.550 environment, but ultimately we deploy it and it's go like hey,
00:19:55.550 --> 00:19:59.267 they need to get people on the site. Right now the nice thing
00:19:59.267 --> 00:20:02.863 is that those artifacts still exist and so you can go to an
00:20:02.863 --> 00:20:06.700 old release and rerelease that old version and it will grab the
00:20:06.700 --> 00:20:10.236 old artifact that was prebuilt, doesn't have to go rebuild
00:20:10.236 --> 00:20:12.754 anything, it will grab that old artifact.
00:20:12.834 --> 00:20:16.814 And rerelease it so that you can basically revert to an old
00:20:16.814 --> 00:20:20.861 version. Then you can fix the new version before you release
00:20:20.861 --> 00:20:24.709 that one, and that's ultimately another value to the Cicd
00:20:24.709 --> 00:20:28.623 pipeline is that reversion is very simple without changing
00:20:28.623 --> 00:20:29.884 like the code base.
00:20:32.184 --> 00:20:35.045 Umm, OK cool. So now the pipeline, the build pipeline is
00:20:35.045 --> 00:20:37.454 built. So now we'll go to the release pipeline.
00:20:38.844 --> 00:20:44.089 And I will do the same process I'll do 2022.4 releases and
00:20:44.089 --> 00:20:44.534 then.
00:20:46.794 --> 00:20:47.564 The swan.
00:20:48.924 --> 00:20:52.231 So this one doesn't export to Jason or YAML, it just is
00:20:52.231 --> 00:20:52.644 export.
00:20:53.424 --> 00:20:55.004 And then here is import.
00:21:01.624 --> 00:21:02.394 I think it's this.
00:21:03.514 --> 00:21:05.074 Yeah, the one whichever one was.
00:21:05.564 --> 00:21:06.154 Latest yeah.
00:21:06.064 --> 00:21:07.334 Yeah, 256.
00:21:07.984 --> 00:21:10.714 We need to probably not name this thing.
00:21:11.744 --> 00:21:12.584 OK.
00:21:13.694 --> 00:21:17.237 So the first thing I want to do here is we're looking at a
00:21:17.237 --> 00:21:20.359 release is you can see the artifact that's here. So
00:21:20.359 --> 00:21:23.782 obviously we're not gonna release the R 2022.41, so I'll
00:21:23.782 --> 00:21:26.304 click on the artifact and I'll delete it.
00:21:28.414 --> 00:21:30.074 And then we'll add a new artifact.
00:21:34.824 --> 00:21:38.274 It isn't set product and we're going to release rock QA, FCI
00:21:38.274 --> 00:21:41.895 Rock QA. If for whatever reason and again I don't know, I don't
00:21:41.895 --> 00:21:45.175 know if we figured out why it does this. It adds an under
00:21:45.175 --> 00:21:48.569 score to the beginning of this, but that's not actually the
00:21:48.569 --> 00:21:52.133 source alias you have to remove that. I don't know why it does
00:21:52.133 --> 00:21:53.434 that, but it just does.
00:21:54.764 --> 00:21:57.144 So just something that you have to remember to do.
00:21:58.364 --> 00:22:02.052 And then if you click this continue into continuous
00:22:02.052 --> 00:22:06.236 deployment trigger. This is actually how it knows to do it
00:22:06.236 --> 00:22:10.703 manually or automatically. So for QA and stage environments we
00:22:10.703 --> 00:22:14.816 set the continuous deployment trigger to run whenever the
00:22:14.816 --> 00:22:19.426 pipeline for CI Rock QA creates an artifact and that just allows
00:22:19.426 --> 00:22:23.468 us to whenever a PR goes through, the build goes through
00:22:23.468 --> 00:22:27.652 the deployment, goes through and we're good to go for prod
00:22:27.652 --> 00:22:28.574 environments.
00:22:28.844 --> 00:22:30.474 We do not check this.
00:22:30.614 --> 00:22:34.222 Umm and the the reason for that is that if we're just making a
00:22:34.222 --> 00:22:37.772 PR in the middle of the data prod, which we could technically
00:22:37.772 --> 00:22:41.208 do whenever, it's not going to auto deploy at 1:00 o'clock,
00:22:41.208 --> 00:22:44.816 that might be like their peak time that they're getting people
00:22:44.816 --> 00:22:48.252 in the site. Now the deployment process is fairly quick. If
00:22:48.252 --> 00:22:51.803 we're running it on a pipeline. So it's only down for a short
00:22:51.803 --> 00:22:55.296 amount of time, but potentially a short amount of time could
00:22:55.296 --> 00:22:58.446 mean the differences of thousands of dollars for a day
00:22:58.446 --> 00:23:00.164 for a volume heavy client, so.
00:23:01.204 --> 00:23:05.329 For QA and stage environments, This is why no one has to go run
00:23:05.329 --> 00:23:08.359 deployments anymore for pipelines because this
00:23:08.359 --> 00:23:12.484 continuous deployment trigger is checked for prod environments.
00:23:13.264 --> 00:23:16.433 Everyone needs to know that if you're, if you're, you know,
00:23:16.433 --> 00:23:19.655 doing a PR into prod and you're wondering why your your code
00:23:19.655 --> 00:23:22.983 isn't on there, or the changes haven't taken effect, it's very
00:23:22.983 --> 00:23:26.099 possible that just nobody has, nobody has gone and run the
00:23:26.099 --> 00:23:29.480 release, and I'll show you how to run the release manually here
00:23:29.480 --> 00:23:32.596 shortly, but that is, that's actually what that is for. Is
00:23:32.596 --> 00:23:35.554 that in prod we don't wanna automatically run releases.
00:23:35.904 --> 00:23:39.010 Uh, at least by default. You know if if the client wants
00:23:39.010 --> 00:23:42.225 things pushed daily, then OK, that's fine, but that is the
00:23:42.225 --> 00:23:45.440 reason is that we don't want this. Take the site down in a
00:23:45.440 --> 00:23:48.764 peak time. If we're doing a PR in the middle of the day, so.
00:23:49.864 --> 00:23:53.885 Uh, there's that. So I'm just gonna add a quick filter here
00:23:53.885 --> 00:23:55.494 for uh, the rock branch.
00:23:59.654 --> 00:24:04.845 OK, cool. And then I'm gonna go to tasks. I am gonna rename this
00:24:04.845 --> 00:24:05.724 to CD Rock.
00:24:06.874 --> 00:24:08.514 QA SEF.
00:24:11.464 --> 00:24:13.264 Stage name is.
00:24:15.774 --> 00:24:20.972 20190 I didn't pick a server to put this on. I think demo I
00:24:20.972 --> 00:24:25.824 think Dev Dev one is actually pretty open, so we'll do.
00:24:27.024 --> 00:24:33.444 CD Rock 2019. Seth Dev 1.
00:24:35.384 --> 00:24:38.860 And then we'll pick the agent pool. So this is where we talked
00:24:38.860 --> 00:24:42.281 about earlier. The default agent pool is for the builds we're
00:24:42.281 --> 00:24:45.756 going to deploy to CEF Dev 1, so we need to pick that agent so
00:24:45.756 --> 00:24:49.067 that it picks there. So you can technically name the agents
00:24:49.067 --> 00:24:52.432 whatever you want. We always name the agents the name of the
00:24:52.432 --> 00:24:55.798 server that it lives on, which makes sense. And then the one
00:24:55.798 --> 00:24:59.219 thing that's different, I guess the 2022.4. Well, so I forgot
00:24:59.219 --> 00:25:02.419 this technically with this doesn't matter as much because
00:25:02.419 --> 00:25:04.074 it's not using git outside of.
00:25:04.804 --> 00:25:05.564 The.
00:25:06.514 --> 00:25:09.484 Outside of, just like pulling in that the artifact and it uses
00:25:09.484 --> 00:25:12.360 that by default anyway, it uses the a lot talking by default
00:25:12.360 --> 00:25:15.377 anyway, but just in case there was some task group on here that
00:25:15.377 --> 00:25:17.074 needed to go pull some other value.
00:25:17.314 --> 00:25:21.556 Umm we I'll just go ahead and set that as a check mark. OK.
00:25:21.556 --> 00:25:25.798 Supply Seth. Artifact 2022.4. We're going to change this to
00:25:25.798 --> 00:25:26.364 clarity.
00:25:29.994 --> 00:25:31.964 Rock QA dot.
00:25:33.454 --> 00:25:34.544 Same thing here.
00:25:39.854 --> 00:25:44.444 And then the artifact is the CI rock QA SEF.
00:25:46.274 --> 00:25:48.584 See data projects rock.
00:25:52.664 --> 00:25:56.137 Don't need anything else there. Running agent is good. OK,
00:25:56.137 --> 00:25:57.314 variable is nothing.
00:25:59.594 --> 00:26:01.484 Options release.
00:26:03.374 --> 00:26:04.104 Rock.
00:26:05.254 --> 00:26:06.904 QA on.
00:26:08.234 --> 00:26:11.664 Seth, go one and then Seth.
00:26:12.704 --> 00:26:14.954 And history. OK, cool. So we'll go ahead and save this.
00:26:16.184 --> 00:26:19.045 And so again, this was gonna talk about earlier about doing
00:26:19.045 --> 00:26:21.524 different. This does allow me to actually pick the.
00:26:21.604 --> 00:26:21.814 The.
00:26:23.014 --> 00:26:24.464 Folder that I want to.
00:26:25.194 --> 00:26:28.891 Create this under. Just saves an extra step. OK, so now we've
00:26:28.891 --> 00:26:32.409 created the build pipeline which actually builds the code,
00:26:32.409 --> 00:26:35.807 outputs it to an artifact, and then we built the release
00:26:35.807 --> 00:26:36.344 pipeline.
00:26:37.814 --> 00:26:41.147 Any questions on the release pipeline and we'll get into the
00:26:41.147 --> 00:26:44.208 prod like the prod delete potentially get into the prod
00:26:44.208 --> 00:26:47.104 one later, but if there are any questions, go ahead.
00:26:47.914 --> 00:26:49.544 Or Brendan, if you got anything else to add.
00:26:52.414 --> 00:26:53.814 No, nothing to add, just.
00:26:57.024 --> 00:27:00.852 I think you're about to get into like backup configs and stuff,
00:27:00.852 --> 00:27:03.604 which is where we'll probably have some some.
00:27:04.354 --> 00:27:06.194 All hands information.
00:27:06.774 --> 00:27:09.853 Yeah, for sure. OK, cool. So, yeah, let's go ahead. And I'm
00:27:09.853 --> 00:27:11.854 going to go ahead and pull up Sev one.
00:27:18.014 --> 00:27:21.661 Cool. So the nice thing is, and this isn't perfect, and so I
00:27:21.661 --> 00:27:25.428 apologize in advance that I have admittedly not gone and fixed
00:27:25.428 --> 00:27:29.314 the problems that with this, but I understand them. So it's kind
00:27:29.314 --> 00:27:33.081 of one of those things that it's a typical clarity thing where
00:27:33.081 --> 00:27:36.848 one person understands what the issues are. And so if somebody
00:27:36.848 --> 00:27:40.495 else had to do it that be a problem. But I will take it upon
00:27:40.495 --> 00:27:43.724 myself to go fix those. So the nice thing is for CLT.
00:27:43.844 --> 00:27:46.703 Which is the auto updated tool that that all of you should have
00:27:46.703 --> 00:27:49.383 and we should actually may go into that later today to make
00:27:49.383 --> 00:27:51.304 sure everyone is up to date on the latest.
00:27:52.424 --> 00:27:55.980 There is also a deployed command line tool and some of you might
00:27:55.980 --> 00:27:58.004 still might actually still use that.
00:27:59.304 --> 00:28:04.201 But I added a CI CD setup command to that. So in CEF tool
00:28:04.201 --> 00:28:05.974 I can do CI CD setup.
00:28:07.974 --> 00:28:08.464 Uh.
00:28:09.174 --> 00:28:11.444 Is it not on this box? It might not be on this box.
00:28:16.614 --> 00:28:17.264 Let's CT.
00:28:21.714 --> 00:28:23.954 Well, I'll be. Why isn't it on this box?
00:28:27.104 --> 00:28:27.964 Which box is it?
00:28:28.664 --> 00:28:29.514 The stuff that one.
00:28:30.684 --> 00:28:31.294 It should be.
00:28:32.054 --> 00:28:32.844 Fired songs.
00:28:34.304 --> 00:28:37.594 It's checked out from source, though that needs to probably.
00:28:34.484 --> 00:28:35.394 This is the.
00:28:39.844 --> 00:28:44.383 Clarity deployment tool. No. Wow. OK, well, then we're gonna
00:28:42.014 --> 00:28:42.924 That's the old one.
00:28:44.383 --> 00:28:47.434 get a quick crash course on getting CLT.
00:28:49.214 --> 00:28:51.144 I put the link in the chat for you real quick.
00:28:51.514 --> 00:28:54.019 Yeah. So I'll, I'll show you how to find it. If you don't know
00:28:52.774 --> 00:28:53.574 So actually.
00:28:54.019 --> 00:28:56.406 that. If you go to a new cleaner and you type in deployment
00:28:56.406 --> 00:28:56.684 guides.
00:28:58.484 --> 00:29:00.714 If you go to this installer download link.
00:29:01.774 --> 00:29:03.714 CLT updates where you demos.com.
00:29:07.274 --> 00:29:08.034 A copy.
00:29:09.934 --> 00:29:11.824 And then so Chrome.
00:29:17.214 --> 00:29:17.694 Is it down?
00:29:21.344 --> 00:29:23.004 Trying HTTPS before it.
00:29:26.184 --> 00:29:29.967 And if the if this works, then we just need to put an HTTPS
00:29:29.967 --> 00:29:31.354 binding. OK, try HTTP.
00:29:36.224 --> 00:29:36.574 Ha.
00:29:38.204 --> 00:29:40.414 The old demo demon strikes again.
00:29:40.684 --> 00:29:45.387 Umm well, you are on the box that that CLT update site is on.
00:29:41.494 --> 00:29:41.884 Alright.
00:29:45.387 --> 00:29:48.194 So go check IIS on there real quick.
00:29:50.354 --> 00:29:53.764 But that being said, no domain is not.
00:29:55.174 --> 00:29:55.904 The.
00:29:57.104 --> 00:29:58.194 Man, it's all there.
00:29:58.424 --> 00:30:02.186 Well, yeah, I can. I can hit the site without slashes. He'll T
00:30:02.186 --> 00:30:02.664 dot zip.
00:30:05.214 --> 00:30:07.986 Well, yeah, you're getting a no domain though. That's the part
00:30:07.986 --> 00:30:10.714 that's weird. Like it's saying that DNS isn't resolving that.
00:30:14.104 --> 00:30:17.354 Yeah, that is weird because I I just loaded it and it's working
00:30:17.354 --> 00:30:17.964 fine for me.
00:30:19.284 --> 00:30:22.342 Is this one of those? Is weird internal DNS things like we had
00:30:22.342 --> 00:30:25.304 a while back and internal server hitting an internal server.
00:30:22.524 --> 00:30:23.354 Yeah, I don't know.
00:30:25.964 --> 00:30:29.812 I guess it's hitting itself. You just add that to the host file
00:30:29.812 --> 00:30:30.834 for this box but.
00:30:31.874 --> 00:30:34.197 Yes. Yeah. If that's the case, then auto updates aren't gonna
00:30:34.197 --> 00:30:34.984 work for that either.
00:30:44.364 --> 00:30:45.814 Uh, yeah, I don't know.
00:30:47.604 --> 00:30:48.774 That's bizarre.
00:30:50.974 --> 00:30:54.427 Uh, I guess the majority of cause CEF Dev one looked looked
00:30:54.427 --> 00:30:58.225 very full for a long time and so I've only been doing deployments
00:30:58.225 --> 00:31:01.908 on SEV two and Sev three, but we realized that Sev one was just
00:31:01.908 --> 00:31:05.304 filled with old projects that are needed to go archive, so
00:31:05.304 --> 00:31:08.354 that's why I was gonna put it on stuff that one but.
00:31:09.564 --> 00:31:10.084 What is it?
00:31:11.954 --> 00:31:13.244 Since the updates.
00:31:19.864 --> 00:31:20.144 Yep.
00:31:21.854 --> 00:31:23.094 See Lt. does it.
00:31:23.684 --> 00:31:23.934 Yep.
00:31:25.764 --> 00:31:27.464 There you go. Weird.
00:31:26.854 --> 00:31:28.144 Yeah, science rules.
00:31:30.004 --> 00:31:31.294 Uh, OK, show in folder.
00:31:38.754 --> 00:31:40.824 Be patient. It's got to come back from space.
00:31:49.224 --> 00:31:54.234 OK, OK, I will copy this to the tools folder.
00:31:57.664 --> 00:32:00.694 And then extract it to seal it.
00:32:03.244 --> 00:32:09.321 And then for the console app for the CEF tool.exe, I'm going to
00:32:09.321 --> 00:32:13.214 set an environment variable on the path.
00:32:17.044 --> 00:32:19.454 Some variables go to the path.
00:32:22.054 --> 00:32:22.944 Edits.
00:32:23.934 --> 00:32:26.224 I'll add a new one for C.
00:32:28.064 --> 00:32:32.444 Gracious data tools, CLT.
00:32:36.544 --> 00:32:38.174 But now I should be able to.
00:32:42.474 --> 00:32:43.574 So I need to restart this.
00:32:49.594 --> 00:32:50.364 Oh yes.
00:32:50.724 --> 00:32:56.231 Yeah, I did. OK, cool. So I just asked me for my acronym. So
00:32:56.231 --> 00:33:01.106 rock. And this is a QA environment. So what this does
00:33:01.106 --> 00:33:03.634 currently is it goes in and.
00:33:05.474 --> 00:33:07.084 Pulls the.
00:33:08.944 --> 00:33:12.532 Ooh, I wonder for a new if I knew for a new version, it might
00:33:12.532 --> 00:33:15.888 not. We'll see. OK. It will go in and it is currently get
00:33:15.888 --> 00:33:17.914 pulling the master branch for web.
00:33:19.254 --> 00:33:23.312 And we'll need to go modify that now. There is a bug, not a bug.
00:33:23.312 --> 00:33:27.246 There's just a a functionality flaw in this, which I guess you
00:33:27.246 --> 00:33:31.241 can consider a bug that it does create the web branch, but then
00:33:31.241 --> 00:33:35.112 later in the process when it creates the IIS site, it creates
00:33:35.112 --> 00:33:38.983 the virtual directories and it creates the SIM links to tries
00:33:38.983 --> 00:33:42.730 to create them to the Web 9 folder which doesn't exist. And
00:33:42.730 --> 00:33:46.663 so right now I have to run this twice. I just need to take the
00:33:46.663 --> 00:33:48.224 time to go in and fix it.
00:33:48.364 --> 00:33:51.310 So once this is done running and it sets all the sites up and
00:33:51.310 --> 00:33:54.398 everything, uh, I'll change this to Webb nine. Let it run again.
00:33:54.398 --> 00:33:56.868 It will create another web folder, but then it will
00:33:56.868 --> 00:33:59.861 probably properly rink to Web nine and I'll just go delete the
00:33:59.861 --> 00:34:00.384 web folder.
00:34:01.904 --> 00:34:04.874 Umm, but this uses the same installer.
00:34:05.634 --> 00:34:09.332 Umm. Methods that the regular installer does and so it's
00:34:09.332 --> 00:34:12.965 creating the IIS app it's creating IIS site will create
00:34:12.965 --> 00:34:16.144 all the app pools. The only thing it doesn't do.
00:34:16.544 --> 00:34:20.420 Umm, out of box is the API app pool in its current and its
00:34:20.420 --> 00:34:24.558 current state. So there are like I said there are some updates
00:34:24.558 --> 00:34:28.894 that need to happen but OK cool. So I'll go change this to Web 9.
00:34:31.864 --> 00:34:32.974 And run this again.
00:34:39.814 --> 00:34:41.654 The one additional thing that this does do.
00:34:43.154 --> 00:34:46.093 Uh, that the regular installer does not is that although it
00:34:46.093 --> 00:34:48.444 didn't do backup configs, which is interesting.
00:34:57.714 --> 00:34:59.774 Ohh, does the CEF configs not have?
00:35:10.844 --> 00:35:11.874 The not pull latest.
00:35:31.294 --> 00:35:34.664 Creates the backup configs from or is it created from?
00:35:38.644 --> 00:35:40.144 What if this just hasn't been pulled in wall?
00:35:45.894 --> 00:35:50.215 To the get config global ad and then do a star instead of the
00:35:50.215 --> 00:35:54.327 CSF config so nobody has to do that again. Instead of Csef
00:35:54.327 --> 00:35:57.394 configs do UM star between quotation marks.
00:36:00.304 --> 00:36:02.714 That should be just like it's all safe.
00:36:03.954 --> 00:36:04.744 We promise.
00:36:06.484 --> 00:36:07.784 OK, so just need the latest.
00:36:11.504 --> 00:36:13.114 So now I get to go run this again.
00:36:20.324 --> 00:36:21.734 Shouldn't need to pull web. There we go.
00:36:23.484 --> 00:36:27.214 So it just didn't pull the latest from Sept configs, but
00:36:27.214 --> 00:36:31.206 OK, uh, so backup configs so the backup configs for the Cicd
00:36:31.206 --> 00:36:33.954 pipelines allow us to do a couple things.
00:36:34.914 --> 00:36:38.264 So whenever we release a site, you know the.
00:36:39.794 --> 00:36:43.604 When it builds, we don't we don't store the the actual like
00:36:43.604 --> 00:36:47.224 app settings or connection strings. That would be on the
00:36:47.224 --> 00:36:51.288 actual like Q or stage site in anywhere that the build pipeline
00:36:51.288 --> 00:36:55.416 would have access to them. So it pulls kind of a generic version
00:36:55.416 --> 00:36:55.924 of them.
00:36:57.044 --> 00:36:59.771 To to you know, to have the right configs and all the things
00:36:59.771 --> 00:37:01.514 that it needs to actually build, Seth.
00:37:01.904 --> 00:37:06.444 Uh, what? The backup configs allow us to do is store those
00:37:06.444 --> 00:37:11.368 solution items, and in those six bin the connection strings and
00:37:11.368 --> 00:37:16.369 the mail settings, et cetera. So that when a deployment happens,
00:37:16.369 --> 00:37:19.524 what is actually going and happening is.
00:37:21.044 --> 00:37:24.383 It creates a a SEF zip. So basically it downloads that
00:37:24.383 --> 00:37:28.208 artifact and so that that'll be like artifact a ZIP or CEF dot
00:37:28.208 --> 00:37:32.094 zip. I don't remember what it is but then it goes and turns the
00:37:32.094 --> 00:37:32.944 app pools off.
00:37:34.404 --> 00:37:37.775 Renames this folder here to. Well, first of all, I guess what
00:37:37.775 --> 00:37:41.254 it does is it it goes and copies out all of the current config.
00:37:41.254 --> 00:37:44.462 So for example, if you've made changes to app settings dot
00:37:44.462 --> 00:37:47.398 client or app settings environment which you probably
00:37:47.398 --> 00:37:50.497 are mostly just doing app settings dot client. So if you
00:37:50.497 --> 00:37:53.814 go to the admin and go modify some settings to turn features
00:37:53.814 --> 00:37:55.934 or routes on that gets stored in here.
00:37:56.794 --> 00:37:59.944 And the first part of that release pipeline, what it'll do
00:37:59.944 --> 00:38:02.934 is it'll copy this this file out to the backup configs.
00:38:04.224 --> 00:38:07.448 Or and same thing with translations connection strings.
00:38:07.448 --> 00:38:10.557 Basically any anything that would be specific to that
00:38:10.557 --> 00:38:12.054 environment it copies out.
00:38:12.904 --> 00:38:17.800 Then it goes and makes that that zip folder. Then it names this
00:38:17.800 --> 00:38:22.619 as Seth dot old self dash old, then it renames the new version
00:38:22.619 --> 00:38:23.614 as just Seth.
00:38:24.294 --> 00:38:27.933 Then it turns the app pools back on after copying the backup
00:38:27.933 --> 00:38:31.214 configs back in. So basically it backs up the configs.
00:38:32.024 --> 00:38:35.781 Renames it, copies the configs into the new version, and then
00:38:35.781 --> 00:38:39.538 goes and deletes the old folder so that basically all the old
00:38:39.538 --> 00:38:42.931 configs have a place to be stored and then get restored
00:38:42.931 --> 00:38:43.234 back.
00:38:44.594 --> 00:38:47.304 Every single time that, that, that, that, that that runs so.
00:38:49.204 --> 00:38:52.072 And I kind of jumbled that explanation, so. So Brendan
00:38:52.072 --> 00:38:54.314 picked me up here if if I missed anything.
00:38:56.114 --> 00:38:59.804 Nope. Yeah, it's the basic processes. Copy out configs.
00:39:00.584 --> 00:39:05.599 Umm extract the the new updated build that was made by the
00:39:05.599 --> 00:39:06.364 pipeline.
00:39:08.404 --> 00:39:12.310 Turn off the app pools, rename the current one to old, rename
00:39:12.310 --> 00:39:16.217 the new one to the actual live name, which would just be CEF.
00:39:16.217 --> 00:39:19.934 Turn the app pools back on and then delete the old folder.
00:39:20.414 --> 00:39:20.644 Yep.
00:39:20.734 --> 00:39:24.614 Umm and I don't know if you already covered this part, but.
00:39:24.204 --> 00:39:25.934 Ohh here it's happening right now.
00:39:26.004 --> 00:39:28.434 Hey, look, here it goes. Yeah, so that front that.
00:39:27.134 --> 00:39:29.714 So created this self .7 zip.
00:39:30.034 --> 00:39:32.464 Yeah. And then the from zip is the new folder.
00:39:34.184 --> 00:39:36.825 Be careful clicking around in there because it might blow it
00:39:36.825 --> 00:39:39.207 up, which is perfect. Exactly. I'm going to talk about
00:39:39.207 --> 00:39:41.762 something that everybody needs to know, and I've done this
00:39:41.762 --> 00:39:44.273 before and it worked. So I'm gonna do it again. Everybody
00:39:44.273 --> 00:39:46.914 that's listening. Please raise your hand on teams. So I know
00:39:46.914 --> 00:39:47.434 that you're.
00:39:48.264 --> 00:39:51.324 Your present and and going to hear this.
00:40:00.874 --> 00:40:04.826 See what we missing? OK, thank. That's pretty much everyone. OK,
00:40:04.826 --> 00:40:07.805 so I have thank you for everybody for listening.
00:40:07.805 --> 00:40:11.696 Extremely important when you are doing anything on one of these
00:40:11.696 --> 00:40:15.647 pipeline projects like changing app settings or fixing something
00:40:15.647 --> 00:40:19.295 or adding images when you're done, close every open folder,
00:40:19.295 --> 00:40:23.247 every open command line that you have do not leave anything open
00:40:23.247 --> 00:40:26.956 when you disconnect from the box. It does not close them for
00:40:26.956 --> 00:40:30.786 you. And when the pipeline tries to run, if you have a command
00:40:30.786 --> 00:40:33.704 line or something open in one of those folders.
00:40:34.074 --> 00:40:37.763 The pipeline deployment will fail. The site will either not
00:40:37.763 --> 00:40:41.575 work or it won't be updated. It'll still be the old stuff, so
00:40:41.575 --> 00:40:45.510 you have to keep that in mind if you're doing anything on these
00:40:45.510 --> 00:40:49.261 boxes, don't leave stuff open when you're done. close all of
00:40:49.261 --> 00:40:52.642 it, and on the flip side of that, if you have a PR, go
00:40:52.642 --> 00:40:56.516 through and it looks like your site didn't update on the other
00:40:56.516 --> 00:41:00.512 side you're tested on QA and it looks like you're changes aren't
00:41:00.512 --> 00:41:04.140 there. Looking at the release you can see if it failed and
00:41:04.140 --> 00:41:07.214 it'll tell you something along the lines of like.
00:41:08.804 --> 00:41:12.700 A permission error when it tried to rename a folder or something
00:41:12.700 --> 00:41:16.416 like that. That tells you that somebody probably has a folder
00:41:16.416 --> 00:41:18.634 or a command line or something open.
00:41:17.484 --> 00:41:21.183 Here I got one right here we felt random. This through Tasco
00:41:21.183 --> 00:41:24.821 the other day. So here I'm clean web. It'll it'll typically
00:41:24.821 --> 00:41:28.641 happen right here. Clean website and service files. So when it
00:41:28.641 --> 00:41:31.976 goes to delete the client plugins or the any basically
00:41:31.976 --> 00:41:35.492 that entire folder it can't do it because somebody hasn't
00:41:35.492 --> 00:41:39.191 opened. So you'll typically see this operation not permitted
00:41:35.664 --> 00:41:35.984 Yeah.
00:41:39.191 --> 00:41:43.072 whenever you see the operation not permitted most of the time I
00:41:43.072 --> 00:41:46.649 would say 95% of the time somebody is logged into that box
00:41:46.649 --> 00:41:48.044 and it may even be you.
00:41:48.644 --> 00:41:49.594 Yeah, yeah.
00:41:48.644 --> 00:41:52.164 Just so you know that that has definitely might be you and in
00:41:50.724 --> 00:41:52.644 She definitely might be you.
00:41:52.164 --> 00:41:55.684 it you know the the best thing to do is especially for like a
00:41:55.684 --> 00:41:59.317 prod box 1, make sure everyone's actually done. But just go log
00:41:59.317 --> 00:42:02.894 people off. That's what we had to do for Tasco. Like if you're
00:42:02.264 --> 00:42:02.584 Yeah.
00:42:02.894 --> 00:42:06.017 you know, you're the person doing the deployment, just
00:42:06.017 --> 00:42:09.593 definitely send a ping. But like if you need to get deployment
00:42:09.593 --> 00:42:11.694 done right now, just log people out.
00:42:12.834 --> 00:42:13.924 Including yourself?
00:42:12.884 --> 00:42:17.574 Now, better yet, instead of just closing the window, don't don't
00:42:13.684 --> 00:42:14.254 Uh.
00:42:17.574 --> 00:42:21.904 close and disconnect. Actually go to the Pearl and log off.
00:42:22.534 --> 00:42:23.324 Sign out, yeah.
00:42:22.994 --> 00:42:25.234 That works too. Yeah, because it'll kill all your. Yeah.
00:42:23.084 --> 00:42:27.102 So that so that you actually close everything else and you're
00:42:26.264 --> 00:42:26.664 Hmm.
00:42:26.324 --> 00:42:27.524 Yep, yeah.
00:42:27.102 --> 00:42:28.334 not left signed in.
00:42:28.784 --> 00:42:29.374 Yeah.
00:42:28.974 --> 00:42:32.293 Good call, especially for prod boxes. People should prefer that
00:42:32.293 --> 00:42:34.989 way rather than just disconnecting from the session
00:42:34.989 --> 00:42:38.204 by like closing the window or something because that does not
00:42:38.204 --> 00:42:41.368 like. Like Michael said, that doesn't actually sign you out,
00:42:41.368 --> 00:42:44.531 it keeps your session open if you wanna end the session then
00:42:42.134 --> 00:42:42.504 Mm-hmm.
00:42:44.531 --> 00:42:47.124 you should use the start button and then log out.
00:42:48.624 --> 00:42:53.143 And that will actually end the RDP session and that guarantees
00:42:53.143 --> 00:42:56.514 that in fact you will not have any files open.
00:42:57.464 --> 00:43:02.103 Yeah. OK. So we are not quite done yet here because we don't
00:43:02.103 --> 00:43:03.244 have databases.
00:43:03.714 --> 00:43:07.274 Uh, so I typically do this all my local instead.
00:43:07.394 --> 00:43:12.785 Uh, and I will go to restore database. So for every release
00:43:12.785 --> 00:43:18.357 version that we do, I create a identity database that is just
00:43:18.357 --> 00:43:23.838 the identity and default C test ran, not the sample data, so
00:43:23.838 --> 00:43:29.319 there's no invoice or product data or any of that. It's just
00:43:29.319 --> 00:43:32.644 the clarity, accounts and users and.
00:43:32.724 --> 00:43:37.166 Umm, the, you know all of the types and statuses and all of
00:43:37.166 --> 00:43:41.607 the things that CEF needs to run, but is no sample data and
00:43:41.607 --> 00:43:43.014 so I store that in.
00:43:44.454 --> 00:43:48.264 Uh, default identity theft 2022.4 so OK.
00:43:50.314 --> 00:43:54.764 And then we'll rename this to Rock Seqa.
00:43:56.614 --> 00:43:59.134 All looks good. It didn't like it.
00:44:09.964 --> 00:44:10.164 But.
00:44:15.394 --> 00:44:15.864 Alright.
00:44:20.004 --> 00:44:22.254 That's the first time I've ever heard that's ever seen that one.
00:44:25.504 --> 00:44:28.694 Database Rock SEQ does not exist. Restore can only.
00:44:30.844 --> 00:44:32.614 Is this a partial backup?
00:44:33.384 --> 00:44:33.824 No.
00:44:38.584 --> 00:44:40.654 Well, let's try that again.
00:44:38.754 --> 00:44:41.454 Let's go to the process, turn it off and turn it back on.
00:44:41.864 --> 00:44:42.514 Yeah.
00:44:43.824 --> 00:44:44.894 Now 118.
00:44:46.184 --> 00:44:48.514 There, there is no exact science.
00:44:47.284 --> 00:44:51.216 Because I did this for cause I did. I mean I used this exact
00:44:51.216 --> 00:44:52.054 same one for.
00:44:51.654 --> 00:44:56.394 Ohh go to the files tab after you set your database tab here.
00:44:59.994 --> 00:45:00.484 OK.
00:45:01.944 --> 00:45:04.659 Widen this out and then that restore as column. OK, it
00:45:04.659 --> 00:45:07.572 doesn't names OK, sometimes it doesn't. For some reason it
00:45:07.572 --> 00:45:10.732 doesn't update those names and it will try to restore under the
00:45:10.732 --> 00:45:12.114 same name as something else.
00:45:14.004 --> 00:45:17.104 Restore can only create database when restoring either a full
00:45:14.244 --> 00:45:15.004 Uh, let me see.
00:45:17.104 --> 00:45:20.154 backup or file backup of the primary file. It's really not a
00:45:20.154 --> 00:45:21.004 full backup, huh?
00:45:21.434 --> 00:45:23.804 That's that's what it seems to think.
00:45:24.284 --> 00:45:25.454 Oh wait, hang on.
00:45:27.014 --> 00:45:27.404 Ohh.
00:45:30.094 --> 00:45:31.364 I've seen this happen a couple of times.
00:45:37.724 --> 00:45:38.254 That's fine.
00:45:41.094 --> 00:45:41.584 Try again.
00:45:42.964 --> 00:45:45.694 But we're just running into all the all the demo problems.
00:45:48.274 --> 00:45:50.944 That's good. People can see some fixes.
00:45:49.674 --> 00:45:50.294 Yeah, it is.
00:45:59.684 --> 00:46:03.483 I don't know what that tail tail log backup actually does, but
00:46:03.483 --> 00:46:03.724 man.
00:46:04.764 --> 00:46:05.234 Oh.
00:46:12.994 --> 00:46:15.004 I yeah, I'm. I'm a.
00:46:16.524 --> 00:46:20.674 I just did this for GFS for using this exact same one.
00:46:27.704 --> 00:46:28.444 Let's see.
00:46:30.224 --> 00:46:31.204 And it's there.
00:46:31.164 --> 00:46:33.214 You take a fresh backup of 1 then.
00:47:20.904 --> 00:47:21.864 Umm.
00:47:24.184 --> 00:47:26.164 I, but that's what I did. It needs to be this one.
00:47:29.564 --> 00:47:31.304 So we'll take this one, but.
00:47:33.064 --> 00:47:34.024 But that's the problem.
00:47:40.514 --> 00:47:42.664 There we go. OK, let's go. Just check it real quick.
00:47:56.924 --> 00:48:01.312 Perfect. OK, so now we have our clarity, clarity, user and all
00:48:01.312 --> 00:48:05.422 the accounts in there. So we should be good to go. OK. And
00:48:05.422 --> 00:48:06.954 then the other one is.
00:48:14.484 --> 00:48:18.989 Uh demo 20. We now we haven't created a 2022-4 yet, so it's
00:48:18.989 --> 00:48:22.894 just 2022.2, but they're all the same on master so.
00:48:24.914 --> 00:48:26.104 It's going to restore this one.
00:48:28.364 --> 00:48:30.194 And we'll start it to rock.
00:48:30.264 --> 00:48:30.664 OK.
00:48:31.844 --> 00:48:34.044 DNN 9 QA.
00:48:41.684 --> 00:48:42.544 That the same error.
00:48:44.124 --> 00:48:44.294 Yeah.
00:48:47.324 --> 00:48:48.524 And the work that time was weird.
00:48:49.194 --> 00:48:51.354 Uh, OK, so.
00:48:52.634 --> 00:48:56.996 Now we have the two databases and when we created the the the
00:48:56.996 --> 00:49:01.429 the backup configs based on our rock and QA environments it it
00:49:01.429 --> 00:49:05.580 created the correct connection strings to these two files.
00:49:05.580 --> 00:49:09.943 However, we're not done yet. We have two things left to do in
00:49:09.943 --> 00:49:12.124 here. Actually I think maybe 3.
00:49:13.964 --> 00:49:17.014 The first one thanks to Old Sebastian.
00:49:18.274 --> 00:49:20.164 Is we need to go to our portal alias table.
00:49:25.324 --> 00:49:28.984 And then I always add both the QA.
00:49:33.034 --> 00:49:34.584 And the.
00:49:36.924 --> 00:49:39.054 Stage URLs.
00:49:40.174 --> 00:49:43.399 So these just so that when I take this backup, move it
00:49:43.399 --> 00:49:44.924 forward, we're good to go.
00:49:46.324 --> 00:49:50.314 Uh. And then I think that I have a file saved. Let me let me see
00:49:50.314 --> 00:49:51.664 if I actually have it.
00:49:56.344 --> 00:50:01.004 Projects. New clients. Yep. Here we go. So I have a.
00:50:01.904 --> 00:50:06.097 A SQL script here in the in the DNN folders and tabs and portal
00:50:06.097 --> 00:50:09.963 settings et cetera. It has the old clarity react, so we're
00:50:09.963 --> 00:50:13.304 going to place clarity react everywhere with rock.
00:50:15.664 --> 00:50:17.864 So that should be good and then?
00:50:17.094 --> 00:50:17.764 Nice.
00:50:18.744 --> 00:50:22.753 Yeah. So and that is you can find that if you go to and I
00:50:22.753 --> 00:50:25.794 think I need to move it to a new clean, no.
00:50:27.084 --> 00:50:29.154 But if you go to.
00:50:30.904 --> 00:50:32.674 The Stack overflow for clarity.
00:50:33.524 --> 00:50:37.573 I'm here if you just type in DNN scan. What do I need to update?
00:50:37.573 --> 00:50:38.944 DNN scan will be that.
00:50:41.004 --> 00:50:41.734 That script.
00:50:42.594 --> 00:50:43.504 Heck yeah.
00:50:42.814 --> 00:50:44.214 I just have mine saved locally.
00:50:44.834 --> 00:50:45.244 Yeah.
00:50:46.924 --> 00:50:50.704 Cool. Let's see. And then go ahead.
00:50:49.304 --> 00:50:50.214 Probably.
00:50:51.494 --> 00:50:55.156 I was just saying we that we have to make the network
00:50:55.156 --> 00:50:58.344 authority ADB owner do we know how to do that?
00:51:00.294 --> 00:51:04.098 Int Service network authority Adam is a DD owner is that don't
00:51:04.098 --> 00:51:05.064 have to be done.
00:51:05.914 --> 00:51:08.434 Not on QA boxes, only on locals.
00:51:06.024 --> 00:51:06.614 Oh.
00:51:09.024 --> 00:51:10.434 OK, OK.
00:51:09.184 --> 00:51:09.344 Yep.
00:51:10.324 --> 00:51:14.414 Yeah, network service network service isn't needed on the
00:51:10.384 --> 00:51:11.324 Uh, and that's.
00:51:14.414 --> 00:51:18.574 database level for QA sites because that user is unique to
00:51:18.574 --> 00:51:22.876 each individual box that it's on. It's an OS user and we add
00:51:22.876 --> 00:51:27.107 it on our locals because it makes using integrated security
00:51:27.107 --> 00:51:31.056 possible because we're authenticating with the database
00:51:31.056 --> 00:51:35.287 as network service. In the case of QA sites or any database
00:51:35.287 --> 00:51:38.884 that's on like 2019 SQL or 20, whatever SQL you're
00:51:38.884 --> 00:51:40.294 authenticating with.
00:51:40.394 --> 00:51:45.149 An actual SQL user SQL login not as an OS person or as the user
00:51:45.149 --> 00:51:49.904 that the app pool is running as, so you don't need to add that.
00:51:50.984 --> 00:51:52.294 Gotcha. Yeah, that makes sense.
00:51:53.544 --> 00:51:53.974 Cool.
00:51:54.954 --> 00:51:55.454 OK.
00:51:55.534 --> 00:51:59.456 So I'm trying to think, well, we probably should go add the
00:51:59.456 --> 00:52:02.594 GoDaddy entry, so let me go do that real quick.
00:52:06.714 --> 00:52:11.776 And I have it just stored as a, so we'll come in here and add it
00:52:11.776 --> 00:52:14.424 is a type of a. The name is rock.
00:52:15.684 --> 00:52:20.320 QA and then I always have to just kind of look to see it's
00:52:20.320 --> 00:52:20.634 206.
00:52:21.604 --> 00:52:26.184 Dial 127.30 dot 131 for Sev one.
00:52:27.404 --> 00:52:28.514 Slide that record.
00:52:32.974 --> 00:52:37.054 And then before I go check it, I always do dnschecker.org.
00:52:44.944 --> 00:52:48.405 And some things are picked it up. So if you're the reason why
00:52:48.405 --> 00:52:51.811 you're seeing a second one that looks like our IP is because
00:52:51.811 --> 00:52:53.374 this is what that redirects.
00:52:55.134 --> 00:52:58.352 That your sub domain does not exist lives on, so when it tries
00:52:58.352 --> 00:53:01.570 to direct to that it can't find it and so it redirects to this
00:53:01.570 --> 00:53:04.584 which is why you wanna wait for it to say pretty much 131.
00:53:05.924 --> 00:53:09.891 Everywhere. But you only get so often to click the search button
00:53:09.891 --> 00:53:10.074 so.
00:53:11.644 --> 00:53:14.674 I could I could view it from that from that box, but.
00:53:16.974 --> 00:53:19.104 I want to see what what it looks like everywhere here.
00:53:27.054 --> 00:53:29.613 We'd probably be OK give it might give it another second or
00:53:29.613 --> 00:53:29.784 two.
00:53:37.294 --> 00:53:40.848 Miami and Canoga Park taking forever here. We'll give it a
00:53:40.848 --> 00:53:43.379 shot. Let's give it a shot anyway, right,
00:53:43.379 --> 00:53:44.644 qa.clarityclient.com.
00:53:47.704 --> 00:53:49.674 No rewrite module there.
00:53:52.074 --> 00:53:53.534 That doesn't make sense.
00:53:56.664 --> 00:53:58.244 Ooh.
00:54:00.224 --> 00:54:02.034 I yes, it definitely have that.
00:54:04.464 --> 00:54:07.944 Yeah, you're right. OK. So then we'll go check the folder.
00:54:16.304 --> 00:54:17.124 You know what?
00:54:18.194 --> 00:54:22.344 Because the backup configs weren't there when, UM, you know
00:54:22.344 --> 00:54:26.355 how I had to go update CEF configs. Well, when I made the
00:54:26.355 --> 00:54:30.159 switch from web to web 9 appropriately here, it didn't
00:54:30.159 --> 00:54:34.378 copy the backup config. So I bet rewrite rules. Yep, look at
00:54:34.378 --> 00:54:34.724 that.
00:54:41.054 --> 00:54:41.684 Which try that again.
00:54:48.224 --> 00:54:49.524 Now, gosh.
00:54:50.664 --> 00:54:52.464 Daniel, restart and restart the app pool is probably.
00:54:54.124 --> 00:54:55.884 Probably didn't pick up on that manually.
00:54:54.494 --> 00:54:55.464 Yeah, yeah.
00:54:56.314 --> 00:54:57.894 Gotta kill DNN at least.
00:55:01.314 --> 00:55:03.284 Rock QA.
00:55:04.644 --> 00:55:07.641 In fact, you should only have to stop and start DNN since the CEF
00:55:07.641 --> 00:55:09.094 stuff didn't even start to load.
00:55:07.704 --> 00:55:07.954 Yep.
00:55:09.424 --> 00:55:09.624 Yep.
00:55:17.294 --> 00:55:20.384 And is it not have the latest? It doesn't have the latest. OK
00:55:20.304 --> 00:55:21.494 Troubled old cert, yeah.
00:55:20.384 --> 00:55:23.624 well, ohhh you have a ticket for that in this Sprint, don't you?
00:55:24.624 --> 00:55:25.534 Most likely.
00:55:25.904 --> 00:55:27.684 You do? Yeah. OK, that's fine.
00:55:28.554 --> 00:55:29.544 Well, that is manually then.
00:55:31.724 --> 00:55:35.750 So if your locals are having the same issue, Brendan has a ticket
00:55:35.750 --> 00:55:39.348 in the Sprint to go update the installer to use the latest
00:55:39.348 --> 00:55:42.764 instead of the old version of the Clarity client Certs.
00:56:22.924 --> 00:56:24.174 Put them in the search folder.
00:56:52.404 --> 00:56:55.272 If you run into an issue where it tells you the password is
00:56:55.272 --> 00:56:57.614 wrong, the cert might already be installed just.
00:56:58.524 --> 00:57:00.734 FYI that that happened to me so.
00:57:01.614 --> 00:57:04.972 Yeah, did. Although I think that I've installed it twice on my
00:57:04.972 --> 00:57:07.796 local and didn't get that password error, so I'm not
00:57:07.796 --> 00:57:11.101 exactly sure what the problem was with yours went on. I think
00:57:08.804 --> 00:57:10.264 Man something.
00:57:11.101 --> 00:57:14.565 it might be. I think it might be because it was DFO, but I'm not
00:57:13.764 --> 00:57:15.154 Hmm, OK.
00:57:14.565 --> 00:57:16.804 100%. But anyway, all right, update this.
00:57:16.194 --> 00:57:19.074 FFO more like DFO old.
00:57:20.464 --> 00:57:22.164 Back in my day.
00:57:23.944 --> 00:57:25.994 Alright, try this one more again here.
00:57:27.614 --> 00:57:29.424 OK, sure.
00:57:33.404 --> 00:57:34.414 That's gotta be a.
00:57:57.754 --> 00:58:00.324 Ohh, the web connection strings. The thing it's OK hang on.
00:58:02.834 --> 00:58:05.646 The same issue that we just had, except all the copied over was
00:58:05.646 --> 00:58:05.954 the uh.
00:58:14.184 --> 00:58:15.054 Was the.
00:58:17.924 --> 00:58:19.794 Is it supposed to be web not Webb 9?
00:58:27.734 --> 00:58:31.384 May just have to check what it's set up in the thingy.
00:58:32.064 --> 00:58:32.674 Yeah.
00:58:32.874 --> 00:58:36.234 I think we typically use Web 9 for locals.
00:58:41.834 --> 00:58:44.368 Yeah, I mean it uses Web 9 for the connection or for the
00:58:44.368 --> 00:58:45.524 connection string as well.
00:58:47.294 --> 00:58:48.964 On QA and stage two so.
00:58:53.344 --> 00:58:53.944 Thinking now.
00:59:00.694 --> 00:59:01.834 Hey.
00:59:07.524 --> 00:59:08.954 Well, it looks like a CEF site.
00:59:09.144 --> 00:59:10.724 Alas, it is loading.
00:59:35.344 --> 00:59:39.018 And we have sign in. Cool. We'll wait for these calls to come
00:59:39.018 --> 00:59:39.314 back.
00:59:40.654 --> 00:59:45.070 Now the one thing I typically do for phase one, one things that
00:59:45.070 --> 00:59:49.141 we capture are try to do some system settings or some like
00:59:49.141 --> 00:59:53.349 site settings as well as set up the account and user which I
00:59:53.349 --> 00:59:57.558 will do. I think we wanted to quickly make sure everyone has
00:59:57.558 --> 01:00:02.043 CLT and then if we had any more questions on this. But I do have
01:00:02.043 --> 01:00:02.664 one more.
01:00:03.364 --> 01:00:09.649 Quick thing for that, for the initial account setup I did
01:00:09.649 --> 01:00:11.274 write a script.
01:00:11.944 --> 01:00:15.697 That creates an account admin just on a couple things, because
01:00:15.697 --> 01:00:19.569 creating an account in the admin and manually typing in all this
01:00:19.569 --> 01:00:21.654 address data was kind of annoying.
01:00:22.774 --> 01:00:26.482 I admit that I wrote a a script to insert this account and then
01:00:26.482 --> 01:00:28.684 you go create the users manually but.
01:00:29.304 --> 01:00:33.174 Umm, let me go find rocking hams.
01:00:35.284 --> 01:00:38.814 On boarding and I can show you that as well.
01:00:43.084 --> 01:00:44.464 When and where?
01:00:48.564 --> 01:00:51.966 So the sales team is working on an onboarding and this is the
01:00:51.966 --> 01:00:55.532 first implementation. Rockingham did the first implementation of
01:00:55.532 --> 01:00:58.934 the onboarding information. And so there's information about.
01:00:59.454 --> 01:01:02.969 You know what out of box features they want turned on and
01:01:02.969 --> 01:01:06.544 off, you know any additional information. This information
01:01:06.544 --> 01:01:10.483 gets passed to the PM as well as the BA for kind of starting the
01:01:10.483 --> 01:01:13.815 discovery process. This information always will always
01:01:13.815 --> 01:01:17.512 exist on projects. So you can always kind of go back and see
01:01:17.512 --> 01:01:21.451 what some of the original things were in here. But I am going to
01:01:21.451 --> 01:01:25.390 come in and see and this is the first time I've really looked at
01:01:25.390 --> 01:01:29.147 this version of this, I've used a Microsoft forms in the past
01:01:29.147 --> 01:01:30.904 that has made it really easy.
01:01:31.954 --> 01:01:34.254 That's basecamp. I don't want that one.
01:01:37.324 --> 01:01:39.144 Let's just see if I can French like street one.
01:01:42.954 --> 01:01:43.754 Address.
01:01:52.894 --> 01:01:53.924 Names and e-mail address.
01:01:54.004 --> 01:01:58.034 The is OK, so there's the admin users. Do we have?
01:02:01.404 --> 01:02:03.644 Looks like I need to go after.
01:02:05.834 --> 01:02:10.461 Kyle to update this so I have the addresses but I think I can
01:02:10.461 --> 01:02:11.954 get them from teams.
01:02:16.424 --> 01:02:17.004 Yeah, there we go.
01:02:18.334 --> 01:02:20.264 Billing address. So this is.
01:02:21.884 --> 01:02:24.704 Rockingham coop.
01:02:26.504 --> 01:02:28.034 I'll be called like that.
01:02:29.174 --> 01:02:29.944 Brock.
01:02:32.044 --> 01:02:35.624 Main e-mail is Gendreau at.
01:02:35.704 --> 01:02:35.954 Yes.
01:02:38.454 --> 01:02:40.734 M.com.
01:03:04.484 --> 01:03:06.274 I don't know if they have a phone number on here.
01:03:09.414 --> 01:03:09.824 There we go.
01:03:20.934 --> 01:03:23.644 Alright, so now if we go back to their site.
01:03:25.614 --> 01:03:27.924 Duplicate go to admin.
01:03:49.744 --> 01:03:53.215 So the majority of what we kind of wanted to cover mostly was
01:03:53.215 --> 01:03:56.407 the the pipelines and the releases discussion. Obviously
01:03:56.407 --> 01:03:59.934 this is kind of going through the release. You know my release
01:03:59.934 --> 01:04:03.406 process, obviously we ran into a couple of hiccups today, but
01:04:03.406 --> 01:04:07.101 typically without I can stand up the pipeline and the release and
01:04:07.101 --> 01:04:10.629 then have the server stood up and ready to go by the time they
01:04:10.629 --> 01:04:14.044 release comes in. And so it's kind of ready to go had like I
01:04:14.044 --> 01:04:17.684 said, we were talking about the pipelines and the releases, but.
01:04:19.224 --> 01:04:22.604 And then with a couple hiccups, took a little bit longer, but.
01:04:24.444 --> 01:04:28.176 With some more automation, we can definitely get this process
01:04:28.176 --> 01:04:31.968 down to really just create the PR and whatnot time. And like I
01:04:31.968 --> 01:04:35.639 said, I still do have to go back and create the branches and
01:04:35.639 --> 01:04:39.131 whatnot. So any questions on this process or pipelines in
01:04:39.131 --> 01:04:43.043 general, anythings you anything you should be looking out for if
01:04:43.043 --> 01:04:46.534 anybody has any experiences of you know we've mentioned a
01:04:46.534 --> 01:04:50.326 couple like Tim said, you know and Brandon said if the release
01:04:50.326 --> 01:04:52.794 isn't pushing, why isn't it pushing and?
01:04:52.844 --> 01:04:55.787 So now it's completely broken. What's going on? You check the
01:04:55.787 --> 01:04:57.922 release and it has the permissions. You know
01:04:57.922 --> 01:05:00.675 permissions error. Somebody logged into the site, but any
01:05:00.675 --> 01:05:02.574 other issues that people have run into?
01:05:04.254 --> 01:05:07.331 That would be good to know about. Would be great to discuss
01:05:07.331 --> 01:05:10.254 now while I'm going and having these these users to this
01:05:10.254 --> 01:05:10.664 account.
01:05:15.624 --> 01:05:19.724 Something I want to cover now while I'm thinking about it.
01:05:17.314 --> 01:05:17.614 Mm-hmm.
01:05:19.334 --> 01:05:19.604 Sure.
01:05:19.724 --> 01:05:21.114 This comes up a lot.
01:05:22.594 --> 01:05:26.809 People ask the question how do I debug on a QA site if there's an
01:05:26.809 --> 01:05:30.577 issue on QA and it's not on my local, how am I supposed to
01:05:30.577 --> 01:05:34.600 debug it? Well, the answer is you should be able to point your
01:05:34.600 --> 01:05:38.496 local at the QA database, which we can cover. How to do that
01:05:38.496 --> 01:05:41.114 really quick if you guys don't know how.
01:05:41.794 --> 01:05:44.567 You can stare and compare your app settings and make them
01:05:44.567 --> 01:05:47.243 identical to QA. Besides, obviously changing like local
01:05:47.243 --> 01:05:50.064 and the URL to QA and changing your folder path and stuff.
01:05:51.424 --> 01:05:54.954 And you can ensure that you've got the latest QA pulled with no
01:05:54.954 --> 01:05:58.318 local changes and you've got everything freshly built, front
01:05:58.318 --> 01:06:01.517 end and back end. And that scenario, your data is exactly
01:06:01.517 --> 01:06:02.014 the same.
01:06:02.984 --> 01:06:06.145 Your settings are exactly the same and your code is exactly
01:06:06.145 --> 01:06:09.360 the same. At that point. The only problem left if you if the
01:06:09.360 --> 01:06:12.258 bug is not reproducible between those two, would be an
01:06:12.258 --> 01:06:15.366 environment problem on the QA box, in which case your site
01:06:15.366 --> 01:06:18.581 wouldn't even really be the thing to debug. We would need to
01:06:18.581 --> 01:06:21.584 be looking at a why that is being a problem on that box.
01:06:22.244 --> 01:06:24.494 UM outside of that.
01:06:25.254 --> 01:06:29.486 You would at that .99% of the time you're gonna end up being
01:06:29.486 --> 01:06:33.788 it, figuring out how to repro your problem and fix it on your
01:06:33.788 --> 01:06:34.204 local.
01:06:35.944 --> 01:06:38.816 That's why it's really important that everybody keeps their app
01:06:38.816 --> 01:06:41.732 settings up to date with what's on QA, and we're working on some
01:06:41.732 --> 01:06:44.604 things internally to make that easier for future projects. But.
01:06:46.064 --> 01:06:50.190 99% of the time, if there's a bug on QA that's not on your
01:06:50.190 --> 01:06:54.246 local, it's missing data, missing or bad data, or missing
01:06:54.246 --> 01:06:56.694 or bad settings. One or the other.
01:06:58.744 --> 01:07:02.128 So that's, that's the answer to that is, if you're, if you've
01:07:02.128 --> 01:07:05.513 got a bug you're seeing on QA, you're having trouble reproing
01:07:05.513 --> 01:07:06.714 it on your local just.
01:07:07.754 --> 01:07:11.137 Point your local at the QA database, make your app Settings
01:07:11.137 --> 01:07:14.859 match QA as exactly as possible, and make sure you don't have any
01:07:14.859 --> 01:07:18.356 local changes in fresh. Build everything, and if you're still
01:07:18.356 --> 01:07:21.796 having problems at that point, then probably just get office
01:07:21.796 --> 01:07:22.134 hours.
01:07:22.814 --> 01:07:24.154 And we'll figure it out.
01:07:31.354 --> 01:07:31.854 Sweet.
01:07:35.064 --> 01:07:38.760 Well, if no one has any further questions and everyone is fully
01:07:37.574 --> 01:07:38.634 I have a questionnaire.
01:07:38.594 --> 01:07:39.814 Alex Alex had his end up.
01:07:38.760 --> 01:07:42.168 understanding, yeah, I I'm sorry. I I was not on the teams
01:07:42.168 --> 01:07:43.034 page. Go ahead.
01:07:43.574 --> 01:07:47.498 Now you're good. So is there, like a best practice for
01:07:47.498 --> 01:07:51.707 ensuring that no one is running or going to run a pipeline
01:07:51.707 --> 01:07:54.204 before logging on to a remote box?
01:07:55.994 --> 01:07:58.674 Generally speaking, so if you're, if you're talking about
01:07:56.064 --> 01:07:57.694 What do you mean before?
01:07:58.674 --> 01:08:01.630 like, what if I need to go and edit settings or do something on
01:08:01.630 --> 01:08:04.264 the box, how do I know that a pipeline is not gonna run?
01:08:04.744 --> 01:08:06.384 Yes. Yeah, exactly.
01:08:05.754 --> 01:08:08.400 Yep, uh, the the problem for it? Well, the thing with you and
01:08:08.400 --> 01:08:09.424 said sites is you don't.
01:08:10.054 --> 01:08:12.804 They'll run when a PR goes through automatically.
01:08:11.734 --> 01:08:14.493 But you could do. You could check if a PR is currently
01:08:14.493 --> 01:08:14.844 active.
01:08:16.164 --> 01:08:19.711 Or a pipeline is currently like a PR has active or completed and
01:08:19.711 --> 01:08:22.767 then checked the pipeline. Like typically if a pipeline
01:08:22.767 --> 01:08:26.096 especially for a Seth Seth, which obviously everyone's using
01:08:26.096 --> 01:08:29.533 CEF, so that's fine. But like if I go to Seth, so if you go to
01:08:29.533 --> 01:08:33.080 pipelines and then you click on pipelines, this will show all of
01:08:33.080 --> 01:08:36.518 the recently run pipelines. So for example, let's say you were
01:08:36.518 --> 01:08:39.847 gonna go look at Tasco stage stuff. This has already run. So
01:08:39.847 --> 01:08:43.012 you're good to go. But if there's OK. So right here, this
01:08:43.012 --> 01:08:45.304 pull request samples, let's say this was.
01:08:45.644 --> 01:08:48.997 Uh anaerobes QA Jeff. So let's say it was this one. Now running
01:08:48.997 --> 01:08:52.036 up here because this is running you probably shouldn't do
01:08:52.036 --> 01:08:55.023 anything until this is finished and the release has gone
01:08:55.023 --> 01:08:58.114 through. But if nothing is running, then you just go check
01:08:58.114 --> 01:09:00.944 the releases and then go specifically to your client.
01:09:01.614 --> 01:09:02.204 UM.
01:09:03.594 --> 01:09:06.746 And so if this is not running either so OK, this is the. It's
01:09:06.746 --> 01:09:09.846 already been released. There's nothing running. The pipeline
01:09:09.846 --> 01:09:12.541 isn't running. You've got yourself a 25 to 30 minute
01:09:12.541 --> 01:09:15.641 window while cuz if let's say a pipeline starts up, it takes
01:09:15.641 --> 01:09:18.539 what 25 minutes, 20 or 30 minutes sometimes to build. So
01:09:18.539 --> 01:09:21.843 you've got yourself a little bit of time there. So that would be
01:09:21.843 --> 01:09:25.096 the best way to go check it is, is there a pipeline running? If
01:09:25.096 --> 01:09:28.045 there's no pipeline, check the release if the release, if
01:09:28.045 --> 01:09:30.434 there's no release running, you're good to go.
01:09:31.034 --> 01:09:32.144 Got it. Perfect.
01:09:32.554 --> 01:09:36.964 And generally speaking, anything that you guys are doing on those
01:09:36.964 --> 01:09:38.634 QA sites and stage sites.
01:09:39.874 --> 01:09:43.148 Shouldn't be something that would lock up the files, and if
01:09:43.148 --> 01:09:46.586 you're modifying like the app settings directly locally on the
01:09:46.586 --> 01:09:46.804 box.
01:09:48.634 --> 01:09:51.637 Ideally you would do that from the admin using the settings
01:09:51.637 --> 01:09:54.589 editor. Just because it avoids that problem altogether. If
01:09:54.589 --> 01:09:57.642 there's a setting you have to change that isn't supported in
01:09:57.642 --> 01:09:59.494 the admin for one reason or another.
01:10:00.934 --> 01:10:03.934 Let me know. I'd love to make it so it is, but if it's like an
01:10:03.934 --> 01:10:06.505 environment setting like a folder path that those are
01:10:06.505 --> 01:10:09.505 intentionally locked down, then sure, yeah, you're going to go
01:10:09.505 --> 01:10:11.934 in the box and change it. But as much as possible.
01:10:10.864 --> 01:10:14.492 Does everyone know where that site site settings at at editor
01:10:14.492 --> 01:10:18.061 is? Raise your hand if you are unaware or I guess the better
01:10:18.061 --> 01:10:21.631 the Brendan Lyons raise your hand if you know where the site
01:10:21.631 --> 01:10:24.264 maintenance and settings settings editor is.
01:10:31.824 --> 01:10:34.704 Well, we got a few people that don't. That's fantastic.
01:10:35.084 --> 01:10:37.084 Awesome. Cool. So.
01:10:36.664 --> 01:10:39.864 Allow me to welcome you into the 21st century.
01:10:39.604 --> 01:10:42.783 This is, yeah, the this we are so far behind the curve. But
01:10:42.783 --> 01:10:46.121 when we got it, it's so nice to have. It's like dry. It's like
01:10:46.121 --> 01:10:49.458 somebody that didn't know about cars. And then all of a sudden
01:10:49.458 --> 01:10:52.902 now you can get from point A to be so much faster if you come in
01:10:52.902 --> 01:10:56.346 here to the admin and you go to site maintenance. So we removed.
01:10:56.346 --> 01:10:59.525 OK, yeah. We removed the old one. So no worry about the old
01:10:59.525 --> 01:11:01.644 one site maintenance and then settings.
01:11:02.704 --> 01:11:06.103 You just need to know the key for which you are doing, but
01:11:06.103 --> 01:11:07.774 going by so like for example.
01:11:08.934 --> 01:11:11.614 Let's do what's a good one?
01:11:10.774 --> 01:11:14.504 And the nice thing too is this is a partial match. It doesn't
01:11:14.504 --> 01:11:18.173 have to exactly match, so if you're not sure what the key is
01:11:18.173 --> 01:11:21.722 that you're looking for, what you're like, that's probably
01:11:18.194 --> 01:11:18.644 Uh-huh.
01:11:21.084 --> 01:11:21.444 Yeah.
01:11:21.722 --> 01:11:25.512 something related to shipping. You could just type shipping or
01:11:25.512 --> 01:11:29.302 quote or sales quote or anything you want in here and find all
01:11:29.302 --> 01:11:32.791 the settings related to that thumb through and figure out
01:11:32.791 --> 01:11:36.160 which one that you need to change. And I mean it's it's
01:11:36.160 --> 01:11:37.724 just pretty cool, I think.
01:11:37.174 --> 01:11:41.120 And this this works on other things too. So for example like
01:11:41.120 --> 01:11:44.484 authorize.net. So if let's say authorize.net is on.
01:11:45.634 --> 01:11:49.930 Then you can come in here and put in, put in your credentials
01:11:49.930 --> 01:11:54.364 for for authorize.net instead of having to go into the box. So.
01:11:55.284 --> 01:12:00.071 Theoretically, other than for you to grab a backup of the
01:12:00.071 --> 01:12:05.354 files, like if you wanna go grab the app settings that are on a
01:12:05.354 --> 01:12:06.014 QA site.
01:12:07.034 --> 01:12:10.794 I can't really think of much. Maybe maybe debugging.
01:12:12.554 --> 01:12:16.303 Like getting in like true like getting in there. I need to put
01:12:16.303 --> 01:12:19.814 stuff on there and debug. There's not a whole lot that you
01:12:19.814 --> 01:12:23.147 would get in there and do on like the Q or stage server
01:12:23.147 --> 01:12:26.896 directly. Especially because the site now handles the settings
01:12:26.896 --> 01:12:27.194 here.
01:12:28.974 --> 01:12:32.472 So I would try and do most of your site maintenance and app
01:12:32.472 --> 01:12:35.912 settings changes here in the admin because this does write
01:12:35.912 --> 01:12:38.944 back to that app settings dot client dot JSON file.
01:12:39.664 --> 01:12:40.174 Yep.
01:12:40.864 --> 01:12:43.794 And doesn't require you to flip the applet which manually.
01:12:43.504 --> 01:12:44.874 And it correct.
01:12:44.404 --> 01:12:48.042 Yeah, that's that's a big one. Is, yeah. If you modify here, it
01:12:48.042 --> 01:12:51.226 does it right at runtime. You can even enable different
01:12:51.226 --> 01:12:54.807 providers do anything you need to do from here. There are only
01:12:54.807 --> 01:12:58.218 a handful of settings that are explicitly not allowed to be
01:12:58.218 --> 01:13:01.742 edited, like site root URL and the folder path and stuff like
01:13:01.742 --> 01:13:05.040 that. Those it will not allow you to edit because you you
01:13:05.040 --> 01:13:05.324 know.
01:13:06.314 --> 01:13:08.979 Obvious reasons. It's a folder path on the site that it's
01:13:07.464 --> 01:13:08.104 Yeah.
01:13:08.979 --> 01:13:11.644 trying to load from and stuff easily break the site. That
01:13:11.644 --> 01:13:14.400 should you wouldn't be able to get into the editor if those
01:13:14.400 --> 01:13:17.065 were incorrect, and if you change them to something else,
01:13:17.065 --> 01:13:18.214 you'll break the site so.
01:13:18.174 --> 01:13:22.534 So for example, like a shipping step. So if I go to develop.
01:13:23.184 --> 01:13:26.867 And I go into the and I go into check out a lot of stuff in
01:13:26.867 --> 01:13:27.174 here.
01:13:28.394 --> 01:13:31.386 So right now I have, you know, my shipping information and I
01:13:31.386 --> 01:13:34.378 have rate quotes turned on. I could technically come in here
01:13:34.378 --> 01:13:36.144 to purchase pains shipping enabled.
01:13:37.114 --> 01:13:40.736 And I can turn that bad boy off, and then I'm gonna go. I'm gonna
01:13:40.736 --> 01:13:43.864 shipping rates enabled. That's our now one off and save.
01:13:45.614 --> 01:13:49.404 So once this gets done saving all hard refresh this page.
01:13:50.904 --> 01:13:51.944 It's not cached.
01:13:51.654 --> 01:13:53.364 And there's no shipping.
01:13:53.424 --> 01:13:55.344 Yay, it wasn't cashed.
01:13:55.414 --> 01:13:58.755 Yeah, I had played. I I I knew that would work because I played
01:13:58.755 --> 01:14:00.634 with this one for. For Tom's. Yeah.
01:13:58.804 --> 01:14:02.842 You've done this before. OK, cool. Alright. Nice. Now one
01:14:02.842 --> 01:14:07.088 quick note. While I'm thinking about this, there are certain
01:14:07.088 --> 01:14:09.664 things that why does your total say.
01:14:10.554 --> 01:14:11.474 That doesn't add up.
01:14:11.904 --> 01:14:12.494 Yeah it does.
01:14:12.274 --> 01:14:16.095 Well, your card Adams quantity 1 quantity one. Ohh they're more
01:14:16.095 --> 01:14:16.274 OK.
01:14:16.604 --> 01:14:19.204 There's a John Deere for $340,000.
01:14:17.564 --> 01:14:22.214 I didn't. Yeah, I didn't see the show more. I was like, why does
01:14:22.214 --> 01:14:25.934 your total say $300,000? OK, sorry. If you go back.
01:14:25.034 --> 01:14:28.415 This is quite the cart too, right? This is like one you'd go
01:14:27.144 --> 01:14:27.394 Yeah.
01:14:28.415 --> 01:14:31.908 to like Walmart, just to like mess with people on shoot trees,
01:14:30.134 --> 01:14:30.514 Yeah.
01:14:31.908 --> 01:14:34.624 technology. John Deere tractor. Sorry, go ahead.
01:14:33.714 --> 01:14:37.597 And echo. Yeah. So go back to that site maintenance editor and
01:14:34.844 --> 01:14:35.574 Yeah.
01:14:37.064 --> 01:14:37.484 Uh-huh.
01:14:37.597 --> 01:14:39.384 type and I'm trying to think.
01:14:40.084 --> 01:14:44.134 Umm. Type in dashboard? I think this is probably a good example.
01:14:44.604 --> 01:14:46.174 I think about the media exclusive 1.
01:14:47.354 --> 01:14:48.744 No, I'm looking for.
01:14:47.494 --> 01:14:49.244 Or that depends on depends on I mean.
01:14:49.574 --> 01:14:52.586 Uh, that, that too, but uh, go to the next page. There's a
01:14:52.586 --> 01:14:55.598 specific thing I'm trying to find in here where, hey, keep
01:14:54.904 --> 01:14:56.134 The URL's one.
01:14:55.598 --> 01:14:55.904 going.
01:14:56.834 --> 01:14:57.764 Ask for routes.
01:14:58.394 --> 01:15:01.084 Not necessarily. It's specific to the editor next page.
01:15:00.794 --> 01:15:01.134 Umm.
01:15:02.714 --> 01:15:07.257 Damn, I can't find it. What I'm trying to find is that obviously
01:15:07.257 --> 01:15:11.520 for booleans and strings and ints and all that kind of thing
01:15:11.520 --> 01:15:15.434 and editor is easy for that a text box or a checkbox or
01:15:12.274 --> 01:15:13.864 Oh, I know what you're talking about.
01:15:15.434 --> 01:15:19.208 whatever. There are however, certain things there are
01:15:16.714 --> 01:15:18.524 It's enabled features.
01:15:19.208 --> 01:15:22.074 however, certain things that don't have.
01:15:22.494 --> 01:15:22.874 They.
01:15:22.794 --> 01:15:24.434 Uh and editor?
01:15:25.194 --> 01:15:29.000 And that's because they would have to be very specific in
01:15:29.000 --> 01:15:32.872 custom, uh. And so in those scenarios, that editor section
01:15:32.872 --> 01:15:34.644 on the right will be empty.
01:15:34.694 --> 01:15:35.314 Provider.
01:15:35.964 --> 01:15:38.190 You can actually see also there's arrays of strings that I
01:15:38.190 --> 01:15:40.378 did. Yeah. So you can see an array you can add and delete
01:15:38.894 --> 01:15:39.154 Yeah.
01:15:40.378 --> 01:15:41.434 options. That's pretty cool.
01:15:41.444 --> 01:15:43.674 So if you stop editing, it puts it back in and.
01:15:43.544 --> 01:15:46.236 Yeah, it just looks at like that, but I'm I was trying to
01:15:46.236 --> 01:15:49.114 remember one of the there are certain settings that are like.
01:15:50.534 --> 01:15:50.994 Uh.
01:15:52.374 --> 01:15:56.490 There are certain settings that are like an object or something
01:15:56.490 --> 01:16:00.284 complex as the value of the setting. When that's the case.
01:16:01.254 --> 01:16:02.864 There may not be a.
01:16:03.714 --> 01:16:07.065 And editor built for it. And if there's not, then the current
01:16:07.065 --> 01:16:10.363 when you have enable editing on the current value field will
01:16:10.363 --> 01:16:11.444 just be a blank box.
01:16:12.164 --> 01:16:14.841 If there's something you routinely come across that
01:16:14.841 --> 01:16:18.187 doesn't have an editor and it's, you know, it's annoying because
01:16:18.187 --> 01:16:21.224 you have to go to the box and edit manually at that point.
01:16:21.924 --> 01:16:25.022 Please let us know what that is because we can add new new
01:16:25.022 --> 01:16:28.067 little editor UI for some of those things that are common
01:16:28.067 --> 01:16:31.165 problems. If it's something that's like I've only run into
01:16:31.165 --> 01:16:34.579 that once, it would be cool, but it's not a big deal. Then we're
01:16:34.579 --> 01:16:36.574 not gonna worry about it cuz angular.
01:16:36.994 --> 01:16:39.619 Umm, but uh. But if it's something that you're, like,
01:16:39.619 --> 01:16:42.584 almost every project you're like, man, it would be cool if I
01:16:42.584 --> 01:16:45.258 could change XYZ from the settings in the admin, but I
01:16:45.258 --> 01:16:48.223 just can't. It does. There's no setting for it or no editor,
01:16:48.223 --> 01:16:49.584 then definitely let us know.
01:16:52.144 --> 01:16:54.464 Indeed, I was trying to find. I thought that.
01:16:54.544 --> 01:16:57.914 Umm, I guess the tax like the the.
01:16:58.654 --> 01:17:01.579 There's a couple settings that like the tax tables and shipping
01:17:01.579 --> 01:17:04.366 like like flat shipping use, but I don't think that actually
01:17:02.174 --> 01:17:02.994 Yeah.
01:17:04.366 --> 01:17:07.063 stored like that. It's stored actually in the database. So
01:17:06.574 --> 01:17:09.404 Yeah. And I can't. I can't remember.
01:17:07.063 --> 01:17:07.794 never mind. Yep.
01:17:10.664 --> 01:17:13.509 I thought the the reason I had you searched dashboard is I
01:17:13.509 --> 01:17:16.401 thought the custom dashboard routes one was gonna do it but
01:17:16.401 --> 01:17:17.414 unfortunately not so.
01:17:17.244 --> 01:17:22.323 Cut. Ohh, cool. Well, that is pretty much it I think. Ohh, I
01:17:22.323 --> 01:17:27.735 need to go reenable those steps and then I'm going to. I'm gonna
01:17:26.964 --> 01:17:27.274 Yeah.
01:17:27.735 --> 01:17:32.814 steal Jesse's Thunder if you're OK with that Jesse. And show
01:17:32.814 --> 01:17:37.394 real quick the coolness that Jesse just did this week.
01:17:37.064 --> 01:17:40.530 I think I think he dropped from here and the nick I saw your
01:17:39.134 --> 01:17:39.474 Left.
01:17:40.314 --> 01:17:41.004 OK, cool.
01:17:40.530 --> 01:17:44.167 hand, Nick. I saw your hand up earlier before we looked at this
01:17:42.434 --> 01:17:42.904 Oh yeah.
01:17:44.167 --> 01:17:47.634 stuff. Did you have a question that we haven't answered yet?
01:17:48.604 --> 01:17:52.256 Uh, yes. So for the app settings. If you are creating a
01:17:52.256 --> 01:17:56.364 brand new and I know you just said to let you know and you can
01:17:56.364 --> 01:17:59.951 add those to the admin portal list, what is the normal
01:17:59.951 --> 01:18:04.059 procedure for putting those on QA or staging environments like
01:18:04.059 --> 01:18:07.254 the weather provider for example, has a bunch of
01:18:07.254 --> 01:18:11.363 different app settings that are brand new and still need to be
01:18:11.363 --> 01:18:11.754 added.
01:18:11.474 --> 01:18:14.929 Yep, so this editor will pick up all app settings automatically
01:18:14.929 --> 01:18:18.438 so you don't have to add them to any additional thing. You don't
01:18:18.438 --> 01:18:21.839 have to run an ET4 or anything like that to get these in here.
01:18:21.839 --> 01:18:23.944 It'll just automatically pick them up.
01:18:24.454 --> 01:18:28.576 Umm. So ideally what you would do at that point is if you make
01:18:28.576 --> 01:18:32.371 a PR that you know is gonna require some app settings for
01:18:32.371 --> 01:18:35.904 the functionality to work for people on their locals.
01:18:37.444 --> 01:18:40.414 You should send a message in your dev chat that says hey
01:18:40.414 --> 01:18:43.488 guys, this PR is about to go through. Once it does, you're
01:18:43.488 --> 01:18:46.875 gonna need to add these settings on your local and then the keys
01:18:46.875 --> 01:18:50.001 and values to add and while you're thinking about that, you
01:18:50.001 --> 01:18:53.388 can come in here on once that PR goes through, you can just jump
01:18:53.388 --> 01:18:56.514 in the settings editor and set those values directly on QA.
01:18:57.174 --> 01:18:59.164 Umm so by.
01:18:58.534 --> 01:19:02.020 One thing we well, I guess I guess you wouldn't. I was gonna
01:19:02.020 --> 01:19:05.563 say one thing. We do wanna do moving forward is allow for the
01:19:05.563 --> 01:19:09.106 the app settings dot client dot JSON to be in source control.
01:19:09.106 --> 01:19:12.535 But if you're doing credentials like the Weather Service or
01:19:12.535 --> 01:19:16.250 payment provider those we don't wanna have in source control. So
01:19:16.250 --> 01:19:19.793 the ones that we would have in so you would put those kind of
01:19:19.793 --> 01:19:23.279 in the environment one what you would put in client are more
01:19:23.279 --> 01:19:26.651 like just features they get turned on. But I caught myself
01:19:26.651 --> 01:19:29.794 as I was about to say that because something like the.
01:19:29.874 --> 01:19:32.509 Other settings because it's credential based. You'd wanna
01:19:32.294 --> 01:19:32.844 Yeah.
01:19:32.509 --> 01:19:34.554 put that in the environment, not the client.
01:19:33.954 --> 01:19:36.962 Yeah, this isn't like the API credentials or anything. It's
01:19:36.962 --> 01:19:39.570 like the low shipping temperature threshold and the
01:19:39.124 --> 01:19:42.904 OK. Yeah, that that can go in the client file for sure. Yeah.
01:19:39.570 --> 01:19:41.024 states that they're allowing.
01:19:42.684 --> 01:19:43.134 OK.
01:19:42.904 --> 01:19:46.501 UM, by the way. Yeah, very important. Very important thing
01:19:46.501 --> 01:19:49.854 that is directly related to what Eric was just saying.
01:19:50.494 --> 01:19:54.160 There are two there are two apps settings files which might be
01:19:54.160 --> 01:19:57.651 kind of annoying sometimes, but it's extremely important to
01:19:57.651 --> 01:19:58.524 understand the.
01:19:58.604 --> 01:20:02.789 Umm, the difference between them, the app Settings
01:20:02.789 --> 01:20:04.184 environment file?
01:20:04.894 --> 01:20:07.014 This file contains only.
01:20:08.374 --> 01:20:11.384 Either things that are relevant to your local or the environment
01:20:11.384 --> 01:20:13.654 that the the site is running on and credentials.
01:20:14.374 --> 01:20:18.599 They should not contain any settings that that are like
01:20:18.599 --> 01:20:20.184 feature sets or like.
01:20:22.104 --> 01:20:26.049 Client specific configuration that's not a credential and then
01:20:26.049 --> 01:20:29.494 on the flip side, the client file should only contain.
01:20:30.674 --> 01:20:33.832 Feature sets and General general site settings. Never
01:20:33.832 --> 01:20:37.693 credentials, never folder paths, anything like that. Those should
01:20:37.693 --> 01:20:40.968 not go in the client file because we don't want that in
01:20:40.968 --> 01:20:44.185 source control. Obviously we don't passwords in source
01:20:44.185 --> 01:20:47.403 control, but it also causes problems if you have local
01:20:47.403 --> 01:20:50.737 folder paths and source control that can break stuff for
01:20:50.737 --> 01:20:51.614 everybody else.
01:20:56.544 --> 01:20:59.733 Brandon, can you repeat what you said for environment, at least
01:20:59.733 --> 01:21:02.324 for me, you cut out for five or six seconds though.
01:21:01.134 --> 01:21:04.614 Oh, I'm sorry. Yeah, my, my internet's been crap lately.
01:21:02.354 --> 01:21:03.554 Hey, go. Here you go.
01:21:05.494 --> 01:21:08.370 Is it this what you're talking about? Because this is an object
01:21:08.014 --> 01:21:10.802 Uh. Perfect. Yeah. Perfect. Yeah. That's a great example.
01:21:08.370 --> 01:21:09.404 sales invoice load fee.
01:21:10.802 --> 01:21:13.350 You can see that the value editor is just blank. The
01:21:13.350 --> 01:21:16.139 default value says NA and AA cause it doesn't know how to
01:21:16.139 --> 01:21:16.764 display that.
01:21:17.524 --> 01:21:18.044 Umm.
01:21:18.864 --> 01:21:21.702 That's an example like. I know no ones going to be editing
01:21:21.702 --> 01:21:23.914 sales invoice, late fees on the regular, but.
01:21:23.674 --> 01:21:24.344 Yeah.
01:21:25.034 --> 01:21:28.821 But if you come across one that that might be more frequently
01:21:28.821 --> 01:21:32.731 you needed then let me know. But Nick, to answer your question,
01:21:32.731 --> 01:21:33.464 think about.
01:21:35.044 --> 01:21:38.817 Starting at the client level, if it is a credential, a folder
01:21:38.817 --> 01:21:42.528 path, or a site specific URL like rock qa.clarityclient.com,
01:21:42.528 --> 01:21:46.544 that kind of thing, none of that should be in the client file. If
01:21:46.544 --> 01:21:50.560 it is any of those three things, they site specific URL, a folder
01:21:50.560 --> 01:21:54.272 path, or a part of a credential, username, password, account
01:21:54.272 --> 01:21:58.106 number, or anything like that. None of those should be in your
01:21:58.106 --> 01:22:01.574 client file. That should all go in the environment file.
01:22:03.234 --> 01:22:06.369 The reason the reason we're doing that and the reason we
01:22:06.369 --> 01:22:09.889 have this split is because the idea behind it, which we haven't
01:22:09.889 --> 01:22:13.354 gotten to yet, is that we will actually be able to store these
01:22:13.354 --> 01:22:16.929 client settings files in source control. And that way when never
01:22:16.929 --> 01:22:20.559 you make your weather PR instead of having to tell everyone, hey,
01:22:20.559 --> 01:22:23.914 turn these app settings on. So your site works, you just add
01:22:23.914 --> 01:22:27.544 them to your app settings client and that gets committed with the
01:22:27.544 --> 01:22:31.064 rest of your stuff and everybody automatically has the required
01:22:31.064 --> 01:22:33.264 settings besides credentials obviously.
01:22:33.694 --> 01:22:36.154 Umm that being said.
01:22:37.614 --> 01:22:40.183 We need to make sure that everybody understands the
01:22:40.183 --> 01:22:43.295 difference between the two and that they're diligent about not
01:22:43.295 --> 01:22:46.308 committing credentials. That's part of why we haven't rolled
01:22:46.308 --> 01:22:49.124 this out yet outside of some technical limitation on the
01:22:49.124 --> 01:22:52.187 settings editor. Always storing things in client is we sorry,
01:22:52.187 --> 01:22:53.224 let me close my door.
01:22:54.644 --> 01:22:57.154 We we have to make sure that everybody is.
01:22:57.844 --> 01:23:02.277 Doing it correctly before we can roll that out to to everybody so
01:23:02.277 --> 01:23:06.575 we don't have credentials being committed to source control and
01:23:06.575 --> 01:23:07.784 all that jazz, so.
01:23:09.674 --> 01:23:10.874 Does that clear that up, Nick?
01:23:12.124 --> 01:23:13.314 Yeah, yeah, definitely.
01:23:13.664 --> 01:23:18.282 OK, cool. Any other questions on pipelines or app settings or
01:23:14.124 --> 01:23:14.734 Sweet.
01:23:18.282 --> 01:23:22.974 really just kind of in general, I feel like got a minute here.
01:23:28.674 --> 01:23:29.344 Sweets.
01:23:32.214 --> 01:23:36.764 Yay, another successful Friday training.
01:23:38.044 --> 01:23:38.854 Thanks guys.
01:23:38.384 --> 01:23:39.584 Uh, yeah.
01:23:39.774 --> 01:23:40.474 That's been good.
01:23:43.514 --> 01:23:45.084 Alright, have a good weekend everybody.
01:23:45.314 --> 01:23:45.874 Thanks everybody.