[Music] hey everyone it's justin thank you for watching in this video i'm still talking about servicenow devops but i want to pull back and talk about an earlier phase of devops right so when you're implementing this you're probably going to do a crawl walk runner approach you're going to do your integrations but not every team is ready for automated pipelines and so you might still be working through your existing change processes and what servicenow did in san diego is they made it so that you could follow your existing change processes but still get some of this devops data associated with your change request so notice on the change models i actually have one here for devops right this is the different workflow or whatever that devops changes will follow if i were to come in and create a change request and say set the category to devops let's go let's go ahead and put some information in here too test change or demo change we're going to demo a change to the world and look above my head i've got this button for add devops data so your teams can come in and they can click this add devops data button and then they can select the type of data they want to add so i've got artifacts released or built and this is going to change what i can pick on this next drop down so i'm going to look at a release i've got one set up for my san diego showcase of course and if i hit next now i get to go pick the different things that i might want to associate with this change request this was happening automatically in my previous videos when we're using pipelines and automatically associated work items with a particular change request but let's go ahead i'm going to associate this particular work item and let's go ahead and pick a couple of commits here too we'll do this this commit and this commit will say so this work item uh or those commits are going to be associated with this particular change request so i'm going to check the boxes again for those and i'm going to click submit and now those commits will be part of my change request and everybody will be able to see those in the related lists at the bottom of the record so pretend i was a good change submitter and i filled out all these fields perfectly with all the information i need or i use the template right so if i wanted to apply a template i could use one of those there let's do this demo change template that you see there at the bottom and it'll automatically populate some stuff for me um yeah so i've got a nice little plan there but the part that i wanted you to see let me kill this here and i'm going to save the change now that we've applied that template associated those commits that didn't work items first but actually associated commits those are going to show up now when i save this request when someone comes in here to review this change request so if i look down here i've got two fields of course they're right behind my head work items and commits and if i click on those i'd be able to see well there's my work items and there's the commits that i was playing around with and associated with this particular change uh in my heads in the way there so you can see the commits and we can see the work items showing up there so that is new to san diego if someone did need to come in and say hey uh there's another commit or there's another work item we want to associate with this change request they can come in they can hit the edit button do the same screens that i just showed you but again this is for those that aren't ready for those automated pipelines the changes getting created and approved automatically you can still follow your existing change process create your changes user templates and then associate your devops data with those particular changes so you still have that insight and visibility when you're running the change process of what is actually involved what artifacts what work items what commits are associated with that particular change request from your dev teams i hope you found this video helpful if you did please like please subscribe or share with somebody who you think might be interested in servicenow devops and until next time don't forget to always be learning [Music] you