[Music] hey everyone it's justin thank you for watching in this video we're going to continue the conversation around devops this time i'm in azure devops and i've connected azure devops to service now devops so all of my planning items my work items my tasks my issues my epics those will go from azure devops over to servicenow my code commits my code reversions my code comments all that comes from azure devops over to servicenow and in this video we're going to talk about pipeline pipeline is the code orchestration it's what moves your code from sub production from tests to uat to production and all that stuff and we use that we use in uh azure devops we use the pipeline in order to make that happen so let's dive right in there's some key concepts i want you to see here around pipelines and i'm going to dive into a yaml file so it's going to get a little bit technical but even for those that are not technical i think this will be important for you to see number one we've broken up the pipeline in the stages i use for my example and this is just an example build test deploy so assuming there's going to be a build phase then you might migrate that to a test environment and then you would to go ahead and deploy that in here when we start the build phase in azure devops in the pipeline we're going to send a message to service now and say hey we started so you can see this little start phase so it knows so servicenow is like okay that started at this particular time then we're going to do something and here we're just saying hello world right no big deal and then after we do something we're going to signal back to servicenow hey we completed all right so you can see the little completed phase right there that is essentially the basic structure in the pipeline to let servicenow know a stage or a phase has started and then completed and this is going to be important in future videos when you see this being mirrored over in a servicenow the next stage is test very similar format so i've got hey i started hey i completed and i do something in between like hello world same thing as i did in my build step into my test step the last piece that i do on my deploy step is i say hey this is actually um going to be a change acceleration so this is where the the cool stuff comes comes in we're going to open a change request and we're not going to move this forward in the pipeline until that change request has been approved now i have nothing else going on in my pipeline i said you know you would actually do something you would do some orchestration but for demo purposes i'm just waiting on service now to approve my change and then my pipeline finishes so the pipeline will actually sit there and be running and you'll see that again in a future video now before we get to that future video let's take a look at how i did this how i got this stuff into my yaml file in the visual studio store there is a service now um package you can install and it'll come with these little tasks that you can add to your yaml file so the one that i was using was this agent job notification so i pick my servicenow instance i tell it what upstream job and i tell it it's my starting or completing and the second one that i used was that change accelerator so you can see down here i've got this server change accelerator and i use that to let servicenow know that i'm going to actually make a change or i'm requesting an actual change now in this you can provide different um change request details so in this box i pointed to the wrong one there so i can actually add different things in like implementation plan back out plan all that stuff or you can use a template over in servicenow but that's where you do that over on this pipeline setup so what will end like this for this video i want to show you what a pipeline actually looks like so you can see there the different stages as they represent uh for one that has it gets done and i'll just open one up so you can see how that would progress i've got it build i've got test and i've got deploy right there and so this deploy step the way i have it configured and the way we'll show it in a future video is it's going to open a change requested service now and if you saw my change policy video depending on some criteria it may automatically approve the change or it may assign it to a group for approval thus at that last part stopping the pipeline until someone does that approval so big stuff to come on this one i hope you found this video helpful if you did please like please subscribe or share with somebody you think might be interested and until next time don't forget to always be learning [Music] [Applause] [Music]