Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Jira Legacy
serverSystem JIRA
serverIde71e36b8-1c31-3d38-9c43-0d513e8b44c9
keyFNSDKEXT-95

Jira Legacy
serverSystem JIRA
serverIde71e36b8-1c31-3d38-9c43-0d513e8b44c9
keyFNSDKEXT-108

Introduction

Unity will utilize FN’s Azure DevOps solution to manage the building and packaging of both the FN SDK and the Unity example project. The following defines how Unity will make use of Azure’s built in build and pipeline tools to conduct proper CI/CD methods.

...

  • A batch file will be written to build the example Unity scene utilizing the FN SDK

Static Analysis

  • FN will provide a SonarQube instance for static analysis of SDK code, including bug and vulnerability detection, and “code smell” checks.

  • SonarQube will be integrated into the AzureDevOps pipeline using the SonarScanner plugin.

  • SonarQube Scans will be performed as part of every build job.

  • Acceptance Criteria for development tasks will include requiring a “passed” status for the SonarQube Quality Gate.

Artifacts

SDK Artifacts

The following artifacts will be generated upon a successful build of the FN SDK

...

  • An internal, Unity facing git vcs repo will be created to mirror the Azure repo

  • Unity developers will connect their local git repo to both the Azure DevOps repo and the internal git vcs repo

  • Any changes made to the root development branch will be reflected both in Azure and the internal git vcs repoAny changes made to the main master branch will be reflected both in Azure and the internal git vcs repo