| Topic | Presenter | Summary | Duration | Tags | Certification Quiz | Captions |
| ----- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Repos | Eric Weathers | This video, led by Eric Weathers, explains Azure at a high level for developers. #Onboarding, #Claritynewhire, #training | 10:25 | #AzureDevOps, #TrainingVideos, #DeveloperTrainingVideos, #Repos, #ClarityNewHire, #NewHireOnboarding | Onboarding: Azure | Azure--Repos_AutoGeneratedCaption.txt |00:00:00.530 --> 00:00:04.658 - Alright, this video is to go over Azure, where were all the 00:00:04.658 --> 00:00:09.130 - repose are found where you can find most of the things that you 00:00:09.130 --> 00:00:13.602 - will need to be working on. Go from there. So the first thing 00:00:13.602 --> 00:00:16.354 - we do is we're going to go to 00:00:16.354 --> 00:00:21.196 - clarityhyphenventures.visualstudio.com. Once this comes 00:00:21.196 --> 00:00:25.390 - up. If you haven't signed in before, I'm doing it on 00:00:25.390 --> 00:00:28.172 - Incognito so it's Gonna ask me to sign in as well. So we're 00:00:28.172 --> 00:00:29.670 - going to go ahead and sign in. 00:00:32.320 --> 00:00:34.300 - And enter our password. 00:00:39.950 --> 00:00:43.772 - OK, so this is going to bring you to the main dev OPS screen 00:00:43.772 --> 00:00:47.048 - here with each of our projects. The majority of the things that 00:00:47.048 --> 00:00:50.870 - you're going to be working on is going to be here in this F 00:00:50.870 --> 00:00:53.600 - product. Clarity could also be one that you work on. 00:00:54.250 --> 00:00:58.254 - And then potentially, if you're working on an older project, or 00:00:58.254 --> 00:01:02.986 - just the DNN, it could be in any of these, like more client 00:01:02.986 --> 00:01:04.078 - specific products here. 00:01:04.080 --> 00:01:08.630 - So you know, for the most part, you're going to be here in Ceph 00:01:08.630 --> 00:01:12.530 - product. Could be in clarity a little bit if you're working on 00:01:12.530 --> 00:01:16.430 - connect or anything like that or just a specific client. So let's 00:01:16.430 --> 00:01:18.705 - go ahead and open up this green 00:01:18.705 --> 00:01:22.770 - button here. Sorry, this orange is for files and Repose, so it's 00:01:22.770 --> 00:01:26.508 - going to open up two files, so this is going to be where most 00:01:26.508 --> 00:01:29.979 - of the files are stored. So if you look in the specific repose 00:01:29.979 --> 00:01:31.047 - Here within the project. 00:01:32.100 --> 00:01:36.507 - The majority of what you're going to look at is in Ceph for 00:01:36.507 --> 00:01:40.575 - newer anything on a subversion 2021 or newer is going to be 00:01:40.575 --> 00:01:41.931 - here for a self. 00:01:43.160 --> 00:01:49.197 - Repo. Potentially there could be DNN things here under Tina 00:01:49.197 --> 00:01:53.527 - 9 hyphen, then whatever the project name is. Again, you 00:01:53.527 --> 00:01:56.558 - could also possibly find some DNN repose. 00:01:57.720 --> 00:02:00.244 - Inside project specific repose 00:02:00.244 --> 00:02:03.540 - Here so. What will show? How to 00:02:03.540 --> 00:02:09.703 - know that later? So the first thing to do is take a look. So 00:02:09.703 --> 00:02:15.898 - if we go here to set product so this is going to be any project 00:02:15.898 --> 00:02:18.376 - that is 2019.3 or older so. 00:02:18.950 --> 00:02:22.730 - For example, an will show where the branches are here, so we're 00:02:22.730 --> 00:02:24.305 - going to click on branches. 00:02:25.350 --> 00:02:30.025 - I meant stuff product and it defaults to mine, but let's 00:02:30.025 --> 00:02:34.700 - click on all OK, so here's some older, even older so. 00:02:35.690 --> 00:02:39.434 - For example, likes F 4.5, four point 6, four point 6.1, four 00:02:39.434 --> 00:02:43.178 - point Seven, 2018, three. So these are all going to be really 00:02:43.178 --> 00:02:46.922 - old, most likely, probably not going to work on them, but there 00:02:46.922 --> 00:02:50.978 - are a couple clients in here that you could need to find, so 00:02:50.978 --> 00:02:52.850 - let's skip on the archive here. 00:02:54.260 --> 00:02:58.400 - Mostly what you're going to look in here is support and clients. 00:02:58.400 --> 00:03:02.885 - And then here's all the clients on those, so this is our naming 00:03:02.885 --> 00:03:06.680 - convention, so it's going to be support slash clients slash the. 00:03:07.300 --> 00:03:11.794 - Acronym for for that client and then. 00:03:12.850 --> 00:03:17.398 - Either QA or staging. If it's an older client, could be devenue 00:03:17.398 --> 00:03:21.946 - 80 or prod or slash and then whatever the name of the 00:03:21.946 --> 00:03:26.115 - branches that you're working on. So let's let's grab one that's 00:03:26.115 --> 00:03:31.042 - active right now, so let's go ahead and grab center so you can 00:03:31.042 --> 00:03:36.348 - see. Here we have dev. We have you 80. If we grab potentially I 00:03:36.348 --> 00:03:41.124 - think that. All of these are on devyaty. Here we go. So bop is 00:03:41.124 --> 00:03:44.776 - on QA stage. This is the new newer naming convention we're 00:03:44.776 --> 00:03:49.092 - going with QA to replace dev and staging to replace you 80. And 00:03:49.092 --> 00:03:52.744 - then you still have your production. OK, so those are the 00:03:52.744 --> 00:03:56.064 - basic naming convictions there. You can see these little icons 00:03:56.064 --> 00:03:59.384 - here. Next to these branches, meaning that these branches have 00:03:59.384 --> 00:04:03.368 - policy is if you work with policies before going to go over 00:04:03.368 --> 00:04:06.688 - them. But but basically so let's click on QA here. 00:04:07.560 --> 00:04:11.061 - Actually, I'm sorry, let's let's go ahead and just 00:04:11.061 --> 00:04:16.118 - showing you may not be able to see this on yours, but if 00:04:16.118 --> 00:04:19.230 - I go to Bob and I think it. 00:04:22.040 --> 00:04:26.040 - Support clients and it's going to be here. 00:04:26.570 --> 00:04:32.324 - So if I take a look at the branch policy, so these are just 00:04:32.324 --> 00:04:37.256 - the policies that we have on this branch. So we have a 00:04:37.256 --> 00:04:42.599 - minimum of two reviewers, you as a requester for a PR into QA, 00:04:42.599 --> 00:04:44.654 - cannot approve your own change. 00:04:45.700 --> 00:04:49.168 - And whenever there's new changes then you still have to get like 00:04:49.168 --> 00:04:53.214 - if I say I review it and accept it, and then you can make 00:04:53.214 --> 00:04:56.104 - another change. I'll have to review and accept it again. 00:04:56.130 --> 00:04:59.514 - How to link a work item. So for example, an Azure ticket 00:04:59.514 --> 00:05:02.334 - whatever as your ticket you're working on for that feature 00:05:02.334 --> 00:05:05.718 - for that bug. Whatever it is, you would link that. That way 00:05:05.718 --> 00:05:09.102 - when they're all of these get PR Dinan deployed all of those 00:05:09.102 --> 00:05:11.358 - tickets can be moved to deploy to QA. 00:05:12.700 --> 00:05:20.028 - Current resolution, so basically if there's an issue. 00:05:20.030 --> 00:05:24.164 - We have to those all of those comments need to be resolved for 00:05:24.164 --> 00:05:28.298 - the PR is allowed to go in and then basic merge. No Fast 00:05:28.298 --> 00:05:32.432 - forward just means that it just sticks on top. So we do have 00:05:32.432 --> 00:05:35.294 - some required reviewers here. Any peer reviewers are required 00:05:35.294 --> 00:05:39.110 - so one from each and this is the overarching one. However, then 00:05:39.110 --> 00:05:43.244 - we have back end reviewers. That's going to be if any of the 00:05:43.244 --> 00:05:47.378 - files changed are not in the 08 UI folder. And then there's a 00:05:47.378 --> 00:05:51.512 - approvers front end. So if any if any changes were made in the 00:05:51.512 --> 00:05:54.056 - 08 it requires a front end of a 00:05:54.056 --> 00:06:00.300 - prover approver. And then and then optional is QA can go in 00:06:00.300 --> 00:06:03.070 - and review as well so. 00:06:03.070 --> 00:06:07.126 - If you have a back end in a front end, if you change 00:06:07.126 --> 00:06:11.182 - profiles, both of these will. So if I'm in back Enders, I'm also 00:06:11.182 --> 00:06:14.614 - NPR approver so that would satisfy this when you would just 00:06:14.614 --> 00:06:16.798 - need both this one and that one 00:06:16.798 --> 00:06:21.542 - OK. So I believe that that is it on branch policies. Obviously 00:06:21.542 --> 00:06:25.304 - you can't push directly into this, so you'll need to change 00:06:25.304 --> 00:06:29.066 - branches, but will have a separate video on git basics if 00:06:29.066 --> 00:06:32.828 - you're not. If you're not familiar with git, OK, so let's 00:06:32.828 --> 00:06:37.616 - go take a look back over here in the repost. So we're going to 00:06:37.616 --> 00:06:42.062 - take a look at Sevso. Seth has the same thing. Stuff is going 00:06:42.062 --> 00:06:46.850 - to be for any versions of stuff versions 2021 or newer, so if we 00:06:46.850 --> 00:06:49.244 - go take a look at the branches 00:06:49.244 --> 00:06:53.758 - here. Going to be set up exactly the same way where we have. 00:06:54.450 --> 00:06:59.510 - Support clients. And then the client acronym. 00:07:00.560 --> 00:07:01.510 - And then. 00:07:05.450 --> 00:07:09.680 - The branch name extensions here. OK, so um similar very 00:07:09.680 --> 00:07:10.949 - similar to there. 00:07:12.260 --> 00:07:17.187 - Where you could also be working if you're a back end are working 00:07:17.187 --> 00:07:22.114 - on connect the most of the new Kinect instances are going to be 00:07:22.114 --> 00:07:26.283 - here in connect V3. Set up exactly the same way with 00:07:26.283 --> 00:07:30.452 - support clients, so you should be able to find anything there. 00:07:31.520 --> 00:07:34.400 - Potentially on some of the connect if it's an older 00:07:34.400 --> 00:07:37.856 - version of connect, connect V2, some of the if I go to 00:07:37.856 --> 00:07:38.720 - Seth product here. 00:07:40.320 --> 00:07:45.886 - Some of the older versions of Ceph have connect within them. 00:07:45.886 --> 00:07:48.922 - So for example, let's go to 00:07:48.922 --> 00:07:55.080 - farm. Farm has connect inside of 00:07:55.080 --> 00:07:56.090 - it. 00:07:57.360 --> 00:08:02.079 - So you'll need to take a look at. That most likely won't be 00:08:02.079 --> 00:08:06.798 - working on these older projects, but if you do, some of the old 00:08:06.798 --> 00:08:10.428 - ones have connect inside of stuff, but starting last 20 00:08:10.428 --> 00:08:14.784 - ninth summer of 2019, we moved connect into its own app, made 00:08:14.784 --> 00:08:19.503 - it a little lighter, and the newer things. As of May 2020 are 00:08:19.503 --> 00:08:23.859 - going to all live here. We do have some connect projects that 00:08:23.859 --> 00:08:27.489 - will live on their own projects for, so for example. 00:08:27.490 --> 00:08:31.220 - I know like master graphics. 00:08:32.930 --> 00:08:37.363 - Master graphics has its own connect because it was just a 00:08:37.363 --> 00:08:41.393 - connectables and stuff or anything like that at the time. 00:08:41.393 --> 00:08:45.423 - We weren't doing anything. Any organization inside of the SEF 00:08:45.423 --> 00:08:50.259 - product project, so it got its own project and lives here. So 00:08:50.259 --> 00:08:52.677 - let's go quickly and find where. 00:08:53.450 --> 00:08:57.290 - Where you should be able to find any of that information. So 00:08:57.290 --> 00:09:01.450 - inside of teams, if you go to that project. So let's see I 00:09:01.450 --> 00:09:04.970 - believe spots he has it and you go to the wiki. 00:09:06.770 --> 00:09:13.970 - And if we go to connect info or really any any of this info then 00:09:13.970 --> 00:09:16.850 - you should have links to the. 00:09:18.210 --> 00:09:22.626 - You'll have links to the to the specific branches inside, so any 00:09:22.626 --> 00:09:27.410 - of these should link you over. So for example, if I go to 00:09:27.410 --> 00:09:31.520 - connect. Connect has these linked as well. Here's the clone 00:09:31.520 --> 00:09:35.940 - URL. So for example the clone URL you can see is connected V3. 00:09:36.650 --> 00:09:40.992 - So here is here's my clone and then obviously going to clone in 00:09:40.992 --> 00:09:45.668 - to develop. But now you can see that this is where a DI slash 00:09:45.668 --> 00:09:50.344 - dev would be in fact. Actually I said it was spot see, so let's 00:09:50.344 --> 00:09:53.118 - go find. Spot see one. 00:09:55.050 --> 00:09:58.470 - Let's go check branches really quickly. 00:10:00.750 --> 00:10:04.846 - OK well spots is not in here so this is a die so will need to 00:10:04.846 --> 00:10:10.190 - clean this up. But ultimately the goal is to get all of the 00:10:10.190 --> 00:10:13.799 - correct branches into this information. Here inside of the 00:10:13.799 --> 00:10:18.611 - wiki and teams. OK, I think that's it for Azure. Repose will 00:10:18.611 --> 00:10:23.022 - have another video on cloning from Azure and things like that, 00:10:23.022 --> 00:10:25.428 - but that's it for this one.