okay so as I said my name is Mike I'm an outbound product manager for uh itsm and devops based in Melbourne and uh with me today I have some colleagues who are going to be helping out so we have Gary who's based in India we have Central also in India and and G2 as well from product success in India and then we have Alex who is in Sydney so uh sorry I'm just having a look at the chat is there something I need to do oh okay cool okay got it all right um so we also have with us um a couple of folks from uh one of our key partners for devops TM Labs um Christian and Daniel so they will also be helping out with today's session all right so um the agenda is we'll we'll give a very brief intro to to what devops change velocity is and the some of the challenges and the problems that IT addresses and talk about our approach around devops the majority of the time will be spent on the lab so I'm hoping that we'll have over an hour to actually get through the lab and then we'll come back about 10 minutes before the end and and we'll wrap up so the first thing you need to do so I've put this link in the chat if you haven't already reserved an instance uh to do the lab then please do so click on that link and put in your a name email address and reservation code and then an instance will be allocated to you for this session these instances will only be available for uh the next uh two two and a half days um so that's in case you want to try and do the lab after this session in your own time you you are welcome to do that but just be aware that the instance instances are only available for a limited time so the uh the idea is to wake up your instance now because it may be hibernating so that when by the time we get through this the initial slides and kick off the lab that your instance is is actually ready to go all right so we'll uh while you're doing that we'll just kick off with uh some intros and um some of you who who have attended uh demos on devops before may have seen some of this information but for those of you who haven't uh we're just going to outline uh what we what our products do in terms of the value so typically when we look at customers today that are you know moving to cloud and and they've got development teams that are running devops we do see some some issues where they're trying to scale up devops and and often they're having some challenges so one of the challenges is there's a lack of visibility and traceability around the data so this is really caused by developers having their own set of tools so developers might be working in in tools like jira uh Jenkins you know Azure devops there's a host of different tools and um from an operational point of view the folks that are looking at the changes that are coming through from those pipelines uh are working in in servicenow and they don't have access to the data in in those tools so that can often cause um a wall between developers and operations because they don't have visibility of all the data so developers sometimes have a fully automated CI CD pipeline so they're you know they're building they're testing and they're deploying code through and fully automated pipeline but when it comes to change management they sometimes have to manage that manually and that can cause wasted time and and what they see as as wasted effort but obviously we need changes to to be created and we need changes to be compliant and we need to make sure that we're meeting all our obligations when it comes to Regulatory Compliance Etc so how do we get around those sort of issues and how do we ensure we can increase the delivery and velocity with devops but all at the same time stay compliant with the change management process so when you look across some of the personas and the roles involved the change manager in the middle there is is often hit by an increasing number of changes that they have to deal with and obviously make sure that everyone's complying with the regulatory requirements um and how do they do that unless there's some automation which which can help them the developer as I said is often having to swivel from their tools into servicenow to put all the data into the change and spending a lot of admin time on on these sort of tasks and from a development point of view you often have the engineering manager looking at their team's performance and their in and trying to get insights into how they're doing but they don't always have visibility across the end-to-end value chain so a lot of these roles have um these personas have have some issues around how how it's managed today so what we do with devops change velocity and the solution that you're going to see today in the lab is we say let developers stay in their own tool sets so some of the tools you can see on the left there jira GitHub gitlab Jenkins and the tool we're going to be dealing with today which is azure devops and we will integrate those tools into service now and we will normalize the data that gets ingested into the platform and that will allow us to do two really important things number one on the right hand side it will allow us to populate the data that we get from those tools into our dashboards the insights dashboard and we'll have a look at that during the lab and that allows us to see how we're performing in terms of devops and gives us some really key metrics and kpis that we can track over time so we're getting to see that and the second important thing is that data can be used as inputs to our change approval policies in order to automate the change process so once we automate the change process we remove those barriers and we remove the manual effort required from everyone involved and it allows us to really increase delivery but maintain the compliance on the government governance that we need for change so we respect the systems of record so typically you know a developer might be working in tools like jira where the stories features bugs Etc are created and that that really describes why they're doing the work so that the user stories contain the why am I doing a change and then the actual changes themselves are the what which would be in their in their code commits usually in a git repo and then the changes get built tested and deployed and then obviously from a servicenow point of view we have the operational service operational system of record but we also have all that data so we have access to the commits the user Stories the vulnerability scan results the testing results from from the pipeline that's all available to us and we can use that data to make decisions about what we want to happen with the changes in in an automated way okay so let's talk about how we're going to run the session today um oops so you should have you should have now registered to get your uh your lab instance up and running and be waking that up now there was some pre-work that needed to be done in Azure devops prior to the workshop uh some of you most of you should have received an email with the instructions for that pre-work but if you registered late you may not have got that in time because it does take a couple of days for one of the parallel job requests to actually get processed by Microsoft so what I'm going to do first before we kick off is just get an idea about who has actually done the pre-work so let me just stop the slides at this point to run the poll whoops okay I'm just gonna I'm just gonna run a poll if you can please um answer the question on the poll so just interested in seeing how many of you have managed to complete all the pre-work for the workshop okay I can see uh 15 responses so we need a few more okay I'm gonna I'm gonna end the poll in about 15 seconds so please respond last chance to respond okay thank you I'm going to end the poll now all right so it it looks like more or less uh about eight people have actually finished the pre-work um for those who responded and some of you didn't have time and and there's one person who ran into issues okay so uh thank you for thank you for that now uh what what we will do then is um we will for those of you who've done the work already the pre-work that's great thank you very much so you will be able to go through the lab and follow uh follow it as we go through and then for the rest of you um you you won't be able to actually complete the lab now but you will be able to do it later in your own time once you do these these initial steps so you're welcome to to stay and to follow what what we go through so that you understand how it works and then you've got the lab guides you'll have access to the instance and once you've set up your Ado project you'll be able to then continue and do the lab in your own time so the lab today is really um this second bit here so what what we're going to do in the lab for the next hour or so is we're going to connect the Azure devops Tool uh to our servicenow instance and get that integration working and then we're going to create a devops application and we'll associate the plan the code repos and the pipelines to the app and then we're going to run the pipeline and have a look at what we at the data that we start seeing in servicenow and then finally we will modify the pipeline to automate a change request okay so given uh given we've only got um less than 10 people I'm just thinking [Music] um I think what we'll do is uh we won't we won't create breakout rooms uh Team we'll just run this as a single session if if anyone runs into problems or you get stuck along the way please raise your hand or post uh in the in the chat and um and one of the one of the servicenow folks on the call or the TM TM Labs guys on the call will uh help you and uh and get you going all right so I'm going to stop sharing that one just before we kick off any does anyone have any questions or any issues before we kick off has everyone got the lab guide got their instance okay so we're gonna start okay so if we if you have a look at if you open your lab guide the first part of the lab guide is about that pre-work that had to be done in azure devops so uh that was about creating a new project and pulling in some data from a template that we have set up um so that those those steps we're not going to go through so where we're going to start if you're following along is we're starting on page seven of the guide so where it's got the heading Lab One devops change workspace project onboarding on page seven that's that's where we're starting okay so the first step to connect the tools is um you need to create a personal access token in Ado so once you've logged into your Ado organization uh just over here next to your name where I'm showing my cursor next to your name you'll see user settings if you click on that and then go down to personal access tokens it will open this screen and what you want to do is create a new access token so you click here to create a token give it a name and an expiry date and just make sure that um sorry the zoo meetings in the way that you you grant full access to the token and then create it so if if you were doing this for real in a production environment obviously you have the option of defining the permissions that you actually need to all the different components in ado and right at the end of your lab guide you will see an appendix which defines the permissions that servicenow devops needs but for the purposes of the workshop just give it full access and then go and create it okay and don't forget to copy it and save it somewhere because we'll need it later on in the lab so once it's created you must copy it and save it somewhere okay the next step is to log into your servicenow instance that that you have and open the change the devops change workspace so once you're logged into your servicenow instance if you click here on workspaces you should see devops change workspace there just click on that and then it should open the screen that you're seeing now with the workspace now what what the workspace is is really a single One-Stop shop for managing the devops change products or application and I'll just quickly orientate you around that so you can see over here we've got getting started and then there's some cards here which will help you set up your accounts and your users now we've already done those steps for you because your instances have been pre-configured so these steps here have already been done what we're going to do is we're going to do these steps here to connect the tool and create applications so we'll go through that and then once those steps are done we'll be able to create the change request automation so that is that is what we're going to do now just to quickly show you some of the other parts of this workspace the applications section which I'm clicking on next is will cover the setup of devops applications and we will go through that next and just so you can see it takes a little time to load so just be aware these instances are very small and they're hosted in the US so they might be a little bit slow they don't perform as quickly as as what you might be used to on your own instance so just be patient and allow time for the instance to to load there are some parts where it'll take some time to to come back to you so just be aware um some of the other parts here we've got tools once we connect our different tools so once you have all your your different devops tools connected this this dashboard or workspace allows you to to manage all those tools and then the other one is the insights dashboard now um what I'll I'll come back to I'll come back to that one and then there's an Administration section so what we'll do next is we're going to connect our tool to Ado so for those of you who've done the pre-work um click on connect tools and you should see pop up this modal so this basically allows you to run a Playbook which is going to help us automate the connection to the tool that we need so over here you can see we categorize devops tools under planning planning tools coding tools orchestration artifact and software quality so we when you click on the different category you'll see some of the tools come up where we have connectors out of the box connectors what we're going to do is if you click on orchestration and then select azure devops that will open up the next part of of what is required to be input in terms of the data so with Ado you have an option of connecting either at the organization level or at the project level so what we will do is we will connect at project level and the next part here is asking for the URL of your Azure devops project so I'm going to jump back into ado and the project that I'm using is this one so if you've already created your project the URL that you need to plug in there is this one here from from your project I'm going to copy that and paste that in there and then give it a name you can you can give it any name you want and then click next for the servicenow guys I I'm not monitoring the chat so if you need to stop me for anything then please let me know yeah there's a there's a question in the chat Mike okay picking Azure devops from either one of those tabs so plan code orchestration so there's there's no Ian there's no there's no difference uh you can connect from any of those options it's because as your devops supports all of those capabilities so it appears in each of the different tabs yeah that's right and I'll I'll quickly thanks Alex that's exactly right and I'll quickly cover that so so one of the reasons why we're using Ado for this lab is just to orientate you on on on as your devops if you've never used it before so you know Ado has a lot of the capability of some of the other tools that and and they're all rolled into one so Ado has boards which is for planning so this boards is similar to a tool like jira so that's where you create your work items and have your backlogs and your Sprints Etc your epics features stories will all go under boards um and you should see in your own ado a number of work items in there already that have been copied from the template then we've got repos which is obviously where the code repository where we're going to have our code again that should be already be populated with some with some files in terms of in terms of the code and the configuration data and then Ado also includes Pipelines so if you're 80 if you've done the pre-work when you click on the pipeline you should see what I'm showing now so your pipeline should have run already once through the build test and deploy steps that that's what you should see right now is that pipeline having run through those steps once already and then Ado also includes test plans and an artifact repository so the reason why we are using it as I said is um because it contains all these things where you know you you do have other other devops tools which will take some of these functions as uh as separate tools okay hopefully that answers the question all right so moving on so the next the next bit is I need to plug in my credentials here so that password access token that I I created just before I need to copy and paste that in here so I'm just going to grab mine and paste that in and then click connect now this this step takes a little while so you need to be patient and allow it to to process you will see a pop-up that flashes on and off what is happening now is servicenow is connecting with that Ado instance and it's checking the permissions assigned to that personal access token to make sure that it has all the right permissions to be able to access what it needs in order to in order for this to work so that is happening now and we should see some activity as I said it it is a little bit slow with these lab instances so just bear with us okay you can see that flashing it will come back if there are any other questions guys on service now guys please um let me know so much can we quickly check somewhere take a pause or where are other participants are they following us yes yes for sure okay so is everyone who is um actually doing the lab today are you all up uh are you all up to the same step that I'm that I'm on now is anyone stuck or have any issues or are you all with us if you are stuck please raise your hand okay I can see suranga raised a hand um can two people have raised hands so guys can you please help out with the with the questions there I'm just going to continue just in the interest of time so what what this is showing me is all these permissions for you know read access to the work items read access to the code Etc this is what servicenow requires in order to make the integration work and those are all whoops those are all there sorry I don't know why I did that just gotta wait for it to come back now okay so I have all the permissions I need I'm going to continue so we're on page eight of the lab at the moment uh yeah guys if you need to create a breakout room to talk with anyone who's stuck please go ahead and do that and then join back to this session when you can all right the next part of the Playbook is asking us if we want to restrict access to access to particular users now normally you might want to do that and you want to you want to set up some groups who will have devops roles in your organization so that's all possible here from the from the Playbook we're not going to do this step so we're just going to skip it as I said you usually this is a much faster in a in a proper instance okay so this step here configure as your devops instance to send data what this is going to do is we're going to set up some web hooks in Ado so that we get real-time uh events coming through when when data is changing or when work work items are created or updated for example so what we're going to do for the to make that happen is on page nine at the top you'll see that there is a password for the integration user that we have to provide you can copy and paste that in here just make sure there are no spaces and that you copy the password correctly and I'll just show you what that should look like so we have pre-configured a password Here just going to copy it and paste that in Okay so so what you should see is now for devops and and the the the Ops the owing opposite is actually a zero so just make sure it says now for devops with the exclamation mark on the end and then once that's pasted properly click configure as your devops and that is going to set up the web hooks for us in ado thank you so the once this uh once this Playbook finishes it things should speed up a bit okay now what we're doing is we're going to associate um the data that we need uh we're going to pull in the data that we need that we want to track so in terms of plans we want to we want to track all the plans so just select um this one what whatever you named your project just select it and then click next so that we're tracking all the plans and the same for repositories so just select make sure Parts Unlimited is selected to track that repository and then click next and the next will be the Pipelines same thing so these are the pipelines that we're going to track so just select both Parts Unlimited and Parts Unlimited end to end and click next so those are the pipelines that we want to track in servicenow okay we're almost there for this step you would normally assign a [Music] a service if if you have services in your cmdb you can assign you can assign services at this point so it's just bringing up for example if you had some non-prod services that you wanted associate with the pipeline and then you had some production ones you're able to do that if you had different pipeline steps for those different environments you can do that at this point we're just going to skip this step but this is just to show you that that functionality is available so we'll skip that one and that should be the end of this of this Playbook okay so that is finished I'm now going to click on view tool record to look at what we have just created and I just want to do a quick checkpoint is was everyone able to stay with me on on that is everyone at the same step or if you have any if you're stuck again or you've got an issue please raise your hand I could see a lot of action happening in the chat so hopefully questions yes so till everything looks fine Mike I think there were a couple of issues which we picked up and sorted out okay fantastic all right thanks T2 all right so this is this is the tool uh this is the tool record that we that we just created so that's just showing you what that looks like now on page 10 we want to make sure that the web hooks that we just set up are actually working in ado so I'm going to jump back to my Ado instance and down the bottom right down the bottom here you'll see project settings if you click on that and then under project settings under General you'll see service hooks click on service hooks okay so I can see that the the web hooks have been set up that that's what you should see in your Ado instance if if that is working so you should see that whenever code is pushed a release is created work item created deleted Etc that it'll send an event to to servicenow and let us know about those updates so just make sure that is working in your ado okay so going back there's a couple of ways we can we can navigate to The Next Step either from the home page I can create on click applications or from here where I ran the Playbook I can click on create a new application they will they'll basically do the same do exactly the same thing I'm just going to go here home and click on create application all right so this will allow me to create a logical container a devops app where I can relate all the data that's applicable from my plans my repository my pipelines Etc to an application and I can either create a new one or if I have existing application models in my cmdb then I can use an existing one so for the purposes of this lab we're going to create a new one and I'm going to call it parts Unlimited and click create okay and then we have the option here to associate this with a business application I'll do that in this case and and I will click save to save this record and you can see on the right hand side I've got some recommended actions so the workspace will give you help and also surface documentation in the tool to walk you through what you need to do next when you're on any particular part of the of the workspace so you can see across here we've got plans repositories pipelines there's nothing in there at the moment so first of all we're going to associate some plans so click on associate plans first yeah okay now when you when this list comes up you might need to just sort this list to be able to find your tool you will see a whole lot of data in here but we want to select the tool that we just created so I've just clicked on tool to to sort the other way so this is the this is my tool so I want to select that one and then associate plans and now we're going to import data the planning data from the tool so what we need to do next is we have we can import up to 90 days of data we just want to go back two months in this case so I'm just going to change 0 5 May to 0 4 April so we've got two months of data and then click on import so that's going to go and import the last two months of all that data for me and you can see there's an import request that's been started there for the planning data next we'll do the same thing for the repositories so Associated repositories click on that one and follow the same steps so click on a tool to make sure that you're selecting the right one depending on what you named your tool you want to make sure I'm selecting Parts Unlimited here and then associate repositories and again just go back two months so zero four and import all that data and again there's an import request that's been triggered there uh and that the next one the last one is pipelines so click on associate Pipelines select both of these and then associate Pipelines and the same thing again go back two months and import data okay so you can see here the import requests have been kicked off and and they've been created now they will run in sequence so they'll take a little while to run so while they are running it will allow that to will allow that to run and finish it take a few minutes to happen we're going to go and have a look at what happens once all the data is imported what what does that give us in terms of insights so I'm on a different instance here just to just to show you what the insights dashboard looks like so over here this is just a summary a summary page but if we dive into our flow metrics once I've got integration with my planning tool I'll be able to see data like this which is all about showing me my cycle time for my planning items and uh and and how how long is it taking me work to flow through from Once story gets created to when it gets deployed so this is showing me the cycle time so how long am I planning items my work items staying in a particular state what is the throughput and distribution so for example if I'm spending a lot of time fixing bugs rather than getting a new customer features deployed you know maybe I have to look at why I'm why I've got a lot of bugs to deal with is my quote code quality not where it should be is my testing not where it should be so it allows me to dive in and understand any any blockers any issues any bottlenecks I have in my process again this is about how long it's taking me to deploy work overall and then how long is work staying in a work in progress State how long am I waiting for things to happen and what can I do about reducing that wait time so that data is all there you can see there's some filters up here which which are out of the box so I I this is showing me all my data but if I want to filter it I can look at a particular application or even a particular repository service business application product even work even a specific work item type if I want to and these which these filter widgets are available across all these different tabs on the dashboard the change acceleration dashboard will show me how I'm doing in terms of change management for devops so what is my volume how long is it taking for these changes to get closed out what about the automated versus manual changes um you know obviously developers are Keen to automate everything and once you start doing that in your organization it'll create momentum for teams that are not automating their changes to want to jump on board and do it here you can see changes that are waiting for approval and how long that's taking so you can dive into why that's happening and you can even have a look at potential savings for developers so we're we're a developer no longer has to manually create a change and copy all the data onto their change where that is now automated there's a saving there and this can track those savings for you the accelerate metrics tab is uh another word for this the industry word for this is the Dora metrics so Dora stands for devops research and assessment which was um set up by Google as a kind of a benchmark or a a performance measurement across the industry of how organizations are performing with devops and there are four key Dora metrics lead time deployment frequency mttr and failure rate so these are tracked out of the box by this dashboard so you're able to see how well you're doing and what you need to pay attention to in terms of your overall devops performance the quality metrics cover your code quality code coverage your test passing rates bug counts and any security vulnerabilities that are getting pulled into and getting flagged by tools like sonar Cube for example or jfrog your development metrics allow you to look at your developer performance so things like your commit frequency who are the how many active committers do I have who are my top committers top reverters usually those are the same people and um you know that all that all builds a picture for you in terms of your your developer performance average commits by committer by pipeline execution commits without work items there's no data on this widget but that's an important one obviously you don't want to commit any code without having a story attached to it so this will track that for you and you might want to you you might want to have a a change approval policy that looks for that as well and stops any work being deployed if there's no work item attached so we do provide for that out of the box and lastly operational stability so this is um the devops changes that are actually flowing through your your system are they causing incidents are they causing outages and what is that doing to service availability so you can track that as well okay any questions on that and again guys I'll ask you to please read the questions for me because I can't see the chat yeah there is no there's no active question as of now let's we answered a couple of questions okay fabulous thank you just just QuickTime check uh Mike yeah okay cool all right no worries let me push on thanks YouTube okay so going back here I'm just going to refresh this um pane just to have a look at our Imports okay so we had two completed one as an error one is waiting okay that's I'm not sure why that's got an error uh but that's okay um maybe because there's no data yet in our pipeline I suspect that's why that won't errored um so that's okay all right we're going to move on to page 14 of the lab guide now so now we're going to jump into the pipeline and and start tracking it so just just to confirm what we actually imported so uh before we do that so the plan so we can see we've got the plan plans now and we've got a repository and we've got two pipelines that are there so we should be able to see if we jump into here uh we should be able to see we've got 120 work items so if you can see the work items so again this is the metadata that's being pulled in from Ado on all the work items that we imported so that's what you should see now in servicenow is that data okay um so now what we want to do we're going to we're going to look at tracking the Pipelines so on page 14 uh what we need to do is go to our Ado project and go to the pipeline so over here on the left you'll see the little rocket and then you click on Pipelines and click down here on Parts Unlimited where you see that and then up here on the top right click on run pipeline now this will come up with a a pop-up you don't have to select anything here we're going to commit to the master branch and we're going to run that okay so that will run and we'll let that run so just before we move on so due to any uh any other issues or questions that I need to address is everyone keeping up um yes everything looks fine till now a couple of folks stay stuck I'm not sure if Chris Krishna if you feel okay as of now uh were the guys able to help you folks that got stuck yes yes everything is going smooth uh okay fantastic yeah guys raise your hand if you have a question if you stuck somewhere uh yep okay great thank you all right so just to show you what while that's running uh what I'll show you is just close some of these some back on uh I'll I'll I'll close all these and I'll navigate from here just to show you so if I click on application and I just need to refresh this list so click here on refresh list and that's going to show me the new application that I created Parts Unlimited so click on that and I can see here that the data that I associated with this application the plans repositories and pipelines so click on the Pipelines and then click on the first one the Parts Unlimited pipeline and then that's showing me that that one is being tracked and that it has four steps so there's the uh there is a build test validate deploy precondition and then deploy so if you click on this pipeline UI view view pipeline you will see servicenow takes the data that's been pulled in from the pipeline and it builds a UI to show you what the pipeline actually looks like and just wait for that to render so you can see we've run the pipeline once so my pipeline history will be here on the left and I can see my build test validate steps here I can also if I had all the data I don't have it yet but I can see um I've got my artifacts I've got if I had commits there and if I had work items it would show me similarly test results and software scanning results are going to show up here so this is not servicenow running the pipeline this is just servicenow building a view of the pipeline that is running in ado okay all right so what we're going to do just jump back here and see how this is going okay that pipeline is finished so if I jump back here and just reload this form I should see the second pipeline execution show up once it refreshes foreign so hopefully this is all all making sense um and and again apologies for the performance of these instances this this should be a lot faster in in your own instances again okay all right so what we're going to do next is um on step three on page 14. so we're going to jump into um sorry about your pardon we're going to go into the next step on page 15 to automate the change requests okay now it's getting exciting so we need to provide we need to provide some details about what we want so you can see here with these with these steps I need to select a step where I want my change to be created so these are not in the right order so it will have a build and then we'll have a test and then we'll have uh precondition and then we'll deploy so what you want to do is you want to click on this deploy application precondition step okay and we need to select type we've got a choice of build and test test deploy Etc we want to make this a prod deploy so select prod deploy and make sure this change control box is ticked and then you should see some other um parts of the form may be made visible so we want to put in a configuration item here and we're going to use uh I'm just trying to find out we're going to use uh it's spell Parts Unlimited and under change approval group we want to put in application development as the group who's going to be pulled in for manual approval of the change type you can leave as normal and we're going to save this at this point okay so that's saved now what you need to do is um in step four on page 15. jump back into your pipeline and we just need to go I just need to move that just need to go back to one step to Parts Unlimited so pipelines slash Parts Unlimited and then you should see the edit button over here on the top click on edit now this is yaml uh yaml is very finicky when it comes to indentation so you can see here that you've got the different steps in this code and that they're indented indentation is Meaningful in in yaml so just be careful about what you do next now if you scroll right down near the bottom so lines 72 to 76 you'll see those lines are commented out and what you want to do is put your cursor right on the left hand side and select down to line 76 so that you've got it selected like that exactly as you see on the screen now the the hashes here are comments so these steps have been commented out the easiest way to uncomment this if you're on a Mac uh you hold down command I think on Windows you hold the Windows key if I'm not mistaken and then hit the slash key and that will uncomment those steps so command slash or Windows key slash should uncomment like that now before you save what we need to do is we just need to make sure that we're pointing to our our servicenow instance our lab instance so online between line 73 and 74 where where you can see settings just click on settings and then over there on the right you will see a servicenow endpoint just click the drop down and you'll be able to select your servicenow instance so just make sure it's selected there and we don't need to change anything else to me let's have a look okay and then make sure you click on the add button at the bottom right so what you should see in your yaml in your pipeline is you should see the connected service name has been saved as your servicenow instance there okay if that is done then click save and just make sure commit directly to master branch is selected and click the save button okay now these pipelines have not been set up to trigger automatically so what we're going to do next is we're going to change some code and then we're going to run the pipeline so we're on step seven so what we want to do is navigate to our uh to our repo so over here on the left where it's got repos hover over that and then click on files once you're there just click on the Parts Unlimited uh top folder and you should see down here there's a readme.md file just click on that file this is just a readme file it's just text it's not actual code but we're just going to simulate a code commit and once that is selected click on edit and we will just add some blank lines to the file to simulate a code update and once you've done that you can then click commit and we need to make sure we as we assign a work item to this change so you can drop down the work items and just select any anything you want any work item you want and once that's done click commit Okay so we've made a change now we're going to run the pipeline so going back here to the rocket click on pipelines and then Pipelines and then click on the Parts Unlimited pipeline and click on run pipeline okay so what we're expecting to see this time is um once the pipeline gets to the deploy stage we should have a change record that gets created and the pipeline should pause so we'll just let that run and I'm going to pause there just to see is everyone managed to keep up anyone stuck any anyone have any issues mentioned one issue Graphics that is stuck somewhere yeah um yeah I I was falling through pretty well uh catching up but when I got into the um pipeline for Parts Unlimited there was only one step listed for me and that's called job I didn't see um the similar steps that I and that you have in there ah okay so when you when you edit your pipeline you're not seeing all this code I I don't even have that selected pipeline that I need to edit I only get one single step in the in that box I know I see okay so it sounds like uh maybe uh so so how this gets populated is that pre-work that was done where we copy from a public repo into your um your project that's where this is coming from so maybe something went wrong with that step and the repo uh the the code didn't get copied all right um that should be fixed if I re-bought it yeah exactly yeah you can you can re you can re-import it I think there's a it's mentioned at the beginning of the lab guide that if the data in the repo doesn't get imported it's got some steps that you can follow to manually import the data so I'd recommend you follow those steps that sounds good no worries thank you yep cool no worries anyone else is everyone else managing to stay with us okay great uh any uh due to anyone else no I think I think we are good as a friend no active questions or okay that's correct all right so um you can you can follow the next steps in the in the workspace um I'm just I'm just going to show you another view which is not in the workspace that when it comes to looking at the changes um I'm I'm not a big fan of what's in the workspace yet it will improve over time but I think the old view actually is slightly better so that's what I'm going to show you next once it loads are we doing for time we still got 20 minutes okay let's have a look all right so you can see here our pipeline has paused and on this servicenow step it should have created a changed request for us and it's waiting it's waiting for that change to be approved before it will it will allow the pipeline to continue so let's go and have a look here if I click on the filter Navigator typing pipeline I can look at my pipeline executions it's the same view that I showed you previously in in the workspace I'm just going to jump in here field okay so let's have a look at that pipeline for the Parts Unlimited now I'm going to click here on Pipeline UI so again I've I've got my history I can see the previous two runs of my pipeline where I had those that data and those steps now I can see my build has completed my testing is completed and I've got a change that's been created so let's have a look at that change now this is this is where you should start to see the power of this product so this change has been created automatically from the pipeline and should be populated with the data that we're looking for from our devops tools so if we scroll down here we can see that um I've got my work item that I associated I've got my test summaries showing me my passing rate for the tests if I was running sonar Cube I'd be able to see the sonar Cube scan data here I can see the commits associated with that and my artifact version and a change policy has been applied here in the normal change policy so this change is waiting for someone to approve it I'm just going to go and for some reason these are duplicated in the lab I don't know why but we'll just go and approve this change manually push this okay so let's see now the change has moved to implement State you can see it was approved and it's moved to implement if we jump back to our pipeline that that should uh whoops sorry I went too far I'm just going to move this out the way we should see that uh events come through to Ado and Ado should allow the pipeline to continue uh is taking a little bit of time because of the how slow these instance is but we should hopefully see that come through shortly so again uh the the next the next step in the process would be to set up some approval policies to to automate the change and that will be the subject of a of an of the next Workshop so we are planning a series of these workshops this is just the first in terms of getting started so the idea is just to to show customers how to use the workspace and how to connect a tool and you've seen the first step in terms of triggering a change to be created from the pipeline the next step is setting up the approval policies to automate the approval of the change and progress the change through uh through the life cycle so I can see this has started going through it's gone through to review already which is great so now I'm able to review the change and I can manually close it once I'm comfortable with with what happened and I can jumping back to Ado I can see that my pipeline has now fully completed so we had the Speed although not really fast in this instance and we have the and we have the governance we had all the data that we needed uh actually captured as a single source of Truth on it on our change record so that that is the end of the lab any questions on what we've seen today before we wrap up like there's a there's a question about what will happen if you didn't approve the change if it was rejected oh okay well yeah great question so so what would happen if I had rejected the change um it would have gone back and canceled the pipeline would have failed and and the change would have been canceled so the the pipeline would have not deployed so what what we can see when we look here you can see the change request happens here and then the deploy is happening afterwards now this is not showing me the latest data but if I had rejected the change here this step the deploy step would not have happened so it wouldn't have deployed the pipeline would have stopped at that point any other questions okay I'm just going to jump back to the slides just to wrap up and run another poll yeah so while you're blinking a poll I think we're just 12 minutes away um still I don't want to ask questions please feel free to raise your hand or type a question chat yep absolutely okay so so what we we showed you we showed you very briefly how to connect a tool create an application get all that data from your tools into servicenow into devops so that you're able to have visibility of that data and then eventually once you uh once you have your policies in place you can fully automate your change but typically customers have a journey that they go through which is you know crawl walk run when it comes to devops so you don't have to jump straight through to change automation uh as your first step you are able to even if you just connect the tools and you get that data and you can populate that insights dashboard that already provides you a whole bunch of value because you've got visibility of the data and you can understand what's going on you can then move through change traceability where developers could with just a few clicks add that data to their to their changes which are still being created automatically and then the next step which would be kind of the the walk step would be to trigger the change to happen automatically from the pipeline but not necessarily stop it from being uh associated with the approval and then the final one which is as as we talked about which is pause the pipeline wait for approval and then only if the change is approved do you continue okay so I'm going to run a final poll and that's just to get your view in terms of what happens next with what you've seen today so let me launch that poll so we're just asking uh asking you to choose what you're going to do next after you've seen what you've seen today so what are your next steps so please answer that we've got about 30 answered so keep going guys put your answers in I'm going to end the poll in about 10 seconds okay thank you so it looks like um most people were here for information which is good but there's a few of you that want to deploy devops in in subprod within a month and some within three months which is fantastic okay so yeah we're very keen for customers to to go ahead and deploy this so if you do need any help or anything just please reach out to your account team reach out to us and we'd be happy to to help you We Will We Will um we will send out uh some the slides and additional links to information as well thank you very much for joining us today and finally um if there are any final questions I'm happy to take people off mute and we can answer the questions live or post in the chat did people find that useful did it did it make sense did you get a sense of how straightforward it is we in in basically in an hour we were able to connect to Ado and bring in all the data and have a change created so that was all within an hour Micah just made everyone to allow to talk thank you thank you unmute yourself and yeah feel free to feel free to to ask verbally any questions uh any comments any suggestions for how we could do this better next time hello hi thank you for the session anyways I did not join on time I was quite late but at least I grabbed something so I wanted to ask if you're doing this in a test environment for example and you want to do the same change in a pro environment can that cause like some kind of ramification what are some some of the ramifications this can cause an important environment if you have done the change uh in a test environment when or in a deaf environment okay so so typically what you would want to do is you would definitely want to set this up in a non-prod environment first and and set up the connections and set up the pipeline and get all the data in and set up your your approval policies Etc and have that working in non-prod first and obviously do it do proper testing to make sure that it's all working properly and that everyone is comfortable with it before you do any deployment to production so you would typically go through the you know the same um sdlc um or you know management process that you would with with any servicenow um change within any upgrade you know you you do it in a subprod instance first and then you'd migrate those changes through to production after you've done the right testing to make sure it's all working okay so uh can it cause any kind of conflict or data loss um it shouldn't cause any conflict or data loss I'm not I'm not sure how you would get uh con you know data loss because all it's doing is it's it's importing data into servicenow and then it's creating a change so I don't I can't see any scenario where that would cause data loss okay all right thank you so much Christian sorry you had a point did you wanna yeah I think a question of maybe was about what if you do the sub uh production setup first and then on the same environment you do also the connection to prod if you have any conflicts when you do this kind of connection from death and prod and pro to the same um a Ado setup for example oh okay um and Mike can answers it because I recently did it yes but I did um like connect a PDI and then a vendor instance and I didn't saw any issues but I did just to avoid issues um in one step you mentioned where you can see the connections so I simply deactivate as a web hooks I mean so I shouldn't even there and simply deactivated the web hook to the PDI when I moved to the vendor instance I see I see so there's if you right click then you can disable it if you don't if you just want to move back and forth you can simply disable the web props for now for that one instance you have to do it six times because I think it Shakespeare books per instance that it generates yes but this is how I let's say work around it just to avoid the concern that Mimi was mentioning okay thank you thank you Christian so 93 or Central did you have any comment on that in terms of having um having a mix of non-prod and prod connected to the same Ado do you have any comments on that I think you summed it up uh correctly my example there should not be any data loss because if it's two different instances right one year abroad and some product which kind of the same Ado at the end of three we are going to we have uh different books for individual instances right so you would keep getting the data and uh and you can also import the data as we just saw so we won't see any data okay great no worries and I can see gaurav you raised your hand did you want to ask something um that I was sweating I could actually have a um some sort of a config merge um and added as a manual step um between those um uh pipeline changes um something that we may have to see like um there are different web applications as components for for the main problem and each one of them may have different dependency configurations um so how can we set that out as a merge step before of pre-compile or pre-deploy oh okay we I think we'd have to have a look at that uh individual use case to understand a bit more but but typically I mean if you look at what devops is trying to do generally the philosophy is to have you know small uh iterative changes that that that make um you know that are simple that that are not too complex that's really what you want to try and go for with your pipelines if you've got pipelines that are quite complex and doing those sort of mergers I'm not sure if that's uh good practice however it's it's a valid thing if it's happening in your organization but we can definitely have a look and maybe provide some recommendations once we understand the use case a bit better please contact us with the details and we'll have a look yeah alternative no no just just a head of heart there and you absolutely granted you're there where you're editing this that's right yeah thank you thank you quick question all right uh we're almost at time so any last final questions before we wrap up great thank you so much for joining us everyone um hopefully you got some real useful knowledge out of that and look out for our future sessions thanks all bye