Licensing Requirements

As of 2025.1, Perforce QAC enforces licensing requirements for desktop versus server-side working.

Desktop usage will require the purchase of a User license that allows use of the QA GUI, qacli, and IDE plugins.
Server usage (i.e. qacli validate build or qacli validate cibuild) will require the purchase of a Build license.

QA GUI and IDE plugin users will checkout and hold the User license while they work on a project.

Command line users (qacli) will likewise checkout and hold the User license for the following operations:

qacli analyze
qacli view

If more users attempt to checkout User licenses than are available, then functionality will be restricted.

Analysis License Checks

In QA GUI, if a language or compliance module license is unavailable, analysis will perform a “best effort” and analyze what it can by default. If Stop on Error is selected, it will halt analysis upon the first license failure.

In qacli analyze, the build will stop immediately if a language or compliance module license is unavailable – unless –force-complete is set.

Licensing Requirements for Viewing Results

Additionally, if the appropriate license for viewing results is not available, then analysis results will be obfuscated – meaning that the location of issues will be hidden.

If a language license is unavailable, results for that language will be obfuscated.
If a compliance module license is unavailable, all results will be obfuscated.

You will need to ensure that all required licenses are available in order to upload results to Validate (either from the GUI or using qacli validate build/cibuild).