hello my name is Isaac Bartz outbound product manager for servicenow and today's video is going to be going over how to get started with devops change velocity as a brief overview we want to remind you of what the devops solution is servicenow is not taking over any of the tools in your existing devops tool chain in actuality we are integrating with your existing planning coding orchestration tools and so forth to be able to pull in key metrics key events and key commits that are happening from your developers our goal once we have these Integrations created is to make it as easy as possible for your development teams to put their data into the servicenow platform and the servicenow's common service data model and that will allow you to make decisions and provide Analytics such as how is your development team performing how is your it team supporting them automate change requests have a better auditing and compliance Trail and overall improved visibility to the key metrics of the most important software applications and projects your company makes with that said let's get started to start things off make sure that you're on a San Diego instance of servicenow or later you'll also need to install devops change velocity version 135.4 or later and we'll show that next as an example we're bringing up four of our most commonly used CI CD tools gr GitHub Jenkins and Ado this is not an all-inclusive list it's just four examples but this should give you an idea of the type of information you'll need to gather to complete the Integrations for example jira you will need the URL to your jira instance and then the jira account username and API token that servicenow will be utilizing GitHub very similar setup and Jenkins and Ado have a few changes as well keep in mind along the bottom you'll see optional servicenow mid server so if you have an on-premise version of let's say Jenkins you will need a servicenow mid server to handle communication at that point most of these Integrations are cloud-based so a lot of times that mid-server is not necessary at all to get started you'll need a subscription to itsm Pro All servicenow itsm Pro customers receive devops change velocity and devops config to activate devops change velocity you have a few options going to the servicenow store is one way to check your entitlement and verify that devops change velocity is available to you will receive the data model all Integrations required to run devops and the reporting which is called devops insight clicking your products we'll see if you have a valid subscription and can activate it another approach would be to go to your plugins or newly renamed to applications in servicenow checking devops brings back plugins you can see here in our list that we do have multiple different devops plugins available but in this case here we're going to be specifically looking for devops change velocity I already have it installed in this particular instance but this would be the one that you're looking for on the size of your instance it can take an hour or two to activate that so make sure that you have time and are activating it beforehand and before you want to get into the configuration once the installation has finished do a quick validation by typing devops into your filter Navigator now you should see all of the new tables that are part of servicenow's common service data model you'll see where your pipelines will be coming in you'll see your commits your artifacts repositories and so forth this means you have now successfully installed servicenow's change velocities plugin one final bit of housekeeping this video is not meant to be an all-inclusive video there is some Nuance between each of the tools in your CI CD tool chain and how to get them connected to servicenow with that said please make sure you go to docs.servicenow.com devops devops again and reference this section to connect to third-party tools any of the settings for bitbucket GitHub gitlab Jenkins that are specific to those tools will be in this documentation for instance Azure devops requires you to go to the marketplace and search for servicenow devops and install the plugin on the Ado site itself this is just an example of a tool specific requirement that you will have to do for each individual tool so just again verify your docs site look in the documentation for what you have to do on the tools side to complete the setup next we're going to wrap up the one-time setup these are some platform settings that you'll need to configure for devops regardless of what CI CD tool you'll be using there's two users that are required to run the servicenowdevops solution that is the devops dot system user and the devops.integration.user let's take a look at these and see what roles these users have first the devops dot system the required role will be SN underscore devops dot admin next devops.integration.user acquired role will be SN underscore devops dot integration the rest of our setup is going to be done in What's called the devops change workspace so at the top of your servicenow instance click on workspaces and because we have the proper plugins activated you should now see the devops change workspace this is a guided setup of sorts you can see here setting up accounts assigning roles tasks creating applications connecting tools and also getting into the change policy itself is all available to us here in the devops change workspace let's begin by setting up the passwords for the accounts but this is very very important for this one step only of setting up accounts you have to be in What's called the devops data model scope again please change your scope to devops data model at this time the rest of the setup will be doing it in global just for the passwords we need this scope though okay so setting up accounts the username is our integration user let's set that password next we've got our devops system user and we'll set our password again I'm going to use the same one that I use for the integration user at this point we have the option to create more users and give them whatever role is necessary at this point you can choose assign role pick another servicenow user and select what role they have whether it's an admin or it's a viewer or a user of some sort but we have all of the users we need so I'm going to cancel this and go back to the home page of the devops change workspace let's continue the setup from here now that we're done with our passwords we do want to change the scope back to Global so make sure you do that and from Global we will continue the rest so you can assign roles we've already kind of done that we have all of the users we need we don't need to add any more users but that's where you would do so at that time or assign devops permissions to an existing user of servicenow assign tasks is very nice because what you can do here is you can assign a task in this case we're going to pick and devops admin that's fine and we want to alert them that they need to connect to another system we'll pick connect Azure devops and there is a due date foreign so at that point this is a way that you can use the workspace to create tasks and communicate with individuals who have credentials if this individual has credentials GitHub or Azure devops you're alerting them that you need further assistance but hopefully uh you already have all the passwords and everything you need let's go back to the home screen here now that our one time setup has been completed we're going to connect to Azure devops with the link called connect a tool notice there's different types of tools we've got planning tools coding tools software quality summary tools orchestration is what we're going to use today so Azure devops is really kind of a One-Stop shop it's Unique in that sense where customers using Azure devops that is their planning coding and orchestration Tool altogether adding a tool name is where we start and I'm going to go ahead and click the next button from here we need to enter the Azure devops instance details so the instance link itself and then the personal access token so you may need an Azure devops administrator to give you that token it has successfully connected there are permission checks here that were done and we can see here that we are connected to build release your Pipelines good confirmation message we can go ahead and continue clicking on the connect button will bring us to the next screen which is asking us who is the individual or username that we're going to be using to send data and we don't need web hooks but if you need near real time fetching of your Azure devops commits and pipelines you can set that up with web hooks but we're going to skip this because we are okay with the the out of the box nightly poll and that'll be fine for our our setup now we're going to select the plans to track so what plans are associated to your application and in this case here we have Parts Unlimited yaml 2 and that's where our planning is taking place so our work items are coming in what repositories are we going to be tracking this is a pretty fresh Ado instance so I only see one repository and that's all I'm going to select now the pipelines you can select all of them at this point if you want but we're only going to select one we're only going to be monitoring that one particular pipeline at this time and here are the services to pipeline steps so on the left hand column you'll see in gray that the steps are coming in from azure devops so deploy deploy application build testing and validating well let's get that connected to servicenow what does this step in servicenow entail so for deploy deploy application we're going to say deploy and test now connecting it to the cmdb what service are we going to be utilizing and all of its corresponding CIS that's extremely powerful because a developer is not tracking Ci's or network outages but now we can this point we're we're going to move forward you can see the tool connections and the import requests the plans that we're connected to the repositories the pipelines and also a history of your tool connectivity so this is very powerful for troubleshooting if necessary we've already done Discovery in our initial connection for the tool just know that that's there again if you need to go back and pull in further historical data from your your tools so Discovery allows you to do that and also entering manual configuration mode this is if you needed to create any changes in your credentials but also if you wanted to disable this connection so if you were to disconnect it it would no longer continue pulling in data on an hourly basis let's talk more about connecting tools just really quickly want to state there is always a little bit of nuance inside each and every one of these Wizards so when you're selecting them go back to docs.servicenow.com if you need any help beforehand to proactively collect the data you need for each one of these individual tools while you're going through the wizard here we do walk you through those steps but it's always a good idea to make sure you look through the documentation first just to be better prepared and have any additional information that one of these tools might require for the most part they're all very similar but again there are additional steps needed in some of the tools now that we've gone over the platform setup and connecting your tools we're going to create applications applications are a container of sorts that bring together your coding tools to your pipeline tools to your orchestration tools to your planning tools and creates an application in service now to make sure all of the data is connected properly let's see how these applications work now that you have at least one tool connected you can create an application go ahead and enter an application name at this point as a reminder an application is simply a collection of one or multiple CI CD tools and the data that they're bringing in we want to combine them underneath the application so you will need to select business app and at this point follow one or more recommended navigation points so associating pipeline also shows up underneath the pipeline tab along the top associating plan same thing you can click on the recommended action or simply go to the plans Tab and Associate that plan if you need to connect an additional tool you can do so at this point let's say your planning is actually happening in jira so if that connection is not already made you would need to connect it at this time let's go ahead and Associate the proper plan the scenario we're working with is Ado is the planning tool so at this point we're going to pull in the plan in this case it's Parts Unlimited yaml and we will go back to the beginning of the project so this has been back to August it's when that planning started and we will pull in the historical information of course the information will continue to get populated going forward from that point now we're going to pick the pipeline so associating the pipeline is going to allow us to select which particular pipeline needs to be connected to this app is the Parts Unlimited and that is actually also the release so I'm going to bring in both yep I'm going to go back and pull in at least from August and we can see the pipelines are now showing let's pick the repositories that we want connected to this application this point we have one repository and that is in fact Parts Unlimited same thing pulling back enough information so that we can have insights and go forward let's go ahead and import that data connecting a tool talked about that really briefly let's say you were doing your coding in another application in another CI CD tool if you don't have it already connected you could connect it at this point here and it would walk you through the wizard in this case here it would be for GitHub now look at automatic change creation so this is the point where service now creates a change request where in the pipeline do you want servicenow to do that so we will pick our main pipeline and this is showing us the four steps that that pipeline has so this is coming from Ado right now the Change Control is false we're not making a change request for any of these steps but we want to change that so on deploy we're going to enable this to be the step that creates the change process so it is a ploy and that will show up in the change request the service so connecting to your cmdb what what Ci's what servers what databases all come along with this and that information is stored Within servicenow so picking the service of fulfillment will allow us to combine that data here's where we're given a script this step is specific to Ado we'll need to copy this script and put it into our pipeline configuration file so we can copy it and at that point we're even able to change it and add more tasks more Fields more values if we like so we've created our first application for our last step we're just going to go over a few other things about the workspace that might be of interest to you and we're also going to show how insights can immediately begin reporting on your development performance and your change management performance a few more things to quickly point out about the change workspace the navigation over here does give you the link for some policy guidance for your change approval and this is going into the conditions and criteria that you might want to put into your flow most of the time there's three outcomes either the change request is going to be automatically approved automatically rejected or sent into a manual Change review process of some sort because there wasn't enough information for servicenow to make that decision we do give you the link here for the default devops change request flow so let's take a look at that we're not going to go into all of the different variables and lookups that it's doing but you can just briefly see here we've got things like assignment groups we're definitely looking up the change request record we're receiving information from your CI CD tool chain or updating the change request setting things like the the window where that change needs to go through so this is an extremely comprehensive workflow process we definitely recommend you check out all that it's doing again this is the devops default change request flow back to the workspace we want to talk about automatic change creation we've seen this already in a previous step that we were doing in our configuration but it's worth noting that you can come back here and make further changes so we'll go ahead and select a pipeline and then here you're going to select your step so the reason for coming back here would be if you wanted to change the servicenow change request creation at a different point so if something changed inside Ado if you added another another step to your pipeline you would be able to modify this step here and tell Ado when to Signal service now to create that change request for further navigation along the left hand side of the devops change workspace you can see all of the applications you've created next will be tools and so from here directly you could connect your planning tools coding tools orchestration tools so on and so forth and finally let's look at insights insights is the reporting functionality of the devops solution soon as all of your tool connections have been made and you've imported some historical Data Insights allows you to view your performance right away I'm gonna go ahead and filter one particular application from here I can see such information as my deployment frequency the work items that have been completed I can also filter down further by a specific Repository by a specific service inside service now and connect it to the cmdb I can even drill down into the specific configuration items connected to these services what you see here is an overview of what we call the Dora metrics Dora was originally created by Google Cloud to track the performance of their development team and how the development team was working with it you see information here such as our volume automated versus manual changes are there any changes awaiting approval and then performance on the development itself how frequently are we committing how many active committers are there other information such as the commits without work items it's best practice in the door metrics to have commits with work items so making sure that you're not creating any unplanned code commits so again insights is live and operational just as soon as you get your tools connected last but not least the administration tab of the devops change workspace allows you to see the system Health dashboard so how many events are you processing which tools are there coming in from in this case here I just have one orchestration tool connected right now but that would certainly grow connectivity giving you a history of any connects or disconnects troubleshooting including error logs your inbound events and how they're processing where they're coming from all of your payloads your pipeline change requests and any registered callbacks the system configuration does have some properties for you to review and of course your user group roles your tasks for users and groups as well so this is the administration tab of the devops change workspace we hope this overview of servicenow's devops change velocity has been useful we certainly want all of our TSM Pro customers to begin adopting this technology and if you have any issues in connecting to your tools please open a support ticket and we can help you with any of those unexpected challenges if you want to watch an end-to-end solution we also have the adoption video in this website please watch the adoption video that will show you a fully configured solution operating from end to end thank you