00:00:04.000 --> 00:00:06.744 About pipelines, when we're having some issues with the
00:00:06.744 --> 00:00:07.870 pipelines, but it's OK.
00:00:09.410 --> 00:00:11.340 The .1 might say really.
00:00:11.600 --> 00:00:16.340 Yeah, actually. So I going to share.
00:00:17.310 --> 00:00:17.900 My screen.
00:00:19.010 --> 00:00:22.780 And then talk it everyone for one hour and 20 minutes.
00:00:25.090 --> 00:00:27.150 I'll cover you for 15 at the end. How about that?
00:00:27.540 --> 00:00:28.190 Perfect.
00:00:28.310 --> 00:00:30.550 Yeah, like at least 10. I can give you a good 10.
00:00:31.580 --> 00:00:32.100 Great.
00:00:34.450 --> 00:00:34.960 So.
00:00:34.770 --> 00:00:36.410 Alright, one hour of pipelines. Let's go.
00:00:36.780 --> 00:00:40.572 Yep. See what we got. All right, so I I'm pretty sure everyone
00:00:40.572 --> 00:00:44.364 knows what the pipelines are and what we use them for, but I'm
00:00:44.364 --> 00:00:46.410 going to cover that first anyway.
00:00:47.080 --> 00:00:52.344 Umm, we use uh pipelines and releases in Azure for two things
00:00:52.344 --> 00:00:55.570 or primarily two things I should say.
00:00:56.250 --> 00:01:01.494 Uh, analyzing pull requests to make sure that they build and
00:01:01.494 --> 00:01:05.190 that there's no issues and everything and.
00:01:06.760 --> 00:01:11.388 Deploying websites automatically for us so that we don't have to
00:01:11.388 --> 00:01:12.100 go in and.
00:01:12.890 --> 00:01:15.360 You know, a lot of people here remember the.
00:01:16.030 --> 00:01:20.243 The old days of RDP into DFO and then Git pull and manually
00:01:17.370 --> 00:01:19.990 Back in the Stony age.
00:01:20.243 --> 00:01:24.526 rebuilding the front and the back end every time you want it
00:01:24.526 --> 00:01:25.860 to deploy a change.
00:01:27.850 --> 00:01:30.030 Yes, the Stone Age. It's very true.
00:01:29.730 --> 00:01:32.900 A server was uphill both ways in the snow too. It was crazy.
00:01:32.690 --> 00:01:34.880 It was, yeah. Couldn't even believe it.
00:01:35.670 --> 00:01:35.950 Well.
00:01:36.380 --> 00:01:41.658 Yeah. But anyway, so those are the two primary things that we
00:01:41.658 --> 00:01:43.190 use pipelines for.
00:01:43.790 --> 00:01:48.568 Umm, so if you I mean you can you can whoopsies look at any
00:01:48.568 --> 00:01:53.663 old poll request here. So we can look at this one you can Click
00:01:53.663 --> 00:01:58.520 to view 3 checks and see which things it did. We can look at
00:01:58.520 --> 00:02:02.660 this analyzer and this is actually a great example.
00:02:04.690 --> 00:02:09.760 Both the angular and react front end analyzers on pull requests.
00:02:10.950 --> 00:02:15.277 Due to some weirdness with the way that the build tools report
00:02:15.277 --> 00:02:19.809 errors, we actually don't have a robust, consistent way to detect
00:02:19.809 --> 00:02:22.350 build errors on these pipelines, so.
00:02:24.510 --> 00:02:27.817 Really this is more down to anybody that's reviewing PR's,
00:02:27.817 --> 00:02:30.899 but for a lot of these especially important ones, it's
00:02:30.899 --> 00:02:33.420 really important to check these build steps.
00:02:33.510 --> 00:02:36.651 Umm. And see and this one did not actually succeed, but it
00:02:36.651 --> 00:02:40.111 says that it did. And again this is because we don't really have
00:02:40.111 --> 00:02:40.590 a way to.
00:02:41.740 --> 00:02:43.740 Detect when they do or don't. UM.
00:02:44.780 --> 00:02:45.680 But uh.
00:02:47.440 --> 00:02:51.404 Anyway, so the the pipelines are all built by individual tasks
00:02:51.404 --> 00:02:54.360 that run one at a time in order top to bottom.
00:02:55.010 --> 00:02:59.722 And these are effectively just the steps required to do
00:02:59.722 --> 00:03:05.106 whatever that pipelines made to do this one this pipeline we're
00:03:05.106 --> 00:03:10.154 looking at is the 2022.2 CEF front end, React Analyzer. And
00:03:10.154 --> 00:03:11.920 so all it does is it.
00:03:12.720 --> 00:03:14.030 Pulls in the.
00:03:14.990 --> 00:03:18.210 Yeah, you know the the the code pulls in CEF configs.
00:03:19.560 --> 00:03:23.962 Switches to node version 16. NPM install build switches back to
00:03:23.962 --> 00:03:28.226 11.15 for other older projects to be on the right version and
00:03:28.226 --> 00:03:32.490 that's it. Just it just does that and moves on with its live.
00:03:33.740 --> 00:03:36.714 Ideally this step would fail because it didn't actually
00:03:36.714 --> 00:03:40.007 successfully build, and we're working on that. We'll get that
00:03:40.007 --> 00:03:43.140 in a more stable place at some point, hopefully soon, but.
00:03:44.750 --> 00:03:49.510 You've all I'm sure, all of us have seen the dreaded.
00:03:50.220 --> 00:03:53.893 Red X on a PR. I don't think I think. Ohh perfect. This one
00:03:53.893 --> 00:03:57.749 still got this weird TS config, one that I thought we fixed on
00:03:57.749 --> 00:04:01.605 the on the pipelines but anyway this just means that something
00:04:01.605 --> 00:04:05.523 about this analyzer failed. So if you're seeing this on your PR
00:04:05.523 --> 00:04:09.011 and this is kind of the main thing that we wanted to get
00:04:09.011 --> 00:04:12.745 into, was PR analyzer issues and deployment issues. So we'll
00:04:12.745 --> 00:04:16.663 start with Jr analyzer issues if you see something like this on
00:04:16.663 --> 00:04:18.070 your PR, it means that.
00:04:18.970 --> 00:04:23.257 There's something wrong, whether it's on the the pipeline itself,
00:04:23.257 --> 00:04:26.180 which is the case for this issue, or on the.
00:04:27.760 --> 00:04:29.080 In your actual code.
00:04:29.860 --> 00:04:33.082 Umm this one is just a weird thing with the way the pipeline
00:04:33.082 --> 00:04:36.515 builds it complaints about files not being there and you have to
00:04:36.515 --> 00:04:39.631 add something to the csproj file and I thought that we had
00:04:39.631 --> 00:04:42.642 already fixed this, but I guess whatever project this is
00:04:42.642 --> 00:04:45.969 probably didn't pull that fix. So technically this one is kind
00:04:45.969 --> 00:04:49.085 of an oddity of the pipeline that actually requires a code
00:04:49.085 --> 00:04:51.938 fix, but it also doesn't actually have anything to do
00:04:51.938 --> 00:04:55.212 with the code written on this PR. It's just a fix needs to be
00:04:55.212 --> 00:04:55.740 pulled in.
00:04:56.880 --> 00:04:57.250 But.
00:04:57.830 --> 00:05:00.848 Uh, if you're ever not sure, like if you get a weird,
00:05:00.848 --> 00:05:03.250 confusing looking error message like this.
00:05:04.210 --> 00:05:09.246 Screenshot the message link the PR with the screenshot on like
00:05:09.246 --> 00:05:13.961 the development team on teams and 99% of the time somebody
00:05:13.961 --> 00:05:14.680 will say.
00:05:15.360 --> 00:05:18.769 Uh, it looks like you're you. You're missing XYZ fix. Here's a
00:05:18.769 --> 00:05:22.070 link to a commit or something that you know to show you what
00:05:22.070 --> 00:05:23.260 you're supposed to do.
00:05:25.310 --> 00:05:28.685 If not, and it's a new issue, then we'll probably tell you as
00:05:28.685 --> 00:05:30.590 much and start looking into it so.
00:05:31.130 --> 00:05:34.421 This is probably a good point for me to interject here or
00:05:34.421 --> 00:05:37.826 something, so when you when you create a PR, those you know
00:05:37.826 --> 00:05:41.287 those analyzers have to run which be all set are essentially
00:05:41.287 --> 00:05:44.975 building. You know the code and making sure it'll build and does
00:05:44.975 --> 00:05:48.380 some other things. Run some tests and the back end analyzer
00:05:48.380 --> 00:05:51.954 especially is going to take a little bit of time. So it's only
00:05:51.954 --> 00:05:55.529 natural and obviously expected that when you first submit a PR
00:05:55.529 --> 00:05:59.217 and you know you have your work items linked and everything like
00:05:59.217 --> 00:06:01.430 that, you move on with something else.
00:06:02.400 --> 00:06:06.665 However, one of the major sort of weaknesses that we have right
00:06:06.665 --> 00:06:10.731 now are coming back, checking and fixing the PR's. So I just
00:06:10.731 --> 00:06:14.729 wanted to make sure everyone knew and and see if anyone has
00:06:14.729 --> 00:06:18.994 any questions or concerns about this that when you submit a PR,
00:06:18.994 --> 00:06:22.793 you are not done until that PR has been approved and has
00:06:22.793 --> 00:06:26.725 actually gone through built successfully and merged. And I
00:06:26.725 --> 00:06:29.790 just wanted to make sure everybody knew that.
00:06:31.080 --> 00:06:34.490 Ideally, if you submit a PR before and I'm just making this
00:06:34.490 --> 00:06:37.956 up, but I mean if you submit a PR in the morning, ideally we
00:06:37.956 --> 00:06:39.660 get it through later that day.
00:06:40.750 --> 00:06:44.534 Umm. And there's a couple reasons for that, but the the
00:06:44.534 --> 00:06:48.454 the big one is we wanna be delivering working software by
00:06:48.454 --> 00:06:49.940 the end of the Sprint.
00:06:50.410 --> 00:06:54.756 Umm, so you know, ideally these PR's get in same day and then
00:06:54.756 --> 00:06:58.540 we're able to, you know, do some testing or whatever.
00:06:59.840 --> 00:07:03.280 So I'll just stop there and see if anybody has any questions or
00:07:03.280 --> 00:07:06.666 you know, comments or concerns on that thought process. One of
00:07:06.666 --> 00:07:10.052 the things I'll point out is I know that a lot of people don't
00:07:10.052 --> 00:07:11.180 look at their e-mail.
00:07:12.050 --> 00:07:16.438 But you do get updates in your outlook, yeah, like your outlook
00:07:16.438 --> 00:07:20.414 e-mail every time James, BLM, Eric, Jesse somebody adds a
00:07:20.414 --> 00:07:24.322 comment, you get an e-mail immediately when a comment is
00:07:24.322 --> 00:07:28.298 added. If if a build fails or something fails, you get an
00:07:28.298 --> 00:07:32.754 e-mail as soon as that happens. So the way that I was able to do
00:07:32.754 --> 00:07:36.936 this back when I was writing more code is I would always try
00:07:36.936 --> 00:07:40.706 to fix the PR's relatively quickly, because I would, I
00:07:40.706 --> 00:07:42.420 would catch in my e-mail.
00:07:42.490 --> 00:07:46.251 That something went wrong and then I would go and check the PR
00:07:46.251 --> 00:07:49.953 so you don't have to do it that way, but definitely something
00:07:49.953 --> 00:07:53.117 that we need to improve on is people keeping up with
00:07:53.117 --> 00:07:56.938 monitoring their existing PR's and making sure that we're we're
00:07:56.938 --> 00:07:58.430 getting them through the.
00:07:59.790 --> 00:08:03.220 Yep, the analyzers are not only a tool for.
00:08:04.970 --> 00:08:06.380 Reviewers and or?
00:08:06.480 --> 00:08:09.848 Umm, you just the system to make sure that everything is gonna
00:08:09.848 --> 00:08:13.109 work, but it's also a tool for you to know that your code is
00:08:13.109 --> 00:08:16.530 good and that it passed at least some sort of technical muster.
00:08:17.650 --> 00:08:18.950 On a similar note.
00:08:20.610 --> 00:08:22.730 When you make a PR and and this.
00:08:23.550 --> 00:08:26.781 This is something that it doesn't happen as much now as it
00:08:26.781 --> 00:08:30.340 used to, but always a good thing to call out when you make a PR.
00:08:31.710 --> 00:08:34.352 There's a little section I wish it would show me the little OK.
00:08:34.352 --> 00:08:35.260 Whatever else do this?
00:08:37.370 --> 00:08:41.420 That guy into this branch, there's a little section.
00:08:42.180 --> 00:08:44.830 Before you even make it, that will show you the changes you
00:08:44.830 --> 00:08:45.050 made.
00:08:45.790 --> 00:08:47.190 Please look at this.
00:08:48.800 --> 00:08:51.803 And if there's files in here that you didn't mean to modify,
00:08:51.803 --> 00:08:54.560 you accidentally committed something or whatever it is.
00:08:55.340 --> 00:08:57.230 This is your last stop.
00:08:58.420 --> 00:09:02.006 To look at this and say, huh, I should probably get rid of this
00:09:02.006 --> 00:09:05.312 console log I left in here, or I didn't mean to commit the
00:09:05.312 --> 00:09:06.880 changes to this file at all.
00:09:07.400 --> 00:09:08.090 Umm.
00:09:08.870 --> 00:09:10.780 And then fix those before you make the PR.
00:09:11.450 --> 00:09:14.904 Umm, because number one, just you just should do that. But #2
00:09:14.904 --> 00:09:17.967 it, it saves US time on reviewing to not have to leave
00:09:17.967 --> 00:09:21.477 comments of like, please remove this console log and then wait
00:09:21.477 --> 00:09:24.150 for you to come back and fix it so we can then.
00:09:24.840 --> 00:09:29.176 You know, approve the PR later. So this this page should be your
00:09:29.176 --> 00:09:30.310 your best friend.
00:09:32.530 --> 00:09:33.640 Please use it.
00:09:35.360 --> 00:09:39.617 And so just another good thing to call out, this is your, this
00:09:39.617 --> 00:09:43.805 is your last line of defense on, on you making a pull request
00:09:43.805 --> 00:09:46.440 with stuff that you didn't mean to so.
00:09:48.250 --> 00:09:48.780 Anyway.
00:09:51.720 --> 00:09:57.819 Just want to put that out there. OK, so back to pipelines and
00:09:57.819 --> 00:09:58.310 such.
00:09:58.950 --> 00:10:03.284 But if you had it, but if Brent did, you didn't remember or or
00:09:59.070 --> 00:09:59.680 Umm.
00:10:03.284 --> 00:10:06.861 didn't remember changing something, or it certainly
00:10:06.861 --> 00:10:11.332 wasn't to file that you changed, but from some kind of weird git
00:10:11.332 --> 00:10:15.390 thing, it appeared that it is your PR modifying some file.
00:10:16.040 --> 00:10:17.060 Say it's a back end.
00:10:16.060 --> 00:10:20.553 You should probably merge the latest of your target branch
00:10:20.553 --> 00:10:24.970 into your branch and resolve. Excuse me resolve any merge
00:10:24.970 --> 00:10:26.340 conflicts because.
00:10:25.580 --> 00:10:27.470 I was just playing devil's advocate, of course.
00:10:27.110 --> 00:10:31.189 Yeah, yeah. And if you're still having git weirdness at that
00:10:31.189 --> 00:10:31.590 point?
00:10:32.770 --> 00:10:35.882 And you're not sure how to fix it. Ask for help so we can make
00:10:35.882 --> 00:10:38.400 sure that you don't accidentally lose any work or.
00:10:39.040 --> 00:10:42.630 Uh, or break anything else get
00:10:43.570 --> 00:10:47.680 Especially when it breaks, it
00:10:48.540 --> 00:10:48.940 Umm.
00:10:50.130 --> 00:10:50.540 Yeah.
00:10:51.240 --> 00:10:53.506 But that's a good question. It's a good point. That does happen
00:10:53.506 --> 00:10:53.860 sometimes.
00:10:56.660 --> 00:10:58.400 All right, so.
00:10:59.300 --> 00:11:02.715 That's kind of the pull request side of things, but like I said,
00:11:02.715 --> 00:11:05.919 the other thing we use it for and and arguably well, I guess
00:11:05.919 --> 00:11:09.176 not reading really arguably just the more complicated side of
00:11:09.176 --> 00:11:11.330 pipelines is using them for deployments.
00:11:12.530 --> 00:11:13.160 So.
00:11:14.930 --> 00:11:18.559 Trying to remember the best way to get to this. I mean you go to
00:11:18.559 --> 00:11:21.908 the pipelines page and you can see here's all the pipelines
00:11:21.908 --> 00:11:25.314 that have run. You can see some of them have Red X's. That's
00:11:25.314 --> 00:11:26.430 obviously not ideal.
00:11:27.220 --> 00:11:30.503 Umm. And that's the kind of thing you wanna look for. So
00:11:30.503 --> 00:11:32.230 let's say that I'm working on.
00:11:33.670 --> 00:11:34.410 Acne.
00:11:35.220 --> 00:11:40.232 And I noticed that let's say QA says hey, you marked this as
00:11:40.232 --> 00:11:44.750 deployed to QA, but I'm still seeing the same problem.
00:11:46.360 --> 00:11:49.338 And you're like, well, that's weird, because my PR definitely
00:11:49.338 --> 00:11:49.770 fixed it.
00:11:50.660 --> 00:11:54.402 First thing you should check on the pipeline project is did the
00:11:54.402 --> 00:11:58.028 release actually go through or did the pipeline go through so
00:11:58.028 --> 00:11:59.840 you can go to all clients Acme.
00:12:00.450 --> 00:12:03.412 And here's your here's your pipeline, and oh, the pipeline
00:12:03.412 --> 00:12:06.525 failed. The last time I tried to run. And then you can click.
00:12:06.525 --> 00:12:09.386 Keep in mind this is kind of weird, but this is a really
00:12:09.386 --> 00:12:12.549 useful thing to know. There's a difference between clicking on
00:12:12.549 --> 00:12:15.460 its name and clicking on the last run that it highlights.
00:12:17.150 --> 00:12:20.321 Most of the time, you probably just need to click on the like
00:12:20.321 --> 00:12:22.570 the last time it ran and see what happened.
00:12:23.270 --> 00:12:25.975 And in this case and then you
00:12:25.975 --> 00:12:28.680 here and that will take you to all the steps and we can go and
00:12:28.680 --> 00:12:29.410 see what happens.
00:12:31.060 --> 00:12:34.490 It did not like a skin name for this run.
00:12:36.560 --> 00:12:41.090 Apparently there's No 7 portal store front skins Acme.
00:12:41.920 --> 00:12:42.710 UM.
00:12:43.710 --> 00:12:48.207 So that is interesting, but I'm glad I had a a a a pipeline that
00:12:48.207 --> 00:12:52.080 that that actually didn't go through pretty convenient.
00:12:54.310 --> 00:12:58.331 Uh, just to show what happens if you don't click on the last run
00:12:58.331 --> 00:13:02.291 and you just click on the name, it will take you to a page that
00:13:02.291 --> 00:13:06.312 shows you all the previous runs. As you can see, this one hasn't
00:13:06.312 --> 00:13:06.930 succeeded.
00:13:07.930 --> 00:13:08.610 In a while.
00:13:11.390 --> 00:13:12.450 Apparently since June.
00:13:14.410 --> 00:13:15.790 So we should probably look into that.
00:13:16.540 --> 00:13:19.659 I bet it's well, these are different areas down here. No,
00:13:19.659 --> 00:13:21.810 they're not. Actually all of these are.
00:13:23.520 --> 00:13:27.846 Not found skin for source folder for the skin, so that's cool.
00:13:27.846 --> 00:13:30.180 Someone should probably fix that.
00:13:33.340 --> 00:13:36.102 If you find an issue with the with the pipeline, that's
00:13:36.102 --> 00:13:39.209 something like that where it's like, hey, there's not supposed
00:13:39.209 --> 00:13:41.280 to be an Acme scan. Why does it want one?
00:13:42.000 --> 00:13:42.710 Umm.
00:13:43.480 --> 00:13:45.330 Post that in the development team as well.
00:13:45.710 --> 00:13:52.500 Umm and either me, James, Jesse or TMK.
00:13:53.640 --> 00:13:57.025 Or Eric or somebody who has pipeline permissions will come
00:13:57.025 --> 00:14:00.811 in and fix it. This one probably just needs the skin name changed
00:14:00.811 --> 00:14:03.220 on the on the create Artifact task group.
00:14:04.280 --> 00:14:05.770 So I'm.
00:14:05.170 --> 00:14:05.370 The.
00:14:05.450 --> 00:14:08.848 This is actually a perfect example for why we're talking
00:14:08.848 --> 00:14:10.100 about this right now.
00:14:11.200 --> 00:14:14.190 So I can just pick on somebody here.
00:14:15.910 --> 00:14:19.685 I hero pick on you a little bit so if if this so you know
00:14:19.430 --> 00:14:19.710 OK.
00:14:19.685 --> 00:14:23.265 something fails, something goes wrong on your PR whose
00:14:23.265 --> 00:14:26.910 responsibility is it to make sure this PR goes through?
00:14:28.040 --> 00:14:29.040 Uh mine?
00:14:29.630 --> 00:14:33.182 Yeah, absolutely. So what Brendan said is, is incredibly
00:14:33.182 --> 00:14:37.045 important about reaching out for help when it's something you
00:14:37.045 --> 00:14:40.596 don't understand. That is absolutely what you should do.
00:14:40.596 --> 00:14:44.209 And I think the the thought process might have previously
00:14:44.209 --> 00:14:48.010 been well, that's just an issue with the server. That's just
00:14:48.010 --> 00:14:51.748 something that whoever set up the pipeline did and that all
00:14:51.748 --> 00:14:55.673 may be true, but you're the only like if you've submitted that
00:14:55.673 --> 00:14:55.860 PR.
00:14:56.650 --> 00:15:00.530 You and any other developer that's on that project are the
00:15:00.530 --> 00:15:04.672 only people who are going to be presently aware of that issue,
00:15:04.672 --> 00:15:08.617 right. And so that means it's incumbent on you to make sure
00:15:08.617 --> 00:15:12.365 that PR can go through and needing help is totally fine.
00:15:10.370 --> 00:15:10.720 Yeah.
00:15:12.160 --> 00:15:13.780 It it sucks.
00:15:12.365 --> 00:15:14.140 Obviously. Go ahead, Jesse.
00:15:13.800 --> 00:15:15.400 Expected you.
00:15:14.490 --> 00:15:17.782 It it sucks that I set the bit up I it was probably me that set
00:15:17.782 --> 00:15:20.662 the five line up wrong and I made it your problem but I
00:15:20.662 --> 00:15:23.903 don't. I didn't know this. Let me know. Just tell me like just
00:15:22.170 --> 00:15:23.860 No, it's it does. No, it doesn't matter.
00:15:23.903 --> 00:15:26.320 tell me right though cuz I didn't look either.
00:15:25.040 --> 00:15:25.410 Yeah.
00:15:25.280 --> 00:15:25.680 But.
00:15:26.260 --> 00:15:27.370 Yeah, yeah, yeah.
00:15:26.720 --> 00:15:28.850 But yeah, I mean, to Brandon's point.
00:15:29.570 --> 00:15:33.233 This is how many pipelines there are. Member even done opening
00:15:33.233 --> 00:15:36.780 all the folders. Yet there are so many pipelines there is no
00:15:36.780 --> 00:15:40.385 way that we can keep track of every pipe, the status of every
00:15:40.385 --> 00:15:43.990 pipeline all the time. So if you're on a project and you make
00:15:43.990 --> 00:15:47.594 a PR and QA says that you're changes aren't there or whatever
00:15:47.594 --> 00:15:50.734 or somehow or another, you notice that this didn't go
00:15:50.734 --> 00:15:52.420 through before one of us did.
00:15:53.540 --> 00:15:56.623 Please let us know, especially if it's not a build issue of
00:15:56.623 --> 00:15:59.758 your code and it's just the pipeline kind of doing something
00:15:59.758 --> 00:16:01.710 goofy which does happen now and then.
00:16:02.420 --> 00:16:05.931 Umm, let us know. Not everybody's able to edit the
00:16:05.931 --> 00:16:10.198 pipeline just because it would. It's easy to break like every
00:16:10.198 --> 00:16:11.230 single release.
00:16:12.000 --> 00:16:15.169 And there's a lot of pipelines, many there were a lot, but
00:16:15.169 --> 00:16:15.920 there's a lot.
00:16:16.300 --> 00:16:20.302 And and the other and the. The other key point here is and. So
00:16:17.360 --> 00:16:17.930 So.
00:16:20.302 --> 00:16:23.350 pick on, somebody else will do Brent this time.
00:16:24.020 --> 00:16:28.773 Uh, so Brent, if if the code if the code that you wrote the
00:16:28.773 --> 00:16:33.604 problem you solved is not on QA. I mean did you do it? Is it
00:16:33.604 --> 00:16:34.000 done?
00:16:37.100 --> 00:16:38.930 Typically no.
00:16:39.390 --> 00:16:43.580 That's right. If if, if you were ever saying to somebody, what's
00:16:43.580 --> 00:16:46.480 the codes on my local or it's on my machine.
00:16:47.120 --> 00:16:50.763 Umm, I mean, if nobody else has access to it, it's it is
00:16:50.763 --> 00:16:54.534 literally like if a if a tree falls in a forest and nobody
00:16:54.534 --> 00:16:56.770 hears it. Did it make noise right?
00:16:57.450 --> 00:16:57.860 Yeah.
00:16:57.570 --> 00:17:02.341 So it's you're not done with whatever that task is until that
00:17:02.341 --> 00:17:04.110 code is actually on QA.
00:17:04.710 --> 00:17:04.910 Yep.
00:17:06.550 --> 00:17:09.935 All this trouble on these pipelines and stuff lately,
00:17:06.710 --> 00:17:06.920 Yep.
00:17:09.935 --> 00:17:13.193 though. Just another devil devil's advocate type of
00:17:13.193 --> 00:17:16.891 situation. What if we did just just back to, you know, the
00:17:16.891 --> 00:17:17.580 style just.
00:17:18.320 --> 00:17:21.381 You know, maybe maybe you could have a schedule that people go
00:17:21.381 --> 00:17:22.450 in and manually do it.
00:17:22.910 --> 00:17:27.226 I would say that if you tallied up the time we've spent fixing
00:17:27.226 --> 00:17:31.610 the pipelines in the last week, it would be a fraction of if we
00:17:31.610 --> 00:17:32.980 had never done this.
00:17:33.650 --> 00:17:36.661 And you measured it up to the time that would have been spent
00:17:36.661 --> 00:17:38.700 doing deployments in the last six months.
00:17:37.600 --> 00:17:37.890 I.
00:17:39.200 --> 00:17:41.966 I agree, by the way, I agree with that. It just doesn't seem
00:17:41.966 --> 00:17:44.460 that way it it's just one of those, those things that.
00:17:42.820 --> 00:17:46.415 Yeah. So yeah, as many of you have probably noticed, we've had
00:17:46.415 --> 00:17:50.010 something of a comedy of errors with the pipelines in the last
00:17:50.010 --> 00:17:51.550 probably week or two where.
00:17:52.290 --> 00:17:56.756 It feels like there's something breaking with the with the with
00:17:56.756 --> 00:17:58.640 an analyzer or or a like a.
00:17:59.580 --> 00:18:01.630 Plate deployment or something like all the time.
00:18:02.740 --> 00:18:07.308 We've been working through these trying to fix them and it's been
00:18:07.308 --> 00:18:11.875 a bit of a nightmare, but we are we are getting there one step at
00:18:11.875 --> 00:18:14.020 a time. So but all that to say.
00:18:17.920 --> 00:18:20.790 It is, I still.
00:18:22.230 --> 00:18:25.911 Pretty confident that we're saving time in the long run,
00:18:25.911 --> 00:18:29.850 quite a lot of time and also saving frustration because when
00:18:29.850 --> 00:18:30.560 these work.
00:18:31.220 --> 00:18:34.798 QA can just know that ohh a PR is approved and done like I can
00:18:34.798 --> 00:18:38.148 look at this bug. User story linked PR says it's complete.
00:18:38.148 --> 00:18:41.498 That means I'm ready to test this. There's no confusion of
00:18:41.498 --> 00:18:45.132 like. Oh, I hope the developer remembered to go back and deploy
00:18:45.132 --> 00:18:45.870 this or like.
00:18:46.710 --> 00:18:49.673 Uh, you know anything else like that? Like at the end of the
00:18:49.673 --> 00:18:52.732 day, yeah, there's gonna be some frustrations. It's not always
00:18:52.732 --> 00:18:53.800 gonna be perfect, but.
00:18:55.300 --> 00:18:58.215 It will save time and and has saved a lot of time and I and I
00:18:58.215 --> 00:19:01.129 don't know if Christian's in here, but he could probably tell
00:19:01.129 --> 00:19:03.150 you that it's made his job easier as well.
00:19:04.850 --> 00:19:08.395 Yeah, back back in that Stone Age. I know many a project that
00:19:08.395 --> 00:19:11.824 we looked and we're like, ohh. This hasn't been deployed in
00:19:11.824 --> 00:19:12.510 three weeks.
00:19:12.930 --> 00:19:13.560 Yeah.
00:19:14.740 --> 00:19:16.130 So that was definitely a thing.
00:19:15.060 --> 00:19:18.422 Christian and Christians like, well, that's why I'm getting all
00:19:18.422 --> 00:19:19.210 these QA fails.
00:19:20.310 --> 00:19:21.960 Uh, Brent got your hand up?
00:19:23.360 --> 00:19:26.631 Yeah. Is it fair to say that every new project should be put
00:19:26.631 --> 00:19:29.956 on a pipeline or what is like the determining factor for that
00:19:29.650 --> 00:19:33.495 Yes, every. So there's only one specific thing I am aware of
00:19:29.956 --> 00:19:30.170 for?
00:19:33.495 --> 00:19:37.151 that would prevent us from putting putting a project on a
00:19:37.151 --> 00:19:41.122 pipeline. And that is if it's a brand project because we don't
00:19:41.122 --> 00:19:44.841 have a way to deploy those via pipeline right now. So like
00:19:44.841 --> 00:19:46.290 projects that are like.
00:19:47.090 --> 00:19:50.383 Are X1 or what's that other one that's doing brands that's
00:19:50.383 --> 00:19:51.220 somewhat newer?
00:19:51.590 --> 00:19:52.330 See if I wouldn't.
00:19:52.030 --> 00:19:52.970 But GBM.
00:19:52.630 --> 00:19:54.000 Seifer yeah.
00:19:53.150 --> 00:19:55.250 JBM JBM.
00:19:54.950 --> 00:19:58.089 Ohh, in JMS coming in with brands. So yes, so those
00:19:58.089 --> 00:20:01.770 projects unfortunately have to be manual deployments because
00:20:01.770 --> 00:20:05.150 the pipelines are not set up to deploy brand sites yet.
00:20:05.990 --> 00:20:08.530 Because brand site deployments are really complicated.
00:20:09.210 --> 00:20:13.679 So I'm hearing that you're gonna help me out and getting all this
00:20:09.340 --> 00:20:09.790 So.
00:20:13.679 --> 00:20:15.710 custom projects on a pipeline.
00:20:17.010 --> 00:20:18.920 Or custom projects.
00:20:19.090 --> 00:20:19.670 Yeah, yeah.
00:20:23.060 --> 00:20:24.100 Now, that being said.
00:20:23.230 --> 00:20:25.845 I mean KB, you could you could figure it out if you wanted to
00:20:25.845 --> 00:20:27.320 build some pipelines for yourself.
00:20:27.060 --> 00:20:28.560 Yeah, yeah, yeah.
00:20:27.220 --> 00:20:31.239 Yeah, that's what I was. With that being said, if you want, if
00:20:28.980 --> 00:20:30.670 Right. The task group stuff.
00:20:29.690 --> 00:20:29.870 I'm.
00:20:31.239 --> 00:20:35.194 you want those in a pipeline, we've built pipelines for stuff
00:20:32.650 --> 00:20:32.990 Yeah.
00:20:35.194 --> 00:20:37.490 that aren't CEF sites, for example.
00:20:36.130 --> 00:20:37.000 Yeah, yeah.
00:20:36.300 --> 00:20:36.530 Yeah.
00:20:37.590 --> 00:20:39.360 Uh, somewhere here.
00:20:38.340 --> 00:20:41.010 If you go into those task groups, they're they're not.
00:20:41.890 --> 00:20:46.077 Massively complicated. You just kind of do them step by step.
00:20:43.500 --> 00:20:44.400 No, they're really not.
00:20:46.077 --> 00:20:50.128 You get the command line right there it right inside you of
00:20:46.110 --> 00:20:46.320 Yeah.
00:20:49.750 --> 00:20:50.020 You.
00:20:49.750 --> 00:20:52.990 Brendan, are you telling me that Azure pipelines weren't built
00:20:50.128 --> 00:20:50.600 course.
00:20:52.990 --> 00:20:54.070 exclusively for Seth?
00:20:55.230 --> 00:20:56.270 Believe it or not.
00:20:55.910 --> 00:20:57.200 Seems that way.
00:20:57.110 --> 00:20:59.740 We asked them and they said what?
00:21:02.780 --> 00:21:05.939 They actually said they are built specifically to not work
00:21:05.939 --> 00:21:09.150 with Seth. That's they. They said that it was really weird.
00:21:06.830 --> 00:21:11.253 Yeah, it feels that way. Yeah, it was really mean. Kind of felt
00:21:06.870 --> 00:21:08.540 Yeah.
00:21:11.253 --> 00:21:12.980 singled out a little bit.
00:21:13.630 --> 00:21:15.480 Uh anyway.
00:21:14.690 --> 00:21:17.569 So in in in having this conversation, I'm wondering if
00:21:17.569 --> 00:21:21.022 we need a channel or or we could use the development channel, but
00:21:21.022 --> 00:21:24.005 I'm wondering if it would make sense to have a pipelines
00:21:24.005 --> 00:21:27.250 channel specifically to be able to report any issues. What do
00:21:27.250 --> 00:21:28.610 you guys think about that?
00:21:27.750 --> 00:21:29.620 And then, yeah, let me.
00:21:28.350 --> 00:21:28.690 Yeah.
00:21:29.250 --> 00:21:29.940 I think so.
00:21:29.380 --> 00:21:29.700 Yeah.
00:21:29.580 --> 00:21:32.562 Or or if you're a developer that knows that you're on a new
00:21:32.562 --> 00:21:35.792 project and you go and look and there's no branch and there's no
00:21:35.792 --> 00:21:38.674 pipeline stuff to put in a request and say, hey, I need a
00:21:38.674 --> 00:21:39.320 pipeline for.
00:21:40.350 --> 00:21:43.291 So and so project or I need branches in a pipeline for
00:21:43.291 --> 00:21:44.200 whatever project?
00:21:44.990 --> 00:21:45.250 Yeah.
00:21:45.880 --> 00:21:48.970 Then we can service those requests in one place.
00:21:46.020 --> 00:21:46.300 And.
00:21:49.780 --> 00:21:52.999 How many people have the ability to make pipelines? Or is there
00:21:52.999 --> 00:21:56.218 maybe a list we could make for that? Or so we know who to reach
00:21:53.450 --> 00:21:54.700 It's.
00:21:55.410 --> 00:21:58.381 So I well I if we put it in that Channel then it would just be
00:21:56.218 --> 00:21:56.570 out to?
00:21:58.381 --> 00:22:01.352 the people that can would would need to kind of keep an eye on
00:22:01.352 --> 00:22:03.380 it. But I know the off the top of my head.
00:22:04.750 --> 00:22:09.788 James me and Jesse. I believe Brandon and Eric and team, OK
00:22:09.788 --> 00:22:11.970 and there might be others.
00:22:13.770 --> 00:22:16.625 Uh, right now. Right now I believe that's it. Basically
00:22:13.890 --> 00:22:14.450 But I think.
00:22:16.625 --> 00:22:19.837 there's there's a lot that could go wrong with just getting in
00:22:19.837 --> 00:22:23.099 there and messing with stuff. So we don't, we're not gonna open
00:22:23.099 --> 00:22:25.240 that permissions to everyone immediately.
00:22:25.320 --> 00:22:29.197 Uh, so we'll, we, we'll probably come up with some sort of
00:22:29.197 --> 00:22:33.075 certification for that for anybody that wants to get on. I
00:22:33.075 --> 00:22:37.017 do know that we're wanting to add one or two more people as
00:22:37.017 --> 00:22:41.157 kind of the team grows. So if you want to be involved in that,
00:22:40.040 --> 00:22:40.410 Yeah.
00:22:41.157 --> 00:22:45.166 definitely, definitely message myself and Brandon and we can
00:22:45.166 --> 00:22:46.480 get that worked out.
00:22:49.830 --> 00:22:50.160 On it.
00:22:49.830 --> 00:22:50.220 Cool.
00:22:50.710 --> 00:22:51.770 We'll figure out a certificate.
00:22:50.880 --> 00:22:51.140 On.
00:22:52.870 --> 00:22:53.440 Yeah.
00:22:54.980 --> 00:22:59.180 Yeah. And like like Eric said, to his point, there's a lot of
00:22:59.180 --> 00:23:03.313 things that can break in here and it's also classic Azure in
00:23:03.313 --> 00:23:03.990 that it's.
00:23:05.220 --> 00:23:08.030 Like annoying something like, annoyingly.
00:23:08.860 --> 00:23:11.863 Alright, so here's a great example. The pipeline screen
00:23:11.863 --> 00:23:15.241 looks like this and there's an all tab and look, here's all my
00:23:15.241 --> 00:23:18.726 pipelines. The release is screen looks like this. There's no all
00:23:18.726 --> 00:23:21.943 tab here, just deployments and analytics. The All button is
00:23:21.943 --> 00:23:23.390 this tiny unlabeled folder.
00:23:24.500 --> 00:23:28.335 Thank you Azure. I consistency is not like and that's like just
00:23:25.500 --> 00:23:26.440 It is very.
00:23:28.335 --> 00:23:31.931 a small example of like it's like, OK, it's not really that
00:23:31.931 --> 00:23:35.646 big of a deal, but imagine that times 1000 because stuff like
00:23:35.646 --> 00:23:39.301 that is on every single page throughout the pipeline editing
00:23:39.301 --> 00:23:42.597 stuff. It's annoying and unintuitive and especially if
00:23:42.597 --> 00:23:46.072 you don't know what you're doing, it's very easy to go to
00:23:46.072 --> 00:23:49.548 the wrong place and break something. It's easy to do that
00:23:49.548 --> 00:23:53.443 when you know what you're doing. I've broken more than one thing
00:23:53.443 --> 00:23:55.120 screwing around in here, so.
00:23:55.580 --> 00:23:57.910 You can tell they were different teams that that made them.
00:23:58.480 --> 00:23:59.440 Yeah, exactly.
00:23:59.970 --> 00:24:02.350 They probably were different teams that made those things.
00:24:01.820 --> 00:24:02.190 Yeah.
00:24:03.110 --> 00:24:04.550 So. Umm.
00:24:04.040 --> 00:24:07.186 Wait, are you telling me the different developers will just
00:24:07.186 --> 00:24:09.650 make something different for no reason at all?
00:24:09.310 --> 00:24:11.260 For no reason to it's such crap.
00:24:10.720 --> 00:24:14.640 Absolutely. Yeah. I don't know who would who would do that.
00:24:12.950 --> 00:24:14.910 Crazy. Crazy.
00:24:16.320 --> 00:24:16.710 Easy.
00:24:16.720 --> 00:24:17.840 Why would anyone?
00:24:18.630 --> 00:24:19.880 Wanna do it their own way?
00:24:21.390 --> 00:24:23.080 Anyway so.
00:24:25.180 --> 00:24:28.631 I'll just keep kind of going on this, so hey, cool. We got one
00:24:28.631 --> 00:24:30.000 that's cooking right now.
00:24:31.020 --> 00:24:34.515 UM, Mr Mr Jesse manually triggered this one. So that's
00:24:34.515 --> 00:24:38.581 actually that's, you know what? Perfect? That actually reminded
00:24:35.480 --> 00:24:36.180 My dad.
00:24:38.581 --> 00:24:42.583 me that I wanted to talk about this. So whenever a branch gets
00:24:42.583 --> 00:24:46.586 updated, assuming the pipeline is set up correctly, it will be
00:24:46.586 --> 00:24:50.652 built set up so that the release for that branch runs out. Or I
00:24:50.652 --> 00:24:54.464 should say, the pipeline for that branch runs automatically
00:24:54.464 --> 00:24:58.594 to deploy the site. However, if there's a situation where, like,
00:24:58.594 --> 00:25:01.770 we were saying earlier, there's a pipeline issue.
00:25:01.850 --> 00:25:05.389 Or like this Acme one, where it's like, uh, the branch name
00:25:05.389 --> 00:25:08.986 wrong. Well, once that gets fixed by somebody or even before
00:25:08.986 --> 00:25:12.466 it does, this is just a good troubleshooting step. You can
00:25:12.466 --> 00:25:15.886 manually run the pipeline and I don't even think you need
00:25:15.886 --> 00:25:17.950 permissions to be able to do this.
00:25:18.690 --> 00:25:22.822 Umm I I'm pretty sure that if you just click pipelines and go
00:25:22.822 --> 00:25:25.820 find the one that like, let's say it's Acme.
00:25:27.080 --> 00:25:30.584 You can just click the three dot way over here and just hit run
00:25:30.584 --> 00:25:34.142 pipeline and it'll ask you some stuff. Just leave it all default
00:25:34.142 --> 00:25:37.590 and hit run. That will manually queue this pipeline to run and
00:25:37.590 --> 00:25:41.148 when it does it will deploy the site and everything, assuming it
00:25:41.148 --> 00:25:42.790 passes and doesn't fail again.
00:25:43.950 --> 00:25:47.090 Always a good troubleshooting step. Occasionally the build
00:25:47.090 --> 00:25:48.260 machines have hiccups.
00:25:49.000 --> 00:25:52.508 Uh, and so this might be kind of the first thing you do before
00:25:52.508 --> 00:25:55.960 you post in the pipeline group is like manually retrigger it,
00:25:55.960 --> 00:25:59.412 see if it goes through. If it does, fantastic. If it doesn't,
00:25:59.412 --> 00:26:02.642 then you've knocked that troubleshooting step out and you
00:26:02.642 --> 00:26:06.038 and say, hey, I already tried
00:26:06.038 --> 00:26:09.602 manually retriggering this, but the error I'm seeing looks like
00:26:09.602 --> 00:26:09.880 this.
00:26:10.480 --> 00:26:13.106 And you can just come in here and screenshot your error
00:26:13.106 --> 00:26:15.310 message and dump it in there and then ideally.
00:26:16.010 --> 00:26:19.554 Uh, link your PR that has the failing pipeline or the pipeline
00:26:19.554 --> 00:26:23.154 that's having the issue, which you can get to that again like I
00:26:23.154 --> 00:26:26.530 said, by going to the most recent run and then you can just
00:26:26.530 --> 00:26:30.017 copy the link and paste it on there and just say hey, this is
00:26:30.017 --> 00:26:33.280 the output of this pipeline, I'm not really sure why it's
00:26:33.280 --> 00:26:36.880 failing. I tried to retrigger it and it didn't. It still failed
00:26:36.880 --> 00:26:37.780 the second time.
00:26:38.040 --> 00:26:41.584 Umm that way. That way we at least know that you you tried
00:26:41.584 --> 00:26:45.129 the basic troubleshooting steps as far as what's available
00:26:45.129 --> 00:26:46.570 without having to start.
00:26:47.460 --> 00:26:49.080 Pulling wires out of it and stuff.
00:26:49.500 --> 00:26:53.359 Umm. And and we can just start it, start at the assumption that
00:26:53.359 --> 00:26:55.590 there really do be something broken.
00:26:57.880 --> 00:26:58.340 So.
00:27:00.030 --> 00:27:04.648 Umm releases is the other half of pipelines. So the way that we
00:27:04.648 --> 00:27:09.338 have it set up right now is that whenever a branch is updated, a
00:27:09.338 --> 00:27:13.812 pipeline will be triggered. All that this pipeline does is it
00:27:13.812 --> 00:27:18.213 pulls the code and builds the front end and back end. So you
00:27:18.213 --> 00:27:22.759 have a blob of working website data just sitting in the ether.
00:27:22.759 --> 00:27:27.232 Cool. Not very useful without the release part of it and what
00:27:27.232 --> 00:27:30.190 the release does is whenever a pipeline.
00:27:30.480 --> 00:27:33.763 Completes and publishes what's
00:27:33.763 --> 00:27:36.020 blob of working website data and the ether.
00:27:36.780 --> 00:27:40.539 The release gets triggered to actually publish those files to
00:27:40.539 --> 00:27:44.176 your QA site or your staging site or wherever it is, and so
00:27:44.176 --> 00:27:45.630 you'll see, for example.
00:27:46.320 --> 00:27:49.668 Uh, we try to have them set up with consistent names of like,
00:27:49.668 --> 00:27:50.100 version.
00:27:50.780 --> 00:27:54.850 Uh, acronym Environment on and then whatever box they're on.
00:27:57.140 --> 00:27:57.590 So.
00:27:59.200 --> 00:28:03.011 These these releases will be the second half of the of the
00:28:03.011 --> 00:28:07.274 equation, so to speak, where the pipeline builds the site and the
00:28:07.274 --> 00:28:10.891 release goes and actually updates the files that are on
00:28:10.891 --> 00:28:14.831 CEF dev, one or whatever box. And so if you're seeing issues
00:28:14.831 --> 00:28:19.094 where like your site is down and it's not just like the app pools
00:28:19.094 --> 00:28:23.099 are off or something and you've looked into it as much as you
00:28:23.099 --> 00:28:26.586 looks like the pipeline
00:28:26.586 --> 00:28:28.330 succeeded last time it ran.
00:28:28.810 --> 00:28:31.030 You can look at the release history and see.
00:28:31.680 --> 00:28:35.170 That, and again this tiny folder icon.
00:28:36.520 --> 00:28:39.406 Let's say that you're looking at Acme and let's there's not even
00:28:39.406 --> 00:28:40.560 a release here. I'm gonna.
00:28:41.440 --> 00:28:44.603 Pretend I didn't see that. Let's say you're looking at uh, I
00:28:44.603 --> 00:28:45.380 don't know bid.
00:28:46.240 --> 00:28:49.940 And you click on this and and pretend that this is an error
00:28:49.940 --> 00:28:53.393 and just say. Ohh OK, so the pipeline succeeded but the
00:28:53.393 --> 00:28:57.462 release failed and you can click on the little progress bar there
00:28:57.462 --> 00:29:00.360 and same deal. You can see all the outputs so.
00:29:02.440 --> 00:29:06.481 Maybe it failed to stop the app pool, so this step has an error,
00:29:06.481 --> 00:29:10.149 or maybe you know it failed to restart the app pools or it
00:29:10.149 --> 00:29:13.878 failed to move the files down or something. Whatever it is,
00:29:13.878 --> 00:29:17.670 again, this may be the kind of thing where you just have to.
00:29:20.230 --> 00:29:23.688 You know, posting like the pipeline team or whatever and
00:29:23.688 --> 00:29:27.692 just say, hey, something's wrong with this release, but if you're
00:29:27.692 --> 00:29:31.574 lucky, you might click on one of these and see an error message
00:29:31.574 --> 00:29:35.456 that is actually useful to you. And it might tell you that, oh,
00:29:35.456 --> 00:29:39.338 this is just like an environment thing that I can go and fix on
00:29:39.338 --> 00:29:40.430 sev one right now.
00:29:41.070 --> 00:29:45.166 Umm. And you know what we've seen in the past for for an
00:29:45.166 --> 00:29:49.549 example of stuff like that is somebody accidentally used the
00:29:49.549 --> 00:29:49.980 wrong.
00:29:51.650 --> 00:29:56.118 App Pool for a different site when they were standing up like
00:29:56.118 --> 00:30:00.585 an extra site on Sept one and they used bids app pool for DNN
00:30:00.585 --> 00:30:04.764 or API storefront for this other one on accident and then
00:30:04.764 --> 00:30:05.700 whenever the.
00:30:06.640 --> 00:30:09.537 Whenever it tries to stop the app pool, it fails because
00:30:09.537 --> 00:30:12.688 there's another site running or something's using this site's
00:30:12.688 --> 00:30:15.890 files, and then when it tries to copy these over, you'll get a
00:30:15.890 --> 00:30:18.838 bunch of errors in here about not being able to overwrite
00:30:18.838 --> 00:30:21.836 files, and so if you see errors that seemed like it may be
00:30:21.836 --> 00:30:25.038 indicating that that's the kind of stuff that hopefully if the
00:30:25.038 --> 00:30:28.240 error message is good enough to actually lead you to that, you
00:30:28.240 --> 00:30:29.510
00:30:29.600 --> 00:30:29.910 The.
00:30:31.090 --> 00:30:33.710 Fix that yourself. Just figure out whatever that weird
00:30:33.710 --> 00:30:36.712 configuration is and get that fixed. If you're not comfortable
00:30:36.712 --> 00:30:39.427 doing that, or the error messages are vague as they tend
00:30:39.427 --> 00:30:42.380 to be, then please ask for help. It's better to ask for help.
00:30:43.900 --> 00:30:47.375 And you know, and it'd be something that was like a quick
00:30:47.375 --> 00:30:50.370 fix then to accidentally break something or just.
00:30:51.240 --> 00:30:53.110 Spend more time trying to fix yourself when.
00:30:53.720 --> 00:30:55.160 When it's not necessary so.
00:30:55.670 --> 00:30:59.385 Yeah. And I just, I just wanna emphasize there like if if
00:30:59.385 --> 00:31:03.355 that's something that you wanna get in or you wanna, you know
00:31:03.355 --> 00:31:07.006 spend a little bit of time trying to fix, you're totally
00:31:07.006 --> 00:31:10.912 welcome to do that. The the thing I want to emphasize though
00:31:10.912 --> 00:31:14.819 is the minimum, I guess sort of the MVP, if you will of this
00:31:14.819 --> 00:31:18.726 situation is that you send a screenshot to this channel that
00:31:18.726 --> 00:31:22.696 will form and we'll get out to everyone that there's an error
00:31:22.696 --> 00:31:25.770 preferably the same day that you submit the PR.
00:31:25.850 --> 00:31:28.486 Unless you know if you submit the PR at the end of the day,
00:31:28.486 --> 00:31:31.209 then you know the the the next day in the morning or whatever
00:31:31.209 --> 00:31:31.560 is fine.
00:31:32.010 --> 00:31:35.300 Umm, but that would be the MVP of this situation.
00:31:39.920 --> 00:31:40.810 Mm-hmm.
00:31:45.860 --> 00:31:46.700 Umm.
00:31:49.010 --> 00:31:52.894 Cool. I can't think of anything else to talk about, so does
00:31:52.894 --> 00:31:57.037 anybody have any questions about pipelines, questions about why
00:31:57.037 --> 00:32:00.727 we use them? Does anybody, anybody who knows stuff about
00:32:00.727 --> 00:32:04.806 them or any? I guess it really did. Does anybody have anything
00:32:04.806 --> 00:32:08.819 they want me to talk about so I could go into task groups and
00:32:08.819 --> 00:32:11.020 stuff with that seems a lot more.
00:32:12.110 --> 00:32:14.714 Nitty gritty than is necessary for just going over like
00:32:14.714 --> 00:32:16.480 troubleshooting the day to day stuff.
00:32:21.790 --> 00:32:24.608 Does anybody, anybody interested in seeing that since we have
00:32:24.608 --> 00:32:26.380 some time and we're in here right now?
00:32:26.520 --> 00:32:26.760 Yeah.
00:32:27.420 --> 00:32:29.120 Yes, show us.
00:32:29.560 --> 00:32:30.430 It's absolutely.
00:32:29.860 --> 00:32:30.220 Cool.
00:32:30.880 --> 00:32:34.970 Alright, so let's go look at how pipelines are actually made.
00:32:31.080 --> 00:32:31.560 Yeah.
00:32:35.740 --> 00:32:39.880 When a mommy pipeline and a daddy pipeline. Just kidding.
00:32:41.760 --> 00:32:44.170 So let's go look at one that's broken, because that'll be fun.
00:32:44.790 --> 00:32:50.592 Umm, so this right here is the pipeline that deploys our
00:32:50.592 --> 00:32:53.340 our2022-2.claritydemos.com.
00:32:54.370 --> 00:32:58.022 So if we click on the three dot, you can hit edit. Is there a
00:32:58.022 --> 00:33:01.320 name for this hamburger menu? No, it's not that, right?
00:33:02.520 --> 00:33:03.270 What they call these?
00:33:03.800 --> 00:33:04.550 The dots.
00:33:05.000 --> 00:33:06.150 Dots. Got it.
00:33:05.460 --> 00:33:07.800 Meatballs. I personally call meat.
00:33:06.780 --> 00:33:07.570 Three time, yeah.
00:33:08.160 --> 00:33:11.410 Ooh, I like meatball. That's good. I'm kind of hungry. OK.
00:33:08.830 --> 00:33:09.110 Yeah.
00:33:10.840 --> 00:33:11.170 Yeah.
00:33:12.940 --> 00:33:19.631 So pipelines are made up of tasks, and specifically we can
00:33:19.631 --> 00:33:22.920 group tasks into task groups.
00:33:23.640 --> 00:33:24.370 Aptly named.
00:33:24.790 --> 00:33:28.460 Umm. And that's good for you know, the fact that every pretty
00:33:28.460 --> 00:33:31.953 much every CEF site running on the same version of self is
00:33:31.953 --> 00:33:35.741 going to have the same steps to deploy the site. So it helps us
00:33:35.741 --> 00:33:39.352 from keeps us from having to go and repeat make all the same
00:33:39.352 --> 00:33:40.180 steps of like.
00:33:41.010 --> 00:33:44.648 Pull down the code NPM install in this folder. Gulp build over
00:33:44.648 --> 00:33:48.285 here. Do this other thing. All of that is contained inside the
00:33:48.285 --> 00:33:48.920 task group.
00:33:49.530 --> 00:33:51.852 And so if we right click on this, we can do manage task
00:33:51.852 --> 00:33:52.100 group.
00:33:52.840 --> 00:33:57.343 And there you go. Here's all the steps for creating a CEF
00:33:57.343 --> 00:33:59.050 artifact for 2022 two.
00:33:59.700 --> 00:34:03.483 So you started from the top, it pulls the latest from the boxes
00:34:03.483 --> 00:34:06.260 CEF config which is always at sea CEF configs.
00:34:07.400 --> 00:34:10.483 Create some folders that are required for the build to go
00:34:10.483 --> 00:34:13.513 through copies in the config switch is to in VMS or Node
00:34:13.513 --> 00:34:17.022 16.9. Does the react build stuff which is back to the old version
00:34:17.022 --> 00:34:20.211 of node does the front end build stuff builds the back end,
00:34:20.211 --> 00:34:23.400 copies all the files into a zip and publishes the artifact.
00:34:24.100 --> 00:34:26.985 Umm, this is one of the places that a lot of changes and and
00:34:26.985 --> 00:34:29.964 and tweaks and adjustments have been happening lately as we've
00:34:29.964 --> 00:34:33.038 been trying to work through some of those issues we were talking
00:34:33.038 --> 00:34:33.700 about earlier.
00:34:34.990 --> 00:34:35.480 But.
00:34:37.540 --> 00:34:41.641 That's yeah, basically. Task groups allow us to consolidate a
00:34:41.641 --> 00:34:45.809 bunch of common stuff, and as you can see, the tasks are basic
00:34:45.809 --> 00:34:50.175 stuff like running commands from the command line and in specific
00:34:50.175 --> 00:34:54.408 folders. So CEF configs run, Git pull, or run NPM run this long
00:34:54.408 --> 00:34:58.311 command, which is just basically NPM install but with some
00:34:58.311 --> 00:35:02.610 debugging stuff on the beginning and run it in the React folder.
00:35:03.180 --> 00:35:08.322 Umm. And so on and so forth. Copy files to from this folder
00:35:08.322 --> 00:35:09.350 to this one.
00:35:09.930 --> 00:35:13.586 Umm, some of them are a little bit more complicated like this
00:35:13.586 --> 00:35:16.710 nugget tool installer and building the solution and.
00:35:17.890 --> 00:35:21.240 Uh, nugget restore and all that kind of stuff, but.
00:35:22.290 --> 00:35:26.163 Interestingly enough, a lot of these uh task groups are are
00:35:26.163 --> 00:35:29.390 what I used as guides to build out the installer.
00:35:31.200 --> 00:35:34.709 Because meaning installer is doing basically the same thing
00:35:34.709 --> 00:35:38.100 that these are give or take some extra setup with IIS and
00:35:38.100 --> 00:35:41.433 databases, but the actual building of the site is almost
00:35:41.433 --> 00:35:43.070 one for one. What this does?
00:35:45.410 --> 00:35:47.020 Umm on the pipeline so.
00:35:47.670 --> 00:35:51.903 Pretty cool. Just kind of a neat aside, but anyway. So on the so
00:35:51.903 --> 00:35:55.941 that's task group, we can just real quick look, there's a ton
00:35:55.941 --> 00:36:00.174 of custom task groups we have in here for creating and deploying
00:36:00.174 --> 00:36:04.017 stuff artifacts for every version of CEF from 2018 to now.
00:36:04.017 --> 00:36:08.054 And then all the pull request analyzers for all the different
00:36:08.054 --> 00:36:08.640 versions.
00:36:09.560 --> 00:36:14.525 Umm, even further actually than 2018. We've got a 4.7 back when
00:36:14.525 --> 00:36:17.240 CEF wasn't even versioned by year.
00:36:18.500 --> 00:36:19.560 So that's a.
00:36:20.420 --> 00:36:21.570 That's a long time ago.
00:36:22.380 --> 00:36:26.132 Believe we stopped doing that and 2000 was at 17, I think,
00:36:26.132 --> 00:36:30.201 year that we had for like year
00:36:30.201 --> 00:36:31.600 versions, pretty cool.
00:36:33.320 --> 00:36:36.800 There is still some 4.7. It's not gonna around in 2019.
00:36:36.800 --> 00:36:38.990 I remember clarity back in 2018.
00:36:39.720 --> 00:36:41.630 Is it office?
00:36:41.820 --> 00:36:43.670 Pepperidge Farm remembers.
00:36:43.300 --> 00:36:44.540 If it's fine, remembers.
00:36:45.830 --> 00:36:46.540 That's awesome.
00:36:48.400 --> 00:36:51.478 Alright, so so that's our task groups. They all look pretty
00:36:51.478 --> 00:36:54.248 similar. The deploy ones are gonna be doing something
00:36:54.248 --> 00:36:57.530 different than the create ones, which is that they're gonna be.
00:36:58.500 --> 00:37:02.259 Uh, they download the artifact. Like I said, the blob of working
00:37:02.259 --> 00:37:05.671 site data and the ether it downloads the file, extracts it
00:37:05.671 --> 00:37:09.314 into the place, stops your app, pools it, does some additional
00:37:09.314 --> 00:37:12.090 cool stuff, copying out translations as needed.
00:37:12.610 --> 00:37:16.722 Uh, it deletes all your files that are on the site right now,
00:37:16.722 --> 00:37:20.834 so cleans out the old stuff, copies in the new stuff, deletes
00:37:20.834 --> 00:37:25.012 the artifact that downloaded to save disk space, pulls back in
00:37:25.012 --> 00:37:28.991 the correct site configs, and fires up the app pools again.
00:37:28.991 --> 00:37:29.190 So.
00:37:31.760 --> 00:37:35.441 That is the process for deploying. So yeah. Anyway, so I
00:37:35.441 --> 00:37:39.509 guess the next part of this is the task groups are used inside
00:37:39.509 --> 00:37:42.350 the pipeline. So we'll go and look back at.
00:37:43.600 --> 00:37:44.490 This little guy.
00:37:46.670 --> 00:37:50.533 Like I said, this is what deploys or this is what creates
00:37:50.533 --> 00:37:53.530 this F artifact for the release 2022.2 site.
00:37:55.450 --> 00:37:58.571 It allows you to select a few different options here. So on
00:37:58.571 --> 00:38:01.952 the base level of the pipeline, one of the things you can choose
00:38:01.952 --> 00:38:02.680 is agent pool.
00:38:04.240 --> 00:38:07.430 This for analyzers and for.
00:38:09.400 --> 00:38:12.540 Create CEF artifact stuff. This should always be default.
00:38:13.800 --> 00:38:18.259 The default pool for us is our build machines, so the default
00:38:18.259 --> 00:38:22.213 agent pool contains all of our all twenty of our build
00:38:22.213 --> 00:38:26.456 machines, and they're all running the Azure agent that can
00:38:26.456 --> 00:38:29.260 accept the pipelines and do the thing.
00:38:29.990 --> 00:38:33.040 Umm. And so pretty straightforward.
00:38:34.440 --> 00:38:37.975 The get sources. This is the one that, uh for all the client
00:38:37.975 --> 00:38:41.741 projects is gonna be, you know, for this release. Obviously it's
00:38:41.741 --> 00:38:45.275 the release branch, but for other client projects it's gonna
00:38:45.275 --> 00:38:48.983 be your client project support clients, athlete, Q or cheque or
00:38:48.983 --> 00:38:51.590 whatever project it is, it's gonna be using.
00:38:52.760 --> 00:38:53.490 That branch.
00:38:55.260 --> 00:38:56.850 These also have phases.
00:38:57.780 --> 00:39:01.260 To my knowledge, I don't think we have any pipelines that are
00:39:01.260 --> 00:39:04.796 more than one phase, but we have the ability to add additional
00:39:04.796 --> 00:39:08.388 phases so that after every task in this group has run, it'll do
00:39:08.388 --> 00:39:09.230 the next phase.
00:39:09.830 --> 00:39:10.530 Umm.
00:39:11.220 --> 00:39:14.317 Again, you can change the agent pool that these execute on. No
00:39:14.317 --> 00:39:17.070 reason for us to do that. So we just tell it to run on.
00:39:18.640 --> 00:39:22.829 And on the same as the inherits from the pipeline itself, which
00:39:22.829 --> 00:39:26.690 is default underneath the phases. That's where you can add
00:39:26.690 --> 00:39:30.879 tasks or task groups. So we've got just the one task group that
00:39:30.879 --> 00:39:35.067 we use for our creating ourself artifacts, and on these you can
00:39:35.067 --> 00:39:38.667 actually specify all the different settings for it. So
00:39:38.667 --> 00:39:42.790 let's see the artifact for it. The path for the admin template
00:39:42.790 --> 00:39:46.455 roots, the path for the storefront, template roots, the
00:39:46.455 --> 00:39:47.240 skin to use.
00:39:47.990 --> 00:39:48.650 Umm.
00:39:49.810 --> 00:39:52.213 Pretty much all the rest of this is usually defaults, mostly gulp
00:39:52.213 --> 00:39:53.560 settings for building the front end.
00:39:54.360 --> 00:39:54.860 Uh.
00:39:56.630 --> 00:39:57.020 So.
00:39:56.730 --> 00:39:57.100 Have a.
00:39:57.750 --> 00:39:58.200 Yeah, that's.
00:39:58.910 --> 00:40:02.945 So when you run into troubleshooting issues, what's
00:40:02.945 --> 00:40:07.523 the number one site that gives you the best information to
00:40:07.523 --> 00:40:09.540 crawl to fix those issues?
00:40:10.770 --> 00:40:13.500 Uh James Gray's brain.com.
00:40:11.720 --> 00:40:12.420 Microsoft.
00:40:15.320 --> 00:40:16.290 But also.
00:40:17.400 --> 00:40:18.100 Salsa.
00:40:18.330 --> 00:40:21.620 Microsoft documentation is OK for the pipeline stuff.
00:40:23.330 --> 00:40:27.060 But generally speaking, when there's pipeline issues, it's
00:40:27.060 --> 00:40:30.917 usually configuration error on our side. It's like something
00:40:30.917 --> 00:40:34.647 wrong with the task groups themselves. I don't think we've
00:40:34.647 --> 00:40:36.670 ever had something happen where.
00:40:37.640 --> 00:40:39.690 The pipeline just flat out.
00:40:40.540 --> 00:40:44.102 Broke or didn't work, and it wasn't our fault. Like it wasn't
00:40:44.102 --> 00:40:46.170 something of ours that broke it so.
00:40:47.590 --> 00:40:51.150 And on top of that, most of what we're doing with the pipelines
00:40:51.150 --> 00:40:54.099 is pretty much the same for every project. We've got
00:40:54.099 --> 00:40:57.492 analyzers for the PR's, we've got a thing that publishes the
00:40:57.492 --> 00:41:00.997 CEF artifact and the thing that deploys the CEF artifact, it's
00:41:00.997 --> 00:41:04.334 all that's already built out. We don't typically have to go
00:41:04.334 --> 00:41:07.227 digging through the documentation too much, and any
00:41:07.227 --> 00:41:10.453 issues that do come up are either like a site environment
00:41:10.453 --> 00:41:13.791 or somebody configured the pipeline wrong and will just fix
00:41:13.791 --> 00:41:14.180 it. So.
00:41:14.880 --> 00:41:17.610 Uh, but I have found with some of the more.
00:41:18.780 --> 00:41:22.310 Like Edge Casey stuff, Microsoft documentation does not too bad.
00:41:24.760 --> 00:41:29.680 And other than that, just stack overflows. Good as always.
00:41:30.330 --> 00:41:30.570 Right.
00:41:31.260 --> 00:41:35.379 Uh Michael has his hand up. I don't know if he's looking to
00:41:35.379 --> 00:41:36.340 say something.
00:41:35.950 --> 00:41:36.450 What's up?
00:41:38.630 --> 00:41:40.130 I did not know my hands up.
00:41:40.780 --> 00:41:41.440 Ohh never mind.
00:41:42.430 --> 00:41:42.910 All right.
00:41:44.370 --> 00:41:45.640 Well, that was an easy question.
00:41:47.840 --> 00:41:48.420 All right.
00:41:49.420 --> 00:41:50.990 Onward so.
00:41:52.820 --> 00:41:56.543 Yeah. So yeah, this lets you customize some options about the
00:41:56.543 --> 00:42:00.506 the way that the task group gets executed so task groups can have
00:42:00.506 --> 00:42:04.109 options that you inject into each of their tasks. Not gonna
00:42:04.109 --> 00:42:06.390 lie, I don't remember how that works.
00:42:08.420 --> 00:42:11.710 Let's see if we can find out real quick. Ah, right here.
00:42:11.710 --> 00:42:13.960 Parameters. Cool. So you do all these?
00:42:15.820 --> 00:42:18.765 And I assume that the names are injected in other places, so we
00:42:18.765 --> 00:42:21.250 setup somewhere in here.
00:42:22.290 --> 00:42:24.170 Where the Hells the gulp set up?
00:42:23.360 --> 00:42:25.330 It's, uh, it's it's.
00:42:26.760 --> 00:42:28.620 Oh, it's perhaps skin gold config dot.
00:42:28.440 --> 00:42:29.600 That's it, alright.
00:42:29.440 --> 00:42:30.010 Umm.
00:42:30.400 --> 00:42:33.970 Percents is how you make those. If you type in some some task
00:42:33.970 --> 00:42:37.310 that has like a percent, whatever percent, that's how you
00:42:37.310 --> 00:42:40.765 make it back on that previous step. He was just on actually
00:42:40.765 --> 00:42:42.780 have an input for it, so stick it.
00:42:41.260 --> 00:42:44.678 Yeah, you're right. You're right. And then you can set your
00:42:44.678 --> 00:42:48.210 default values and descriptions for those values right there.
00:42:47.150 --> 00:42:50.839 Which is crazy. I feel like you should have an ad button on
00:42:50.630 --> 00:42:51.860 Absolutely right.
00:42:50.839 --> 00:42:54.711 here, right? It's extremely that took forever for me to figure
00:42:54.590 --> 00:42:57.405 Yeah, I remember it being complicated, which is why I was.
00:42:54.711 --> 00:42:57.170 that out just by trial and error. Yeah.
00:42:57.405 --> 00:43:00.362 That's why when I said I looked, I was like, I honestly don't
00:43:00.362 --> 00:43:02.890 remember how this works, but so that's how works. It
00:43:02.890 --> 00:43:05.990 automatically adds them to this list based on your tasks having.
00:43:06.930 --> 00:43:10.290 Percent whatever percent in them like right here.
00:43:10.770 --> 00:43:14.180 Patrick asked if they work for DNN as well, and I don't think
00:43:14.180 --> 00:43:17.700 we've ever built DNN, but there are definitely some DNN release
00:43:17.700 --> 00:43:21.110 ones. Yeah, they're not widely used, but they would go in and
00:43:18.180 --> 00:43:19.420 Yes. Yeah, so.
00:43:21.110 --> 00:43:24.190 like add extra skin files or whatever, I mean and stuff
00:43:24.190 --> 00:43:27.710 whatever's in the like our DNN git. But I I don't think they're
00:43:27.710 --> 00:43:30.020 widely used, and I don't know if I would.
00:43:30.590 --> 00:43:34.258 Yeah, for most client sites, generally speaking, we don't
00:43:31.280 --> 00:43:31.660 Trust.
00:43:34.258 --> 00:43:34.700 bother.
00:43:36.400 --> 00:43:41.172 But it is absolutely possible to deploy uh DNN via the pipelines
00:43:41.172 --> 00:43:45.870 and stuff. Yeah, we usually we do that for a lot of the release
00:43:45.870 --> 00:43:46.310 sites.
00:43:47.500 --> 00:43:51.182 Umm, I did not do that for the release 2022.2 site, which is
00:43:51.182 --> 00:43:55.106 the only release site I've stood up, but again totally possible.
00:43:54.420 --> 00:43:54.800 Either.
00:43:55.106 --> 00:43:55.830 Very doable.
00:43:56.490 --> 00:43:59.441 I actually haven't tried it sometime, but does does the
00:43:59.441 --> 00:44:02.445 actual DNN branch we use for Seth. I mean if you were to
00:44:02.445 --> 00:44:05.871 delete everything in it and then just you know pull it from from
00:44:05.871 --> 00:44:08.400 our Git branch, does it, does it actually work?
00:44:09.460 --> 00:44:12.860 Because it at one point it didn't. I I think. And then then
00:44:12.860 --> 00:44:16.317 I kind of swore off of it though after that. So I I would it
00:44:15.460 --> 00:44:16.250 I have no idea.
00:44:16.317 --> 00:44:17.450 would it work I see.
00:44:17.940 --> 00:44:21.832 I know that our I think that we don't actually build anything.
00:44:21.832 --> 00:44:25.167 All that we do is we copy in whatever configs our our
00:44:25.167 --> 00:44:28.997 specific to our stuff, wrap it up in an artifact and then the
00:44:28.790 --> 00:44:30.020 And DLLS and stuff.
00:44:28.997 --> 00:44:32.642 release just copies in the connection strings and all that
00:44:32.642 --> 00:44:36.224 stuff and then creates the siblings. So it'll delete your
00:44:35.450 --> 00:44:35.750 Yeah.
00:44:36.224 --> 00:44:39.745 DNN folder, copy in the artifact, make your symlinks and
00:44:39.745 --> 00:44:43.760 copy and connection strings and then turn that falls back on so.
00:44:44.240 --> 00:44:44.790 Umm.
00:44:46.090 --> 00:44:50.753 Yeah, but yeah, that's 100% possible. And if you have DNN
00:44:50.753 --> 00:44:52.280 sites specifically.
00:44:53.100 --> 00:44:56.569 UM or like projects that are Deane and only this could
00:44:56.569 --> 00:45:00.353 potentially be a way to save you some time, but it does not
00:45:00.353 --> 00:45:04.137 handle changes to like the database since that's completely
00:45:04.137 --> 00:45:05.020 separate from.
00:45:05.760 --> 00:45:08.230 Uh, what Azure can track?
00:45:09.400 --> 00:45:12.408 So in terms of like if you're adding new pages or things that
00:45:12.408 --> 00:45:15.514 are gonna be inside the and in database, that's just gonna have
00:45:15.514 --> 00:45:18.328 to be manually pulled over to like QA site and stuff like
00:45:18.328 --> 00:45:18.570 that.
00:45:20.550 --> 00:45:24.820 But if you are making changes to content inside.
00:45:25.570 --> 00:45:28.995 Uh, DNN, that's actual code. Changes are committing to a repo
00:45:28.995 --> 00:45:31.370 then absolutely. This can do that for you.
00:45:33.440 --> 00:45:33.850 So.
00:45:34.630 --> 00:45:36.060 Hopefully that answers the question.
00:45:40.830 --> 00:45:41.590 Yeah. So.
00:45:43.750 --> 00:45:47.729 That kind of digs into the the implementation or the way that
00:45:47.729 --> 00:45:51.386 we build out our actual pipelines releases also use task
00:45:51.386 --> 00:45:52.990 groups so we can look at.
00:45:56.110 --> 00:45:58.300 The release for the same site.
00:45:58.700 --> 00:46:02.989 Umm, so on the left side here. This is the part that basically
00:46:02.989 --> 00:46:05.440 is the trigger to run this release.
00:46:06.090 --> 00:46:10.268 This this one is looking at the build pipeline that we were just
00:46:10.268 --> 00:46:13.867 looking at the source alias. I always forget where this
00:46:13.867 --> 00:46:17.338 actually comes from, but it it has to match something
00:46:17.338 --> 00:46:17.980 somewhere.
00:46:19.100 --> 00:46:21.330 I think it just has to match the name of the pipeline.
00:46:21.960 --> 00:46:24.991 I think so too. There is a setting back on the pipeline
00:46:24.991 --> 00:46:28.131 that does match that, but I think it's the name is. Yeah,
00:46:26.590 --> 00:46:27.730 Yeah, yeah.
00:46:28.131 --> 00:46:28.780 pretty sure.
00:46:28.400 --> 00:46:31.863 We typically just set it all to the name so that it's
00:46:31.863 --> 00:46:35.711 consistent. But UM then then there's one. Here's a little a
00:46:35.711 --> 00:46:39.688 little thing for for anybody that that is working on these or
00:46:39.688 --> 00:46:43.600 wants to work on pipelines and hopes to get to be able to at
00:46:43.600 --> 00:46:47.576 some point here's a little thing that I hate, that you should
00:46:47.576 --> 00:46:51.360 probably remember because I forgot it more than once. This
00:46:51.360 --> 00:46:55.015 little lightning bolt here doesn't normally have a check
00:46:55.015 --> 00:46:58.735 mark on it. If you click on this. This enables continuous
00:46:58.735 --> 00:46:59.440 deployment.
00:46:59.710 --> 00:47:02.932 If you don't do this, this release will just never run
00:47:02.932 --> 00:47:05.860 unless you do it manually, which I think is dumb.
00:47:07.280 --> 00:47:10.381 So you have to come in here, click on the lightning bolt.
00:47:10.381 --> 00:47:13.322 Check this and tell it to include and then your client
00:47:13.322 --> 00:47:16.744 branch or whatever branch you're building it for. Then and only
00:47:16.744 --> 00:47:19.150 then will it automatically run the releases.
00:47:19.830 --> 00:47:20.470 Uh.
00:47:21.330 --> 00:47:24.765 Again, I think it's dumb if I'm making a continuous deployment
00:47:24.765 --> 00:47:28.253 release, it should probably just have that on by default, but I
00:47:28.253 --> 00:47:28.580 guess.
00:47:29.800 --> 00:47:33.815 I guess there's more people that want it off by default than not
00:47:33.815 --> 00:47:37.644 in the world. Maybe. Maybe we're just doing something totally
00:47:37.644 --> 00:47:39.620 weird, but whatever. Anyway, so.
00:47:40.680 --> 00:47:43.390 Once the trigger passes, it goes over to the stages.
00:47:45.660 --> 00:47:48.549 So again, we've only got one stage here, kind of like the
00:47:48.549 --> 00:47:51.538 phases in the pipeline. So I don't really know that we have
00:47:51.538 --> 00:47:53.430 anything that that needs to do stuff.
00:47:54.560 --> 00:47:57.970 So these ones again click on the little side piece here.
00:48:00.070 --> 00:48:03.130 Selecting the trigger you have to do after release, not manual
00:48:03.130 --> 00:48:05.510 only the rest of it. I believe we leave default.
00:48:07.650 --> 00:48:11.880 On this guy here, you could click on one job, one task.
00:48:12.520 --> 00:48:14.420 And that will take you into a pipeline.
00:48:15.090 --> 00:48:18.772 And this pipeline is where the deploy self artifact is.
00:48:18.772 --> 00:48:23.046 However, 1 interesting thing to note is that this agent job does
00:48:23.046 --> 00:48:26.860 not run on the default pool. It runs on the server you're
00:48:26.860 --> 00:48:30.805 actually deploying to. So for example, here's your CEF devs
00:48:30.805 --> 00:48:35.013 and CEF stages. Here's our demo web boxes, DFO for the old, the
00:48:35.013 --> 00:48:35.670 old folks.
00:48:38.590 --> 00:48:39.440 Uh, so?
00:48:40.100 --> 00:48:43.020 This is the one that actually copies those files, and then
00:48:43.020 --> 00:48:46.186 again our deploy self Artifact task group that I briefly looked
00:48:46.186 --> 00:48:46.730 at earlier.
00:48:48.490 --> 00:48:51.724 And on this one you pass in what to do, so you tell it. Here's
00:48:51.724 --> 00:48:54.804 the app pool like root to kill all the app pools that match
00:48:54.804 --> 00:48:58.192 this name. Here's the artifact I need you to download, and here's
00:48:58.192 --> 00:49:00.450 the folder where my CEF site is configured.
00:49:01.140 --> 00:49:03.380 And it will just go in and do all the stuff.
00:49:04.080 --> 00:49:05.770 Umm so.
00:49:07.120 --> 00:49:07.890 That.
00:49:08.720 --> 00:49:14.070 Is most of what I can think to cover besides agents and stuff.
00:49:14.220 --> 00:49:18.733 UMJ guess you can look at that. So that's gonna be deployment
00:49:18.733 --> 00:49:19.970 groups, isn't it?
00:49:21.670 --> 00:49:22.880 CEF product.
00:49:24.610 --> 00:49:28.755 Agent pools the alright. So here's all our agent pools
00:49:28.755 --> 00:49:33.427 again. You can see CEF devs and CEF stages clarity production
00:49:33.427 --> 00:49:34.180 demo webs.
00:49:34.840 --> 00:49:38.330 And these have to have. Uh.
00:49:39.320 --> 00:49:43.020 Somebody go in and set them up. So for example, it looks like
00:49:43.020 --> 00:49:46.720 SEF stage one doesn't actually have this set up, so if you're
00:49:46.720 --> 00:49:50.420 setting up a client project on a box that doesn't have these.
00:49:51.060 --> 00:49:54.938 Uh, somebody will need to go in and set up the agent pool for
00:49:54.938 --> 00:49:55.500 that box.
00:49:58.250 --> 00:49:59.200 Is there a good like?
00:49:58.340 --> 00:50:02.137 There is a there's a new cleanup guide for it. It's not massively
00:50:02.137 --> 00:50:05.934 complicated, but you do need the special password for the release
00:50:05.934 --> 00:50:09.559 manager account, so that would be something that only a few of
00:50:09.559 --> 00:50:12.780 the people who could could set these up would would do.
00:50:13.780 --> 00:50:16.633 I did. Uh, stage two the other day. So the password still
00:50:16.633 --> 00:50:19.485 works, but so does the token that we use. So right there,
00:50:18.660 --> 00:50:19.570 Yay.
00:50:19.485 --> 00:50:19.780 right.
00:50:20.890 --> 00:50:24.642 But the again like I mentioned earlier, the default one has all
00:50:24.642 --> 00:50:26.400 of our build servers on it so.
00:50:27.310 --> 00:50:30.800 You can you can look at them in all their glory.
00:50:33.950 --> 00:50:36.660 Hard work and boxes doing a lot of.
00:50:37.580 --> 00:50:39.000 Crunching the numbers and such.
00:50:39.750 --> 00:50:41.540 Umm yeah.
00:50:43.660 --> 00:50:46.575 What else do we have in here like this is a place that
00:50:46.575 --> 00:50:48.270 probably no one's gonna look at.
00:50:50.960 --> 00:50:52.250 Unless they're setting up a new.
00:50:53.060 --> 00:50:55.830 Agent pool. Like there's really no reason to ever go in here.
00:50:57.000 --> 00:50:58.350 But it is really cool. So.
00:50:59.960 --> 00:51:03.149 You can see also we've got some of our production sites that are
00:51:03.149 --> 00:51:06.190 pipelined deployed by some, I mean the only one which is row.
00:51:06.860 --> 00:51:10.310 I think all the others are manual deployments of some kind.
00:51:11.730 --> 00:51:13.020 Unless sure is.
00:51:13.970 --> 00:51:15.410 I think that's a client one as well.
00:51:16.620 --> 00:51:18.000 Hasn't seen deployment in.
00:51:18.930 --> 00:51:20.180 Four years.
00:51:21.700 --> 00:51:24.164 That's a good thing, right? That means they're stable and
00:51:24.164 --> 00:51:25.310 everything's working great.
00:51:25.960 --> 00:51:27.670 Yeah, actually baby, right?
00:51:29.230 --> 00:51:30.260 Said set up it's.
00:51:30.990 --> 00:51:31.260 Yeah.
00:51:32.770 --> 00:51:33.980 They haven't complained.
00:51:33.150 --> 00:51:33.610 But yeah.
00:51:34.400 --> 00:51:35.950 They yeah, obviously.
00:51:37.140 --> 00:51:41.614 Umm, so yeah, cool. Any other questions or things that anyone
00:51:41.614 --> 00:51:45.870 saw along the way that they thought looked cool? They want
00:51:45.870 --> 00:51:46.880 me to look at.
00:51:54.570 --> 00:51:55.850 I will tell you this.
00:51:56.910 --> 00:52:01.390 The first time I received some training on this, we set up a.
00:52:02.440 --> 00:52:06.563 An account that was free and then I have my clarity account
00:52:06.563 --> 00:52:10.618 and then my secondary Azure cloud account. I think you can
00:52:10.618 --> 00:52:14.535 do artifacts in that. In practice it on your own account
00:52:14.535 --> 00:52:16.390 and set it all up for free.
00:52:21.760 --> 00:52:23.770 If that's an option, anybody is willing to try.
00:52:24.450 --> 00:52:28.368 Uh, similarly real quick the we also have I think each of our
00:52:28.368 --> 00:52:32.350 Windows accounts, I don't know if it's everyone, it might just
00:52:32.350 --> 00:52:36.331 be anyone within enterprise but gets $200 of Azure credits per
00:52:35.510 --> 00:52:35.790 Yeah.
00:52:36.331 --> 00:52:36.710 month.
00:52:36.930 --> 00:52:39.963 Yeah, yeah, I got that same one. I don't think it matters if it's
00:52:39.963 --> 00:52:40.790 enterprise or not.
00:52:42.620 --> 00:52:46.244 There you can use those to play around with this outside of the
00:52:46.244 --> 00:52:49.698 CEF stuff if you wanna just kind of go through and look at a
00:52:49.698 --> 00:52:50.490 little closer.
00:52:52.610 --> 00:52:56.031 And we kind of briefly touched on this earlier, but there
00:52:56.031 --> 00:52:59.747 pipelines are not just for, for CEF, the only instance we have
00:52:59.747 --> 00:53:03.522 here right now is that the old clarity deployment tool repo has
00:53:03.522 --> 00:53:07.238 a pipeline where I'm gonna be moving that to the clarity tools
00:53:07.238 --> 00:53:10.600 repo since it's all sort of consolidating into one tool.
00:53:11.740 --> 00:53:15.773 And we're gonna be using that to make it so that you guys can
00:53:15.773 --> 00:53:19.936 automatically download updates to the installer and CLT without
00:53:19.936 --> 00:53:24.099 us having to do any manual work. Just push a change and you see
00:53:24.099 --> 00:53:26.180 it. That's the plan anyway, but.
00:53:24.710 --> 00:53:25.040 Cool.
00:53:27.390 --> 00:53:30.487 Same same deal goes for any other projects. If you're
00:53:30.487 --> 00:53:34.100 working on projects that aren't SEF, and you can summarize the
00:53:34.100 --> 00:53:37.540 build step and the deployment steps with some commands that
00:53:37.540 --> 00:53:41.210 you could do in command line or whatever other pieces and tasks
00:53:41.210 --> 00:53:44.651 that Azure has, by all means, if it saves time and makes it
00:53:44.651 --> 00:53:45.740 easier to test and.
00:53:46.420 --> 00:53:49.496 Or that kind of stuff that makes perfect sense to to automate
00:53:49.496 --> 00:53:50.290 where we can so.
00:53:50.670 --> 00:53:55.382 Yeah, and I'll I'll own the the DNN side of it. And just like
00:53:55.382 --> 00:53:58.270 try to get it going as much as I
00:53:59.670 --> 00:54:03.482 Ping whoever I need, so if you wanna hop on there with me,
00:54:03.482 --> 00:54:07.100 it'll probably be Patrick and I hammering away at that.
00:54:12.730 --> 00:54:15.700 Cool. And then, Richard, you had a question.
00:54:18.220 --> 00:54:20.930 Yeah. In regards to the stuff installer.
00:54:21.330 --> 00:54:25.652 Uh, is there any way to try and flip some of the settings for
00:54:25.652 --> 00:54:25.930 the?
00:54:26.790 --> 00:54:29.650 A CEF instance so that it matches the.
00:54:31.420 --> 00:54:35.965 The demo site that's currently being used, like any demos. All.
00:54:34.500 --> 00:54:37.809 Oh yeah, that's a good question. UM, that's something kind of
00:54:35.965 --> 00:54:36.320 Yeah.
00:54:37.809 --> 00:54:39.890 separate. But I do wanna fix that too.
00:54:41.760 --> 00:54:46.348 Which is I want to start making it a thing that we do moving
00:54:46.348 --> 00:54:50.937 forward where the config file that is used on a demo site is
00:54:50.937 --> 00:54:55.675 available in CEF config so that if people are fixing core bugs
00:54:55.675 --> 00:55:00.414 and things like that, they have the same app settings that the
00:55:00.414 --> 00:55:02.670 site was qaid with in general.
00:55:04.270 --> 00:55:05.320 We could also.
00:55:06.850 --> 00:55:11.297 We can also fix that, especially in the more recent version of
00:55:11.297 --> 00:55:15.674 CEF by moving the OR putting the client config file in source
00:55:15.674 --> 00:55:20.262 control. The only reason I don't want to go that route for doing
00:55:20.262 --> 00:55:24.285 it directly in core is because I don't want every client
00:55:24.285 --> 00:55:28.309 branching off to have the release site config, which has
00:55:28.309 --> 00:55:30.920 like every single feature turned on.
00:55:32.240 --> 00:55:35.400 It and so for client projects though.
00:55:36.500 --> 00:55:41.627 And this is just kind of a PSA or a an announcement that I hope
00:55:41.627 --> 00:55:44.750 people are, you know, cheer cheer for.
00:55:46.770 --> 00:55:48.230 Four 2022.2.
00:55:49.390 --> 00:55:53.388 And and newer whenever you create a repo for a client
00:55:53.388 --> 00:55:53.980 project.
00:55:55.250 --> 00:55:59.310 Feel free and by feel free I mean please do.
00:56:01.420 --> 00:56:06.490 Add the app settings dot client dot JSON file to source control.
00:56:08.310 --> 00:56:11.461 And for client projects, we can keep that specific file in
00:56:11.461 --> 00:56:14.558 source control and make it so that everybody pulling that
00:56:14.558 --> 00:56:17.868 project has the same settings all the time and it's something
00:56:17.868 --> 00:56:19.790 we can keep an eye on and whatever.
00:56:21.060 --> 00:56:24.108 That should hopefully save everyone a lot of time. That
00:56:24.108 --> 00:56:27.046 being said, we are gonna be vigilant and PR's for any
00:56:27.046 --> 00:56:30.420 changes related to that, making sure people aren't committing
00:56:30.420 --> 00:56:31.290 folder paths or.
00:56:32.470 --> 00:56:34.080 Passwords or anything like that.
00:56:36.730 --> 00:56:38.180 But uh yeah.
00:56:39.340 --> 00:56:41.866 And like I said, the only reason I don't want to do that in core
00:56:41.866 --> 00:56:44.120 is because then every client project that branches off is
00:56:44.120 --> 00:56:46.607 gonna have every single feature enabled and have to go and make
00:56:46.607 --> 00:56:47.850 it crap. A little modifications.
00:56:50.030 --> 00:56:54.250 So does that answer your question, Richard? I guess more
00:56:54.250 --> 00:56:55.730 of kind of like a A.
00:56:56.940 --> 00:57:00.010 I can get you the app settings for the for the.
00:57:00.730 --> 00:57:03.746 Release site and then moving forward I want to put those in
00:57:03.746 --> 00:57:06.911 CEF config so that people can get at them a little easier than
00:57:06.911 --> 00:57:08.670 having to RDP into a specific box.
00:57:14.890 --> 00:57:15.850 Alright and I think.
00:57:15.100 --> 00:57:18.070 Did I miss that? Did I? Did I miss that? Brendan, can you can
00:57:16.710 --> 00:57:17.260 I'm sorry.
00:57:18.070 --> 00:57:21.184 you quick high level, what would go in that client config versus
00:57:21.184 --> 00:57:24.011 what would not? I know you mentioned like folder paths and
00:57:23.230 --> 00:57:23.810 So.
00:57:24.011 --> 00:57:26.789 credentials, but what what ideally does go in that client
00:57:24.980 --> 00:57:26.090 Yeah.
00:57:26.789 --> 00:57:28.130 one that's written the repo?
00:57:28.450 --> 00:57:32.603 Yeah. So that one's gonna have all of your, like clarity dot
00:57:32.603 --> 00:57:36.688 feature set dot sales invoices enabled or enabled providers
00:57:36.688 --> 00:57:37.300 lists or.
00:57:38.620 --> 00:57:42.558 Custom dashboard routes all that kind of stuff. That is the same
00:57:42.558 --> 00:57:46.192 on every single setup of a client site. For the consistency
00:57:46.192 --> 00:57:49.766 for the fact that you know it needs to be that way for the
00:57:49.766 --> 00:57:50.250 clients.
00:57:50.950 --> 00:57:53.498 Workflow to work and for all the other code people are writing on
00:57:53.498 --> 00:57:54.270 the project to work.
00:57:55.060 --> 00:57:55.600 Umm.
00:57:57.000 --> 00:58:01.242 Uh, but not anything that is either secure at like as in a
00:58:01.242 --> 00:58:05.914 credential, or what's the word I like to use for this transient,
00:58:05.914 --> 00:58:10.299 as in different between every setup so gonna be folder paths
00:58:10.299 --> 00:58:14.756 in URLs and stuff like that. So that's sort of what I imagine
00:58:14.756 --> 00:58:19.141 would would be in that client file is all your feature sets,
00:58:19.141 --> 00:58:20.650 providers, tasks etc.
00:58:20.730 --> 00:58:21.090 That are.
00:58:22.230 --> 00:58:26.917 Excluding any credentials related to those providers and
00:58:26.917 --> 00:58:27.410 stuff.
00:58:28.700 --> 00:58:32.046 Stuff that I'm always looking for when I ask for, like, hey,
00:58:32.046 --> 00:58:35.118 will you send me your app settings and then but you see
00:58:35.118 --> 00:58:38.629 me, you see me changing like 20 things anyway. But I'm changing
00:58:38.629 --> 00:58:42.030 like the folder paths. But I I wanted all of like the feature
00:58:41.400 --> 00:58:41.690 Yeah.
00:58:42.030 --> 00:58:45.211 set things. So it's it's extremely awesome that that's in
00:58:45.211 --> 00:58:48.228 potentially in in version control for client things it
00:58:47.560 --> 00:58:49.860 Yeah, the idea is to, yeah.
00:58:48.228 --> 00:58:51.520 might even be good and it might even be good in the release
00:58:51.520 --> 00:58:54.866 branch. But I I can see your I
00:58:52.440 --> 00:58:53.060 It could be.
00:58:54.230 --> 00:58:58.010 And like I can be wrong I'm I'm happy to be wrong.
00:58:54.866 --> 00:58:55.030 it.
00:59:00.440 --> 00:59:05.791 But yeah, the idea is that it makes tasks like turn on
00:59:05.791 --> 00:59:08.320 discounts for XYZ project.
00:59:08.450 --> 00:59:11.253 Uh, right now that effectively is like turn it on in your
00:59:11.253 --> 00:59:14.298 local, make sure it works. Copy the app settings to all the QA
00:59:14.298 --> 00:59:16.763 and stage and then send a message to all the other
00:59:16.763 --> 00:59:19.807 developers and say hey, we're turning this app setting on. Add
00:59:19.807 --> 00:59:20.870 this to your settings.
00:59:22.240 --> 00:59:25.049 Now it's just turn it on your local and make sure it works.
00:59:25.049 --> 00:59:26.500 Commit and make a pull request.
00:59:27.540 --> 00:59:31.160 That's it. Everybody else will pull it down as normal, just
00:59:31.160 --> 00:59:34.840 like every other change you make, and it'll it'll, you know,
00:59:34.840 --> 00:59:36.650 track with that client's code.
00:59:38.200 --> 00:59:40.070 As as needed so.
00:59:43.480 --> 00:59:45.800 Yeah. Richard, did you have anything else or?
00:59:47.380 --> 00:59:49.520 Somebody else had their hands up, Justin.
00:59:48.970 --> 00:59:50.260 Ah, no, no, that's it for me.
00:59:49.820 --> 00:59:50.290 Weathers.
00:59:50.560 --> 00:59:53.070 OK, cool. Uh, what do you got, Justin?
00:59:53.850 --> 00:59:57.909 Hey, I was just wondering cause for like athlete bid they have
00:59:57.909 --> 01:00:02.032 the X portal so putting them on a pipeline. I know that there's
01:00:02.032 --> 01:00:06.026 been some confusion but is it possible to put the export on a
01:00:06.026 --> 01:00:09.956 a pipeline? I don't imagine why it wouldn't be right like is
01:00:09.420 --> 01:00:13.593 Yes, possible. Yes. Have we done it yet? No. So it getting that
01:00:09.956 --> 01:00:10.600 that just?
01:00:11.710 --> 01:00:12.010 Umm.
01:00:13.593 --> 01:00:17.765 to work would just be a matter of building out a working set of
01:00:14.780 --> 01:00:15.110 OK.
01:00:17.765 --> 01:00:21.677 task groups and pipelines and and stuff like that. And then
01:00:21.677 --> 01:00:25.784 getting releases for it. But it is definitely something that's
01:00:23.630 --> 01:00:23.960 It.
01:00:25.784 --> 01:00:27.740 physically possible, I'm sure.
01:00:28.070 --> 01:00:30.240 Ituses.net core, so it might.
01:00:28.910 --> 01:00:33.939 And we go through that right now, it would just be a command
01:00:33.939 --> 01:00:36.000 of getting the folder in.
01:00:35.700 --> 01:00:39.380 So yeah, it would be part of. You'd have to. I don't actually.
01:00:38.500 --> 01:00:42.470 Dot net buildand.net publish and then copying the folders.
01:00:40.660 --> 01:00:43.586 Yeah, pretty much. And then copying it all in. Yeah, it
01:00:43.586 --> 01:00:46.512 would take longer than 20 minutes to do, but I mean, we
01:00:46.512 --> 01:00:49.490 would do that. And I think
01:00:49.490 --> 01:00:52.833 they're. So there's analyzing, there's analyzers for exporting.
01:00:52.833 --> 01:00:53.930 If we look at 2021.4.
01:00:55.040 --> 01:00:55.710 Right here.
01:00:56.860 --> 01:01:00.717 Uh polls does this and just builds the solution for X
01:01:00.717 --> 01:01:02.930 portal. OK, so that's it. Cool.
01:01:04.570 --> 01:01:08.107 But yeah, Jesse's right given that exporter is actually on a
01:01:08.107 --> 01:01:11.295 newer version of of net. Specifically, it's running on
01:01:11.295 --> 01:01:15.122 net core NET 5. Even I think you
01:01:12.900 --> 01:01:15.630 It's all command line. You can do it in all the command line.
01:01:15.122 --> 01:01:18.890 and then copy that folder to an artifact and then make a deploy.
01:01:18.890 --> 01:01:22.485 That is, I mean, I wouldn't be too difficult at all really to
01:01:22.485 --> 01:01:23.470 make that happen.
01:01:24.110 --> 01:01:27.506 Worse, everything else that we've said is wildly convenient
01:01:27.506 --> 01:01:29.600 with Azure has turned out to not be.
01:01:29.970 --> 01:01:34.500 Yeah. True. Very, very true.
01:01:37.020 --> 01:01:39.913 So, but yeah, I mean we basically you would just go in
01:01:38.220 --> 01:01:38.490 Cool.
01:01:39.913 --> 01:01:43.279 here and make a task group for where the hell is the new button
01:01:43.279 --> 01:01:44.330 in here? Am I blind?
01:01:46.350 --> 01:01:49.270 There's import, but I don't see a new.
01:01:53.750 --> 01:01:55.550 You don't have permission to do new task groups.
01:01:56.220 --> 01:01:57.290 Do you think it's that granular?
01:01:56.630 --> 01:01:57.620 Unbelievable.
01:01:58.810 --> 01:01:59.310 You might be.
01:01:59.740 --> 01:02:01.390 Hold on. Here's what we're gonna do.
01:02:02.360 --> 01:02:07.561 Given the old Razzle dazzle, export one import it, change its
01:02:02.590 --> 01:02:03.250 Going to export.
01:02:04.300 --> 01:02:05.160 Export and import.
01:02:07.561 --> 01:02:07.980 name.
01:02:08.810 --> 01:02:11.827 I made the 2022.2 once. This must have been how I did it. I
01:02:11.827 --> 01:02:14.693 just exported and imported whatever. Alright so I can do
01:02:14.693 --> 01:02:16.000 that I guess, but I can't.
01:02:17.320 --> 01:02:22.810 OK, so this is gonna be a create X portal.
01:02:25.220 --> 01:02:29.060 Artifact for 2021.4.
01:02:31.720 --> 01:02:33.040 And we'll just leave it at that.
01:02:33.380 --> 01:02:37.740 Seeiftheresany.net core tasks in the in the choice, yeah.
01:02:33.680 --> 01:02:34.900 Yeah, we're gonna keep that.
01:02:35.640 --> 01:02:39.098 Ohh, they're definitely is. Yeah. So we're gonna pull our
01:02:39.098 --> 01:02:40.290 latest self configs.
01:02:40.940 --> 01:02:42.700 Copy configs pre.
01:02:44.570 --> 01:02:45.480 I don't need that.
01:02:47.300 --> 01:02:47.830 Or that?
01:02:49.980 --> 01:02:51.970 Any of these can I? Yeah.
01:02:50.450 --> 01:02:52.460 Any of those do they all would just go.
01:02:53.270 --> 01:02:54.580 You get all that out of here, alright?
01:02:54.680 --> 01:02:55.350 Sound effects?
01:02:56.280 --> 01:02:56.930 Thank you.
01:02:58.310 --> 01:03:02.240 So in while we're in here, I can go back into the task groups and
01:03:02.240 --> 01:03:04.860 open one of our like create self artifacts.
01:03:04.790 --> 01:03:05.690 Did you save?
01:03:06.840 --> 01:03:10.340 I didn't. Ted, don't you don't you worry about a thing.
01:03:07.440 --> 01:03:09.170 Ohh jeez.
01:03:12.500 --> 01:03:16.654 Yeah. All right. OK. So we got pull latest stuff configs. I
01:03:16.654 --> 01:03:20.878 guess we can probably add these fellow if you can copy these
01:03:20.878 --> 01:03:22.470 over here. No, nothing.
01:03:23.210 --> 01:03:24.640 That was too much to hope for.
01:03:23.410 --> 01:03:26.110 That would be that would be very convenient.
01:03:26.740 --> 01:03:29.150 Wildly convenient. You might even say.
01:03:29.340 --> 01:03:33.280 Yes, I still have that written down. What you said that.
01:03:30.590 --> 01:03:34.210 In fact, here's what I'm going to do. Going to discard this.
01:03:30.660 --> 01:03:31.360 I love that.
01:03:34.210 --> 01:03:35.100 We're gonna go.
01:03:35.930 --> 01:03:39.280 Uh back leave.
01:03:38.540 --> 01:03:40.580 What do you do? You just destroyed it.
01:03:41.670 --> 01:03:45.636 I cast it into the fire. We're going to take uh this 2021.4
01:03:45.636 --> 01:03:49.801 create artifact, import that one since that one's gonna have a
01:03:49.801 --> 01:03:52.180 lot more overlap with what we need.
01:03:52.810 --> 01:03:55.440 Michael just posted the the actual.
01:03:56.560 --> 01:04:00.420 Command to run in the in the command line. Will that also do
01:04:00.420 --> 01:04:03.900 a build.net publish will build it if it isn't already.
01:04:04.950 --> 01:04:06.640 I I think it does, yeah.
01:04:07.030 --> 01:04:07.770 So that's.
01:04:07.410 --> 01:04:12.250 Yes, that publishes it to the second directory.
01:04:08.200 --> 01:04:09.650 That's pretty, pog.
01:04:13.750 --> 01:04:14.920 Well, there you go.
01:04:15.980 --> 01:04:20.250 That's you would just replace part of the path with UM, you
01:04:20.250 --> 01:04:20.890 know the.
01:04:22.500 --> 01:04:24.620 With the yeah, the output directory, yeah.
01:04:23.270 --> 01:04:25.820 With one of the very exactly yeah, yeah.
01:04:25.850 --> 01:04:28.762 So yeah, we're gonna build's build category. That's cool.
01:04:27.720 --> 01:04:28.170 Sick.
01:04:28.762 --> 01:04:31.774 That's pull. Latest make these folders. Even though I don't
01:04:31.774 --> 01:04:33.480 think they're needed for xportal.
01:04:34.400 --> 01:04:35.170 Uh.
01:04:38.560 --> 01:04:41.610 Yeah, OK, that seems fine. Copy and config because those
01:04:41.610 --> 01:04:42.680 probably are needed.
01:04:43.790 --> 01:04:44.820 That's not needed.
01:04:46.570 --> 01:04:48.160 Copy configs post.
01:04:51.250 --> 01:04:54.061 They're doing the same thing. We probably don't need to pre and
01:04:54.061 --> 01:04:56.695 post there, so we can just remove the word premich one this
01:04:56.695 --> 01:04:57.090 one time.
01:04:57.780 --> 01:05:02.009 Don't need to build react don't need to install anything for the
01:05:02.009 --> 01:05:03.050 front end stuff.
01:05:03.220 --> 01:05:06.504 It doesn't need to build Seth either, right? It's don't thing.
01:05:05.700 --> 01:05:07.300 Correct. So.
01:05:06.504 --> 01:05:07.650 So all of that really.
01:05:08.130 --> 01:05:13.420 We need to change this guy to xportal dot SLN.
01:05:14.790 --> 01:05:19.050 And also this guy to X portal.
01:05:20.450 --> 01:05:21.100 That's all in.
01:05:23.510 --> 01:05:24.160 Sick.
01:05:23.790 --> 01:05:26.533 Actually, no. You know what? I don't think we need to this. We
01:05:26.533 --> 01:05:29.320 may. OK, let me first get rid of everything down here because I
01:05:28.860 --> 01:05:29.200 Because.
01:05:29.320 --> 01:05:31.540 know we're not gonna need any of these. Whoa, God.
01:05:30.630 --> 01:05:33.853 If the publish is gonna, if the publisher is going to make it
01:05:33.510 --> 01:05:35.841 Exactly. I was thinking that too, what we might be able to
01:05:33.853 --> 01:05:34.580 build already.
01:05:35.841 --> 01:05:37.460 get rid of this and just do it that way.
01:05:38.450 --> 01:05:41.320 So, but let's click on right here.
01:05:42.000 --> 01:05:45.415 Add a task and you can go and look through all your stuff and
01:05:44.720 --> 01:05:45.280 The core.
01:05:45.415 --> 01:05:48.610 you look at build.net core build test package or publish.
01:05:49.890 --> 01:05:51.540 That's wildly convenient.
01:05:51.700 --> 01:05:52.480 Dot net.
01:05:54.540 --> 01:05:55.930 Mildly I love it.
01:05:55.320 --> 01:05:55.860 Build sure.
01:05:56.790 --> 01:05:57.200 Like.
01:05:57.120 --> 01:06:00.110 No, we don't want a nugget push. We want a publish.
01:06:00.860 --> 01:06:04.934 KB, We said that about like this option on these task groups the
01:06:04.934 --> 01:06:08.506 other day and it spoiler alert, didn't really do what it
01:06:08.506 --> 01:06:10.260 advertised. It was gonna do.
01:06:09.090 --> 01:06:13.211 Yeah, run, run this task even if a previous task is failed, even
01:06:13.211 --> 01:06:17.395 if the deployment was cancelled. So it's just a I don't care. Run
01:06:15.780 --> 01:06:16.770 Oh my God.
01:06:17.395 --> 01:06:19.360 it always anytime and it works.
01:06:19.810 --> 01:06:21.590 Kind of, yeah.
01:06:20.300 --> 01:06:21.870 Mostly, yeah.
01:06:23.260 --> 01:06:27.667 So but anyway, wow. And even has a thing to zip the the the
01:06:27.667 --> 01:06:29.430 published files for you.
01:06:31.420 --> 01:06:31.870 Wow.
01:06:31.570 --> 01:06:32.530 I know, trust it.
01:06:33.880 --> 01:06:35.110 Check it. Check it.
01:06:38.150 --> 01:06:40.300 This is wildly convenience.
01:06:41.100 --> 01:06:42.880 Wildly convenient.
01:06:44.810 --> 01:06:45.790 All right, so.
01:06:45.070 --> 01:06:46.780 It looks easy, it's wrong.
01:06:46.980 --> 01:06:49.490 I work, V said exactly.
01:06:50.160 --> 01:06:54.690 So build sources directory, build dot sources directory.
01:06:58.850 --> 01:07:00.620 I guess it's something that gets passed in.
01:07:01.350 --> 01:07:04.156 Which is going to be like the root of the subfolder. Yeah. So
01:07:04.156 --> 01:07:05.740 I guess what we can do right here.
01:07:06.400 --> 01:07:08.420 As we can just have it.
01:07:17.320 --> 01:07:17.820 Do that.
01:07:17.600 --> 01:07:17.810 OK.
01:07:18.900 --> 01:07:21.200 Going to do Dash C debug.
01:07:22.040 --> 01:07:23.690 Actually we do dash C.
01:07:25.170 --> 01:07:25.680 Uh.
01:07:25.400 --> 01:07:26.080 Mode.
01:07:26.780 --> 01:07:28.760 Yeah. I was about to say you might do release.
01:07:27.050 --> 01:07:27.920 Second here.
01:07:29.080 --> 01:07:29.560 Yeah.
01:07:30.480 --> 01:07:35.375 Didn't didn't add it. It's OK. Maybe it's dollar mode like
01:07:35.375 --> 01:07:35.790 that.
01:07:37.690 --> 01:07:40.161 Yeah, that did it. And then we
01:07:40.161 --> 01:07:42.760 debug. What you could change it to release or release sites.
01:07:43.990 --> 01:07:47.120 Or for production sites. Cool. So then.
01:07:47.900 --> 01:07:49.070 See mode.
01:07:50.180 --> 01:07:51.450 Dash O.
01:07:52.460 --> 01:07:56.703 Build that source. What was it? Build dot sources directory?
01:07:56.703 --> 01:07:57.050 Yeah.
01:08:02.140 --> 01:08:03.000 Flash.
01:08:04.020 --> 01:08:08.050 UM publish, just do that OK.
01:08:10.170 --> 01:08:13.201 If true folders created by the publish command will have the
01:08:13.201 --> 01:08:16.232 projects folder named prefix to their folder names. When the
01:08:16.232 --> 01:08:18.120 output paths. Nah, I don't need that.
01:08:20.290 --> 01:08:22.580 This slash publish in the argument.
01:08:23.320 --> 01:08:26.140 So that it puts all those files in it. That's where it puts it,
01:08:23.710 --> 01:08:25.440 Oh. Oh, that's the that's I see.
01:08:26.140 --> 01:08:26.360 yeah.
01:08:26.250 --> 01:08:28.000 That's the folder path minus take OK.
01:08:27.640 --> 01:08:31.464 Yeah. And I think we need just need this build dot sources
01:08:31.464 --> 01:08:34.120 directory so it knows where to run this.
01:08:35.160 --> 01:08:39.550 And then we can get rid of the old build.
01:08:40.500 --> 01:08:41.960 We can make our making.
01:08:40.620 --> 01:08:42.640 Do you think it's gonna do with that zip?
01:08:43.660 --> 01:08:45.970 It's a good question. I kind of want to just run this.
01:08:46.450 --> 01:08:46.990 To see.
01:08:46.770 --> 01:08:49.800 And yeah, so then I'm going to get rid of.
01:08:49.080 --> 01:08:49.620 Running.
01:08:50.680 --> 01:08:53.150 All of these copy commands because we don't actually.
01:08:54.000 --> 01:08:57.000 Need to do any of that if it's zipping it for us.
01:08:58.020 --> 01:09:01.397 There is a way. It's it's hidden and I'll show you where to
01:08:59.560 --> 01:09:00.250 It says.
01:09:01.397 --> 01:09:04.605 click. But when you build, when you build these, you can
01:09:04.605 --> 01:09:07.250 download the artifact. It's it's weird and it.
01:09:08.460 --> 01:09:12.174 It's a weird it's it's tough to get to it, but you can download
01:09:12.174 --> 01:09:14.030 the artifact after it publishes.
01:09:13.550 --> 01:09:16.572 Does it actually make the two zip folder? It makes it directly
01:09:16.572 --> 01:09:19.593 inside. Alright, cool, so that's fine. And then you can delete
01:09:19.593 --> 01:09:20.840 the archive file which is.
01:09:22.060 --> 01:09:24.421 Probably something we'll do, but we'll cross that bridge when we
01:09:24.421 --> 01:09:24.820 come to it.
01:09:25.650 --> 01:09:27.560 Alright, so this publishes the artifact.
01:09:28.270 --> 01:09:31.620 The path to publish would be.
01:09:32.940 --> 01:09:36.170 Build dot artifacts staging directory.
01:09:37.130 --> 01:09:38.560 Do we pass that in over here?
01:09:39.650 --> 01:09:40.270 Showdown.
01:09:41.440 --> 01:09:42.470 Where's that coming from?
01:09:43.350 --> 01:09:46.974 It must be one of the constants that that are probably set in
01:09:46.380 --> 01:09:47.050 Yeah, yeah.
01:09:46.974 --> 01:09:48.260 the project somewhere.
01:09:48.330 --> 01:09:52.696 Uh archive file to create build dot artifact staging directory,
01:09:52.696 --> 01:09:53.310 so if we.
01:09:54.380 --> 01:09:56.340 Did this and instead.
01:09:57.290 --> 01:09:59.680 Did just build dot.
01:10:00.400 --> 01:10:05.450 Artifacts staging directory and they got rid of publish.
01:10:06.050 --> 01:10:09.714 Just tell it to output the publish directly to that and
01:10:09.714 --> 01:10:10.760 then publish it.
01:10:13.660 --> 01:10:14.200 Umm.
01:10:15.630 --> 01:10:16.680 Yeah, cool.
01:10:20.290 --> 01:10:21.700 Who wants to see it? This works.
01:10:23.350 --> 01:10:24.610 With our last 10 minutes.
01:10:24.970 --> 01:10:25.460 Yeah.
01:10:25.060 --> 01:10:25.460 Yes.
01:10:26.440 --> 01:10:26.880 Yeah.
01:10:27.150 --> 01:10:28.760 So we can save this guy.
01:10:27.610 --> 01:10:29.500 Are you an optimist or a pessimist?
01:10:31.550 --> 01:10:35.690 Optimist. You can tell optimist. Tell tell.
01:10:33.570 --> 01:10:35.010 Optimist. They're funny.
01:10:35.380 --> 01:10:37.360 Yeah, but at some Microsoft products so.
01:10:37.610 --> 01:10:38.810 Ohh true yeah.
01:10:37.630 --> 01:10:40.300 Hey. Yeah, yeah.
01:10:38.100 --> 01:10:39.230 It's not gonna work. Yeah.
01:10:38.200 --> 01:10:41.690 I am I am optimistic that I can get it to work. I'm not
01:10:41.690 --> 01:10:44.120 optimistic that I nailed it first try.
01:10:44.340 --> 01:10:46.160 Yeah. Yeah, I I like.
01:10:45.120 --> 01:10:47.300 That would be really cool if I did but.
01:10:48.060 --> 01:10:49.650 Yeah, I like the, you know, the.
01:10:49.730 --> 01:10:52.850 Yeah. What's the best way to say that?
01:10:54.190 --> 01:10:57.032 Try and play around with it and get it to run and see what
01:10:57.032 --> 01:10:57.850 errors come back.
01:10:59.720 --> 01:11:00.960 Yeah, that's what I was gonna do.
01:11:01.670 --> 01:11:01.970 Yeah.
01:11:05.870 --> 01:11:06.490 One second.
01:11:11.770 --> 01:11:16.078 I will tell you this. I remember Chris Golden training us and the
01:11:16.078 --> 01:11:19.864 dude went through it so quickly. You were like, what just
01:11:19.864 --> 01:11:22.540 happened? Did I just black out? I don't.
01:11:24.960 --> 01:11:27.440 It's a lot of. It's a lot of information for sure.
01:11:26.300 --> 01:11:29.984 Is it is? It is, but the dude was going through it so quickly
01:11:29.984 --> 01:11:33.668 you couldn't keep up like the whole team couldn't keep up and
01:11:33.668 --> 01:11:37.351 he was just like click here. Do this. Do that? Like what? No,
01:11:37.351 --> 01:11:40.797 I'm gonna have to go back and rewatch what you just did 5
01:11:40.797 --> 01:11:41.510 seconds ago.
01:11:42.030 --> 01:11:42.460 Yep.
01:11:43.790 --> 01:11:45.940 OK, well, let's trigger it. Let's see what happens.
01:11:46.540 --> 01:11:46.830 Yeah.
01:11:48.330 --> 01:11:49.190 Pipelines.
01:11:50.240 --> 01:11:52.276 Alright, I just made a task group. I need to actually make a
01:11:52.276 --> 01:11:52.810 pipeline for it.
01:11:54.080 --> 01:11:54.690 Alright.
01:11:56.160 --> 01:11:58.750 I always forget. I think we do this one.
01:11:59.690 --> 01:12:03.946 CEF product at every time I do this I do it wrong the first
01:12:03.946 --> 01:12:04.300 time.
01:12:05.060 --> 01:12:09.881 Just give me an empty just where's empty? Empty, empty,
01:12:09.881 --> 01:12:11.000 blank, empty.
01:12:17.320 --> 01:12:20.970 It's annoying because yeah, I did it wrong. It always wants
01:12:20.970 --> 01:12:24.741 you to use their stupid YAML textual one in the visual editor
01:12:24.741 --> 01:12:28.573 is perfectly good and fine and much, much more intuitive and I
01:12:28.573 --> 01:12:31.310 always do it wrong the first time like that.
01:12:32.050 --> 01:12:35.908 And then I have to remember how to do it and I think I usually
01:12:35.908 --> 01:12:39.030 end up just exporting and importing a pipeline to.
01:12:40.650 --> 01:12:41.620 Yeah, let's do that.
01:12:43.330 --> 01:12:45.280 And if I remember right, the export button.
01:12:43.410 --> 01:12:47.061 Think Johnathan Lee thinks we're scrubs? Because we we he likes
01:12:47.061 --> 01:12:50.712 the able version better. I think he thinks we're scrubs because
01:12:50.712 --> 01:12:53.050 you and I like the visual version there.
01:12:54.150 --> 01:12:57.085 If the visual version does everything I need to know and I
01:12:57.085 --> 01:12:59.921 don't have to learn another proprietary stupid scripting
01:12:59.921 --> 01:13:02.010 language, then I'm taking the visual one.
01:13:02.520 --> 01:13:03.120 Me too.
01:13:03.190 --> 01:13:06.558 Soon as the visual one doesn't do what I need it to, I will
01:13:06.558 --> 01:13:07.400 concede defeat.
01:13:08.260 --> 01:13:09.170 But until that day.
01:13:12.520 --> 01:13:15.760 You can export it to JSON and edit the JSON.
01:13:14.500 --> 01:13:17.133 That's I'm trying to remember where you do that, though,
01:13:17.133 --> 01:13:18.010 because it in here.
01:13:17.500 --> 01:13:20.530 Oh, it's a. It's the three little digits up, yeah.
01:13:19.370 --> 01:13:22.708 Oh, there it is. It wasn't the. Oh, because I went to a run last
01:13:22.470 --> 01:13:24.490 That the meatballs, it's the.
01:13:22.708 --> 01:13:23.170 time, OK?
01:13:24.340 --> 01:13:25.330 Meatball yeah.
01:13:24.920 --> 01:13:27.180 That they're actually called ellipsis.
01:13:27.670 --> 01:13:28.280 Ohh.
01:13:29.090 --> 01:13:32.400 My goodness, you learn something new every day.
01:13:30.980 --> 01:13:33.920 I mean, that's the obvious name. That's the.
01:13:33.010 --> 01:13:33.980 Meatballs. Cooler.
01:13:34.060 --> 01:13:37.290 I'm keeping Meatball definitely in my in my mind.
01:13:34.770 --> 01:13:38.310 Yeah, yeah. All chicken wings.
01:13:37.260 --> 01:13:39.090 The meatball. The meatball menu.
01:13:39.960 --> 01:13:40.360 Yeah.
01:13:40.440 --> 01:13:43.840 So we're going to call this a 2024.
01:13:41.310 --> 01:13:44.740 Wasn't that guy like a president or something, or a general or?
01:13:45.930 --> 01:13:49.030 Tests X portal.
01:13:46.320 --> 01:13:47.410 Yeah, it looks these.
01:13:50.910 --> 01:13:52.210 Thing on the default.
01:13:51.370 --> 01:13:52.850 Ellipses Grant is that you?
01:13:52.670 --> 01:13:53.780 Yeah, yeah.
01:13:55.810 --> 01:13:56.410 I like that.
01:13:58.100 --> 01:13:58.830 Umm.
01:13:59.970 --> 01:14:04.141 Right on agents. And instead of that guy, we're going to add our
01:14:04.141 --> 01:14:06.900 own custom task group, which was X portal.
01:14:10.280 --> 01:14:17.180 OK. And we're gonna just add a 20214 X portal test to that mode
01:14:17.180 --> 01:14:19.120 is gonna be debug.
01:14:20.260 --> 01:14:22.899 Sure. I don't care because I'm gonna give her that little
01:14:22.899 --> 01:14:23.490 ending piece.
01:14:24.890 --> 01:14:25.580 I think that's it.
01:14:27.570 --> 01:14:30.470 Just, uh, move that guy.
01:14:32.950 --> 01:14:35.000 Save it and queue it. Why don't we?
01:14:39.440 --> 01:14:42.420 Not sure how busy the build machines are right now so.
01:14:45.540 --> 01:14:48.130 No, it got picked up right away by Mr Bill 0.
01:14:49.770 --> 01:14:51.080 Means nothing's going on.
01:14:54.980 --> 01:14:59.030 Alright, so it's gonna pull the latest poll they'll ever drunk.
01:15:05.990 --> 01:15:09.989 In time, I say a long word like that. I I hear David Lynch in
01:15:09.989 --> 01:15:13.020 the back of my brain saying swirl the numbers.
01:15:14.240 --> 01:15:16.290 What's? What's that from?
01:15:17.450 --> 01:15:19.440 Sir, hold on. I can let me just.
01:15:20.000 --> 01:15:21.720 Just get a derail with training for that.
01:15:20.430 --> 01:15:21.420 Yeah, yeah.
01:15:22.140 --> 01:15:25.012 Well, I mean this has to run. It's gonna take a minute. So
01:15:22.190 --> 01:15:23.110 Entertain us.
01:15:25.012 --> 01:15:27.640 let's go see what David Lynch's number of the day is.
01:15:28.770 --> 01:15:29.070 Yeah.
01:15:30.600 --> 01:15:31.560 Like are are you?
01:15:31.140 --> 01:15:32.350 Wait, who's David Lynch?
01:15:32.790 --> 01:15:35.530 I the the Twin Peaks guy or not twin?
01:15:33.780 --> 01:15:34.040 About.
01:15:34.750 --> 01:15:36.240 Yes, the Twin Peaks guy.
01:15:36.330 --> 01:15:37.240 About the find out.
01:15:36.660 --> 01:15:37.070 Ohh.
01:15:38.610 --> 01:15:43.275 He does a video on YouTube
01:15:43.275 --> 01:15:46.990 has been doing it every day for some 900 days.
01:15:47.380 --> 01:15:48.600 That guy is delightful.
01:15:47.710 --> 01:15:50.300 He stands. He stands in his kitchen.
01:15:49.200 --> 01:15:49.890 How?
01:15:51.150 --> 01:15:54.397 Wearing sunglasses and he swirls the numbers in his little jar.
01:15:54.397 --> 01:15:56.730 And then he tells you what today's number is.
01:15:57.560 --> 01:16:00.410 I think I think Sesame Street's been doing that longer though.
01:15:58.120 --> 01:15:58.760 That's amazing.
01:16:01.220 --> 01:16:01.600 Yeah.
01:16:01.400 --> 01:16:04.030 Yeah, but Sesame Street's not a kooky old man.
01:16:04.070 --> 01:16:06.180 There's something about David Lynch that's just.
01:16:05.400 --> 01:16:06.770 I mean, you don't know that.
01:16:07.050 --> 01:16:10.503 I guess I don't, but there's something about David Lynch.
01:16:07.270 --> 01:16:09.120 Yeah, they.
01:16:10.503 --> 01:16:10.800 He's.
01:16:11.710 --> 01:16:12.510 He did a.
01:16:12.350 --> 01:16:15.800 I guess it's day 685, my favorite.
01:16:14.780 --> 01:16:18.482 I have seen his YouTube. He look for him on on when he mixed,
01:16:18.482 --> 01:16:22.243 when he's cooking quinoa. It's it's this whole 20 minute video
01:16:22.243 --> 01:16:26.005 that he made. It's in black and white. If so, if you like, you
01:16:26.005 --> 01:16:29.408 know your Twin Peaks and he menacingly describes cooking
01:16:29.408 --> 01:16:33.110 quinoa while he cooks it. It's it's hilarious. It's just it's
01:16:32.580 --> 01:16:33.250 He's.
01:16:33.110 --> 01:16:35.020 so medicine dark. It's so weird.
01:16:34.450 --> 01:16:38.210 Yeah, he's like a good director and everything, but that doesn't
01:16:38.210 --> 01:16:41.623 transfer to like the production quality of his videos, and
01:16:41.623 --> 01:16:45.383 that's why they're so good. It's like, does these, like, here we
01:16:45.383 --> 01:16:48.854 go for today's number camera pointed up from the counter at
01:16:48.854 --> 01:16:51.978 what looks to be a concrete bunker of a house and his
01:16:51.978 --> 01:16:52.440 kitchen.
01:16:53.530 --> 01:16:57.161 He's just like staring into the
01:16:54.190 --> 01:16:54.620 So far.
01:16:57.161 --> 01:16:58.780 sunglasses and his own house.
01:16:59.710 --> 01:17:02.983 And the camera is like peeking or the the microphones like
01:17:02.983 --> 01:17:06.423 peeking every two seconds, and you can hardly understand what
01:17:06.423 --> 01:17:09.640 he's saying. It's a delight. It's it's an absolute treat.
01:17:11.700 --> 01:17:14.070 Did it build? Ohh it's still new to restoring I see.
01:17:13.430 --> 01:17:14.500 It's yeah, it's cooking.
01:17:15.540 --> 01:17:16.860 Oh.
01:17:16.220 --> 01:17:17.950 Hey, immediately. Well, wait a min.
01:17:19.950 --> 01:17:22.170 Kind of. See the output for that. Thank you.
01:17:24.880 --> 01:17:25.990 Come on, come. Yeah.
01:17:25.410 --> 01:17:28.060 30 UI ohh X well X portal.
01:17:29.820 --> 01:17:31.490 Ah yes.
01:17:32.810 --> 01:17:34.700 This service stack versions.
01:17:33.080 --> 01:17:33.280 Right.
01:17:34.000 --> 01:17:38.370 Lasix service stack 13 three.
01:17:35.820 --> 01:17:37.160
01:17:38.160 --> 01:17:41.131 Yeah, alright. Well, I don't have time to fix that in the
01:17:41.131 --> 01:17:43.949 next two minutes, but you get the idea. If we fix that
01:17:43.949 --> 01:17:46.100 annoying thing, this would probably work.
01:17:46.840 --> 01:17:47.330 Cool.
01:17:47.950 --> 01:17:49.460 So that's pretty cool.
01:17:49.850 --> 01:17:50.610 And it's pretty cool.
01:17:51.620 --> 01:17:53.950 Well, applied learning as they
01:17:54.210 --> 01:17:56.210 Yeah. Thank you for this.
01:17:55.810 --> 01:17:58.560 We got two minutes left. We could watch David Lynch video.
01:17:58.970 --> 01:18:00.880 Just do it. Yeah, let's.
01:18:02.460 --> 01:18:04.990 Let's just see what today's number is.
01:18:03.830 --> 01:18:06.890 A making quinoa.
01:18:08.820 --> 01:18:10.600 I guess share the audio, you forgot to show.
01:18:10.400 --> 01:18:13.460 You have to Scroll down and look at that first comment.
01:18:11.810 --> 01:18:12.620 It's OK.
01:18:13.000 --> 01:18:14.090 Some magine it.
01:18:13.980 --> 01:18:18.012 Yeah, the analysis that there's a guy that had now has been
01:18:14.520 --> 01:18:15.320 Oh my God.
01:18:18.012 --> 01:18:19.020 doing analysis.
01:18:18.480 --> 01:18:21.655 Hey, before we before we see what the number is, anybody
01:18:21.655 --> 01:18:25.163 wanna put a guess in you? It's gonna. I'm I'm feeling a strong
01:18:22.430 --> 01:18:22.630 Yeah.
01:18:23.060 --> 01:18:23.890 Well, how?
01:18:23.390 --> 01:18:24.020 I.
01:18:25.163 --> 01:18:25.720 six today.
01:18:26.020 --> 01:18:27.450 I'm feeling a strong eight.
01:18:26.390 --> 01:18:26.680 OK.
01:18:27.000 --> 01:18:29.050 I'm gonna go with a 10.
01:18:29.820 --> 01:18:30.280 Oh 10.
01:18:29.910 --> 01:18:33.546 OK, alright. I don't know if 10s an option. I think it only goes
01:18:30.390 --> 01:18:31.500 10 two 110.
01:18:31.730 --> 01:18:34.010 The statistics lean to 8.
01:18:33.546 --> 01:18:34.440 as high as nine.
01:18:35.290 --> 01:18:35.620 Ohh.
01:18:35.460 --> 01:18:37.931 Oh no, there is 10. Yeah, Tens, 10s in there. OK, cool. Yeah,
01:18:37.660 --> 01:18:37.960 OK.
01:18:37.900 --> 01:18:38.240 OK.
01:18:37.931 --> 01:18:38.250 alright.
01:18:38.000 --> 01:18:39.210 OK, alright.
01:18:40.030 --> 01:18:40.600 Let's see it.
01:18:41.220 --> 01:18:42.990 10 as well, solidarity.
01:18:43.210 --> 01:18:43.950 Three on 10.
01:18:44.880 --> 01:18:49.240 OK, I'm. I'm sticking with six. That's OK. It's 5 clock.
01:18:45.190 --> 01:18:46.920 I think we lost a couple people, by the way.
01:18:48.040 --> 01:18:48.440 Howell.
01:18:49.450 --> 01:18:50.000 Yeah, there we go.
01:18:49.530 --> 01:18:50.260 They lost.
01:18:49.680 --> 01:18:50.010 Yeah.
01:18:50.660 --> 01:18:51.150 Ohh.
01:18:50.690 --> 01:18:51.160 What do we got?
01:18:51.410 --> 01:18:52.760 No way.
01:18:52.720 --> 01:18:53.310 Is at 10.
01:18:52.810 --> 01:18:53.720 I think it's 8.
01:18:52.830 --> 01:18:53.380 No way.
01:18:55.160 --> 01:18:55.700 It's.
01:18:56.510 --> 01:18:59.290 Ohh yeah, that's Richard. Hell yeah.
01:18:56.720 --> 01:18:57.660 Ah.
01:18:57.660 --> 01:19:00.190 Ohh that's crazy.
01:18:57.770 --> 01:18:58.460 Ohh.
01:18:59.560 --> 01:19:02.210 I think it's job alright.
01:19:00.210 --> 01:19:00.980 You felt it.
01:19:00.240 --> 01:19:02.800 Please statistics lean with a.
01:19:03.270 --> 01:19:06.935 If I went and bought a lottery ticket right now, what do I what
01:19:06.330 --> 01:19:06.660 Yeah.
01:19:06.935 --> 01:19:08.710 do I put in just top your head?
01:19:07.670 --> 01:19:08.200 Yeah.
01:19:09.250 --> 01:19:09.510 Yeah.
01:19:10.410 --> 01:19:11.930 12345.
01:19:12.240 --> 01:19:14.150 Ohh no I can't do that.
01:19:13.350 --> 01:19:14.770 I I'm a millionaire.
01:19:16.280 --> 01:19:18.030 That's my password. I can't use that.
01:19:16.610 --> 01:19:17.040 Alright.
01:19:19.910 --> 01:19:21.380 Thanks. Thank you, Brendan.
01:19:21.990 --> 01:19:22.940 Yeah, that.
01:19:22.010 --> 01:19:25.010 Yeah, I hope that this was enlightening.
01:19:22.400 --> 01:19:22.910 That everybody.
01:19:22.540 --> 01:19:23.130 Yeah. Thank you.
01:19:24.110 --> 01:19:24.990 Yeah, it was really cool.
01:19:24.410 --> 01:19:25.270 Yeah. Thanks.
01:19:25.800 --> 01:19:28.777 I hope that everyone will subscribe to David Lynch on
01:19:28.777 --> 01:19:32.139 YouTube and follow his channel. Watch the number of the day,
01:19:29.830 --> 01:19:30.030 Yeah.
01:19:30.990 --> 01:19:31.810 That just happened.
01:19:32.139 --> 01:19:32.690 every day.
01:19:32.790 --> 01:19:33.040 Yeah.
01:19:33.700 --> 01:19:36.570 You take one thing away from this. It's David lynch.
01:19:36.920 --> 01:19:37.400 That's correct.
01:19:36.950 --> 01:19:37.760 Yeah.
01:19:36.970 --> 01:19:37.260 Yep.
01:19:37.800 --> 01:19:38.050 OK.
01:19:38.290 --> 01:19:40.640 He'll have gained 15 subscribers.
01:19:41.090 --> 01:19:41.760 Yeah.
01:19:41.870 --> 01:19:42.280 Yeah.
01:19:44.620 --> 01:19:47.858 And the classic Twin Peaks is excellent, though that is a
01:19:45.020 --> 01:19:45.400 All right.
01:19:47.858 --> 01:19:49.030 crazy excellent show.
01:19:49.920 --> 01:19:51.030 The new season is OK too.
01:19:51.420 --> 01:19:54.625 Ohh, one last David Lynch related thing that I just
01:19:51.690 --> 01:19:52.660 It just just OK.
01:19:54.625 --> 01:19:58.384 remembered. He he cameoed as himself in an episode of Family
01:19:58.384 --> 01:19:58.630 Guy.
01:19:58.710 --> 01:19:58.900 I.
01:19:59.460 --> 01:20:00.060 Umm.
01:20:00.420 --> 01:20:01.470 No way.
01:20:03.240 --> 01:20:04.850 Uh, yeah.
01:20:05.500 --> 01:20:06.190 Pretty good.
01:20:07.320 --> 01:20:09.830 It's called how David Lynch stole Christmas.
01:20:10.430 --> 01:20:11.100 Umm.
01:20:10.590 --> 01:20:11.060 That's awesome.
01:20:11.680 --> 01:20:12.220 1.
01:20:13.490 --> 01:20:16.330 Alright, take care everybody. Thank you, Brandon.
01:20:17.380 --> 01:20:20.440 Yep. See you guys. Yeah, yeah.
01:20:17.410 --> 01:20:17.700 Like.
01:20:17.420 --> 01:20:18.330 We're good weekend guys.
01:20:17.800 --> 01:20:18.020 Yeah.
01:20:18.870 --> 01:20:21.200 Have a good weekend. You guys have a good weekend.
01:20:19.350 --> 01:20:20.960 See you on Tuesday.
01:20:20.240 --> 01:20:20.470 Well.
01:20:21.230 --> 01:20:21.780 My Brendan.
01:20:22.280 --> 01:20:23.210 Happy 4th of July.
01:20:23.960 --> 01:20:24.570 Happy 4th.
01:20:25.110 --> 01:20:25.980 Happy early for.
01:20:26.080 --> 01:20:27.220 In out.
01:20:27.150 --> 01:20:27.570 The else.
01:20:28.610 --> 01:20:29.380 There you guys.
01:20:29.180 --> 01:20:29.890 That it goes.