Troubleshooting
Last updated
Last updated
Here are some common issues that you may encounter when configuring and using Cover Pipeline for GitLab.
Diffblue Cover performs a number of checks before, during, and after creating unit tests. Cover can generate a range of output codes during these checks to provide general information and highlight any issues. These codes and associated messages are output during the run, visible in the job output, and saved to the log files. See for details.
For general Diffblue Cover issues, see the Cover CLI topic.
License issues are reported using . Common issues include:
L005 - The license has expired - Update your license key (see ) and/or contact for assistance.
L009 - License key not found - Make sure you've entered the correct license key and in the format provided (see ).
To resolve this issue, simply update the docker image name in your .gitlab-ci.yml file.
Access token issues are reported using the E120 - Git command failed output code (see ). For example:
Access token with incorrect permissions. In this case, check that the access token has correct permissions for the project (Developer role, plus api and write_repository scopes/permissions) - see .
A mismatch of the access token name can lead to a Git error. GitLab requires the access token name used in the Cover Pipeline for GitLab integration to match the name of the access token in GitLab. Check and update your access token name as needed - see .
The Diffblue Cover docker image to use as part of your project pipeline is specified in your .gitlab-ci.yml file (see ). Tag variations are provided for each supported JDK version (see for details). An error in the naming of the docker image will cause a failure to download the docker file:
If no tests are created, updated, or removed as part of your merge request, you may have selected the Diffblue Cover: Skip label in the merge request. This label is used to mark a merge request as requiring no tests to be written. See .
