[Music] hey everyone it's Justin thank you for watching in this video we're continuing our devops discussion and I want to go over the configuration of a integrated devops tool and what that looks like in service now so in previous videos we talked about the overall concept showed you a pipeline we talked through configuring that and that was Azure devops so I'm going to show you on the servicenow side what the Azure devops configuration looks like so to do that I'm going to start with the devops menu within servicenow so you can see here I type in devops and I can see all the different things that I can do in the devops application in servicenow we're going to get to the pipeline in a future video but right now I want to talk through one of the tools that I've integrated with this particular service now instance and that is azure devops we might do jira in a future video or some other tools but when you configure one of these it's actually much simpler than it used to be in the past I can vouch that personally because I've configured this with every release of servicenow setting up Azure devops I basically provided some credentials I went through a menu item that you'll see here let me just click create new essentially I basically gave the it gave it a name picked from a list of things that I wanted to integrate and one of those was Azure devops so if you haven't seen these before this is what's out of the box that's what's out of the box no that's that's without a box point in the right direction so sonar bit bucket GitHub jira Jenkins gitlab jfrog Azure devops and Agile development 2.0 this is the servicenow Agile development 2.0 so I did Azure devops and I gave it a URL username and for Azure devops to use a personal access token that's what's supported to do the integration so what that integration looks like in service now once you've configured it it will make the connection and then you run a discovery so if you see here I've got a discover button so Discovery is these jobs these scripts that are going to run and find different things so it found uh one plan which is really a project in Azure devops one repo or repository which is I've I've named the whole project is named San Diego showcase as you may have seen in a previous video any orchestration tasks that's part of the pipeline that I've showed in a previous video on Azure devops and then we have a listing here for the pipeline itself so these orchestration tasks are actually part of this Pipeline and then I've got basically a running history of all the connections that have happened with that particular tool so when you come in here and you discover it will go do these import requests and it'll run these Imports and it'll pull in the different things so if I move my head you can see the different capabilities it's going to look at planning it's going to look at code it's going to look at orchestration and if I was using the artifacts which I haven't played around with yet in the devops app it would pull in any artifacts as part of that Discovery piece so if we click on plans here we can see I've got that San Diego showcase but within the actual plan or a project you've got work items you've got features you've got releases and applications so you can see here me testing and doing some stuff different release versions features that might have so I did a netback and that map to a feature and then I've got an app so this app is what lives in service now now it's part of the cmdb so we've Associated this planning tool with the devops demo app that I created in my cmdb in this particular instance next up I've got the repo or repository uh not much going on there other than commits so you can see on the branches yeah so you see all the branches that I've done through demos and stuff like that all the commits that I've made as part of my testing and troubleshooting and getting stuff done and if I had any import requests they'd be showing there so that's what's giving you insight into all that stuff orchestration tasks they're pretty much straightforward I'm going to go over these in a future video but if you look around my head here they're essentially build test deploy which you've if you've watched the Azure devops pipeline setup you can see how that kind of mirrors what's over there and then in the future video we're going to dive deep into the pipeline configuration because that's where we're going to do stuff like configure Change Control to set up templates uh look at what branches are monitored and stuff like that but what you just saw is how the Azure devops looks on the service now side so connection was made we discovered everything we imported different things and now there's web hooks that get set up when you're configuring it so that when something happens in Azure devops we're notified in serviced now so if there's a work item a new work item a commit or something like that those are automatically being sent to servicenow and of course a servicenow wants to talk to Azure devops it definitely can I hope you found this video helpful if you did please like Please Subscribe or share it with somebody you think might be interested and until next time don't forget to always be learning [Music] thank you [Music]