[Music] hey everyone it's justin thank you for watching in this video we're going to continue talking about devops and we're going to connect the dots between the azure devops pipeline and what that pipeline looks and looks like in service now so to refresh your memory there is a video for this but if you don't haven't seen that video in azure devops i've got a pipeline configured and that pipeline has three stages to it okay so it has a build a test and a deploy stage and in a previous video i showed the yaml configuration for how this talks to servicenow and how it might process moving your code from build to test to production okay so this is the azure devops side of things now on the servicenow side of things there is a mirrored pipeline so we basically when we connect servicenow to azure devops it will once we run that pipeline one time it'll automatically build out the pipeline for us and that's what i want to show you today so what i'm looking for is pipelines over here on the left hand side in our in our menu pipelines you can have as many as you need you can have pipelines per product per application per team per system whatever it is i have one set up for this showcase in san diego so i'm going to pull up this particular pipeline and notice it has the same stages that were over in the one i had in azure devops so i got a build i got a test i got a deploy stage and like i said you run the pipeline once servicenow will automatically detect that and will build this out for you you used to have to create these manually you don't have to do that anymore so let's start with build take a look what's going on with build we can see that we can specify what type of stage it is i left that out of the box and touch it we can specify the order member order and service now just shows uh we're just default how things what order they show in when we're looking at the list stuff like that if you notice on the previous screen it was kind of backwards uh one was at the bottom or bill was at the bottom deploys at the top i could fix that by changing the order but importantly this particular one has to match what is over on the orchestration task or task level or stage in azure devops this seems to match exactly so what you're seeing here if you've seen that yaml video the stage is build the job is build one so that's the relationship there and then servicenow would automatically put this slash in there when they detect this so i built that and it has a link to the actual task notice up above we have the option to if we wanted to have change control on any step on any orchestration task we can enforce change control i don't want it on my build step um test is going to look very similar to the build so not a lot going on there but there's my orchestration stage plus job name and i have the same option for change control there didn't do it and let's go to the fun one so this is the deploy step so there is change control on this particular step now there's another feature called change receipt change receipt what that'll do if this is enabled um and you can check the box and it'll just you know it'll enable that is it'll open the change and log it but the pipeline will continue so it's not going to hold up the pipeline for change control so that's what change receipt does the other items here configuration item you could just associate a configuration item with the changes as they get created change approval group and the change type um are all configurable so you can have different groups for different pipelines that would be assigned to that change request that gets created and for the change type you can do standard normal or emergency now i'll warn you when this gets picked up as a change and we'll show that in the future video um it'll be a type or a model of devops so um and it's gonna have a different flow uh i think i showed that in my first or second video it's a different flow associated with the devops flow or devops change but the change type are the standard out of the box model standard normal and emergency and i left mine as normal now you can pick a template out for that change so you can say if anybody has templates built out you can use a template and it'll automatically populate the values that are configured for that template so let's just go ahead and look at one of these we gotta change devops maintenance window itsm let's take a peek and see what that template does we'll just go ahead and open this and yeah we'll leave without saving i don't care if it's a demo um so this particular change template that someone has configured probably some demo person will have a certain number of fields automatically have a value so if we were to use that template as part of the change request coming from azure devops it'll go ahead and populate those fields with those values so you can see your assignment group backup plan service cab required configuration item right all this work that your teams would have to fill out right so the idea um ideally ideally the idea is we're saving our team's time by going ahead and applying a template to our change as it comes over from azure devops last piece to notice here is the change controlled branches so you can turn on a change control for a particular step in the pipeline but then you can also specify hey it's only going to be on the master branch or the main branch or it's only going to be on x y or z branch or something like that for demo i just have it a star meaning it's going to cover every branch when someone makes a commit and it's going to kick off the change process hey guys real quick i was about to stop the video and i forgot to sexually click on the actual pipeline um ui so you could see it within service now so that was like the big lead-up point everything recorded great so i didn't want to really go re-record it so here's the pipeline ui this is what it looks like visually graphically in service now so i've got a build step that starts and finishes i can go and look at my artifacts i can look at my commits associated with it my work items and for that test and deploy stages you can see there i've got the same options we can look at test results i don't have test results or software quality actually configured but i can see yes this test step ran yes this deploy step ran you can even click on here and view the change request that's associated with it that automatically got created but that's the visual representation of the pipeline ui within servicenow so back to the end of my other video so that's how we mirror or duplicate the pipeline in service now to match what's happening in azure devops and what you'll see in a future video is when that happens it's going to go ahead because of this particular configuration it's going to run through the pipeline but when it gets to deploy which is this phase right here it is going to enforce change control and as you'll see in future videos we even have some options on how how enforced that is do we want to auto approve or do a manual approval or do different things with it we've got lots of options so i hope this video is helpful if you liked it please subscribe or like the video share it with somebody who you think might be interested in devops and until next time don't forget to always be learning [Music] [Applause] [Music] you