Skip to main content

Automated cloud assurance and code compliance

Each InsuranceSuite project developed and deployed in the cloud must follow Guidewire Cloud Standards. In this way, you can avoid potential maintenance, upgrade, and performance issues. Automated cloud assurance processes help you to verify your code before merging it.

Code inspection process​

To support the code inspection process, a TeamCity Automated Cloud Assurance build runs for each InsuranceSuite application to check the code for any violations.

The build is available under Project → InsuranceSuite Application → Automated Cloud Assurance.

The steps for the process are as follows:

  1. Commit changes to your codebase.

  2. Wait for the Automated Cloud Assurance build runs to check committed changes against the Guidewire Cloud Standards.

  3. If the number of violations exceeds the threshold, the build fails.

    This doesn't prevent you from opening a pull request, but it's automatically marked with the NEEDS WORK label.

  4. As one of its steps, the build generates an inspection report showing error details.

Tip:

For details, see Guidewire Cloud Standards.

Inspection sources​

The analysis uses two sources of inspections:

  • Guidewire Studio for InsuranceSuite applications that provides the base code inspections.

    For details on Studio inspections, read the Working in Guidewire Studio topic in the Configuration Guide for your InsuranceSuite application.

  • Cloud Assurance Plugin for Studio that adds additional cloud assurance inspections to those ensured by Guidewire Studio.

    To download the Cloud Assurance Plugin, go to Guidewire Marketplace.

Build timeout​

By default, the Automated Cloud Assurance build is set to time out after 120 minutes. To modify this value, contact Guidewire.

Verify code inspections​

Verify the inspection errors to ensure compliance with Guidewire Cloud Standards.

  1. In TeamCity, go to Project → InsuranceSuite Application → Automated Cloud Assurance.

  2. Select your branch, and select the build you want to check. The Overview tab provides you with the following details:

    • Pull Request Details

      Details of the pull request containing the inspected code.

    • Code inspection

      Number of issues that were found during the analysis and a link to a detailed report.

    • Problem

      Reasons for build failure.

  3. Go to More → Code Inspection. The report contains the following information:

    • Number of inspection errors

      The Total number includes both errors and warnings, and the Errors number lists only inspection results at the error severity level. Use the toggle to narrow down the results.

    • Inspection scope

      This section lists packages in your configuration files that triggered inspections. Inspections coming from the Cloud Assurance Plugin include the Warnings and Errors prefixes.

    • Details of selected errors

      This section provides further details of selected errors. The content of this section depends on the error that you choose, and redirects you to the code line containing the error.