Cloud 5 - Mysteries of Cloud Manager - Experience Audit

This mini-series is called The Mysteries of Cloud Manager. In it, we’d like to dive into some of the things that Cloud Manager does and clear up some of the confusion around it. Today, I’ll give you an overview of some of the important things that Cloud Manager does and where the hang-ups usually are. I’ll be using a full production environment to demonstrate things today, so you may see some pieces that don’t exist in sandboxes or non-full production instances. So we’re dropped off here at the Cloud Manager program overview page, and you can see your environments and pipelines and so on and so forth. You can add additional pipelines and show all and so forth, but that’ll drop you back off at these tabs that you can see at the top. So we have the environment tab, which shows you your different environments, the domain settings, SSL certificates, all pretty self-explanatory. You can also dive into the different environments to see a kind of a snapshot and see the published service and the preview service and all those URLs and so on. Pipelines will give you access to all the pipelines you configured or add more. We do have a front-end pipeline configured here. Repositories being you can get your repositories that you configured or you need access to credentials. Activity, you can see the different activities that you’ve executed on that program. Reports will show you the SLA activities that happened, so what, you know, any downtime or unavailability of the different environments. And the learn tab will get you access to certain features that you want to check out, so quick overviews and some deep dives and some deep dive solutions. So clicking on the ellipsis for the environments give you access to the details of the environments or logs or dev console and access, and we’ve covered this before in some of our previous videos. Pipelines, you can click on down the right or you can go to the link at the top and on there you click on that and you can see the details that have executed or edit them and see that this is a deployment pipeline and configure which repository on which it will act on. You can see the deployment triggers as well. So let’s look at a production one and you’ll see that they’re mostly the same here. Some of the, on the source code tab you can see that it does some functional testing and you can schedule things and so on. On the experience audit tab we can check out some of the, you know, best practices, PWSCO type stuff so you can add different pages. So looking at the results from a non-production pipeline build, you can see the different activities that have happened. So we did the build and unit testing which does a lot of code scanning and so on. So clicking on the code scanning review summary you can see the different checks that it did. So security rating, it needs reliability and so on. Different requirements for which this build would pass. So, you know, looking at the performance, the amount of duplicated lines and the number of open issues and so on. This one obviously is pretty good. So security rating is A. You can see that this one checks out pretty good. So you can download the details of the code scanning or look at the build log directly. Same thing with the build images. So if something fails there you can download those and check them out and see why they failed. Looking at the production pipeline we can see that it has the build tag and the commit and so on for the repository under the build and unit testing. You can download the logs like we did just before. We also have that review summary for the code scanning that we’re now familiar with. And you can check out the build log for the build images or stage and so on. So what we’re interested is once it’s successfully deployed to stage you can see it does a series of product functional testing and custom functional testing as well as UI testing. We’re going to cover those later in the next series. But let’s look at the experience audit. So clicking on review summary you get a page up there and you can see that it’s generated by Lighthouse. That’s the Google Lighthouse project. This is all informational only. If you have a bad score it will not fail the pipeline. So this is mainly to help you have a better, more accessible, more SEO friendly website. So you can see if we scroll through we have lots of different audits that passed. So if you want to check out something like SEO you just click on it. Click the details. And you can see it change over time.