Using Code Analysis with PowerShell in Toad DevOps Toolkit

Hello data friends. My name is Robert Pound, and I am a product technologist for Quest. In this video, we'll discuss Toad DevOps Toolkit code analysis. Toad DevOps Toolkit is a Windows application that allows you to reliably execute Oracle database functions within continuous integration platforms such as Bamboo or Jenkins. Toad DevOps Toolkit supports access through a number of languages, but the focus of this video will be on PowerShell. It is assumed for this video that you have knowledge of PowerShell, a tenuous integration platform such as Bamboo or Jenkins, and an understanding of the Toad features being discussed. There are several components to help you along your DevOps journey. The focus of this video will be static code review using the code analysis feature. It is helpful but not necessary to review the code analysis dashboard in Toad for Oracle as a reference. You may also want to check out the Example folder, which is located under your installation directory Examples, PowerShell, and PowerShell Script to review the different examples in PowerShell at your disposal. If we wanted to look at code analysis-- and I have it open in the ISE-- the example script contains every example for code analysis. And you should use it as a reference when creating your own script. Switching over to a simplified demo, we will go ahead and walk through this. To start off, I just want to point out that I'm using PowerShell 5.0. And that's because that is the PowerShell that was used when creating the example demos. However, it is not necessary. And also, I'm not using code best practices for this simple script, for clarity. We have our connection information at the top, the database, then the connection string. And the first thing we do is create a new com object, Toad.ToadAutoObject. This will start the process so that we can utilize Toad DevOps Toolkit. And once the object has been created, the first thing we do is establish a connection using the connection information at the top. We create a name for our report, and also indicate the directory that we want to store the report, and also the type of report that we want to create. In this case, an HTML report. I have not specified the rule set here. And by default, if we do not specify a rule set, it will use the default top 20 rule set. So once we have the parameters set, the next thing we do is identify the object that we want to analyze. In this case, we're adding a single object called OW_PLACE_ORDER, and it is owned by a QUEST_DEV, in this case. And the object type is a function. So once we've established what we want to see and what we want to analyze, we finally just execute. And once the code analysis is complete, we perform some housekeeping, and quit, stopping the process. So if I move to the Temp directory, we will see the report that has been generated. And we can see the code analysis for this particular object highlighting the various code metrics and code violations. And that pretty much sums it up for code analysis using Toad DevOps Toolkit. Hopefully this was helpful. For more information on this topic, you can view the Help file, which is located under Quest, Toad DevOps Toolkit. And you can see the Help file here. You can also check out the community-driven innovation going on at www.toadword.com. For more information on this product, go to www.quest.com/products/Toad-DevOps-Toolkit. Thank you, and have a tremendous day.