When Packaging code for analysis with the Delivery Manager Tool, if the packaging step has abnormally terminated then subsequent steps may fail as well.
You will see in the Delivery Manager Tool logs, the message "The packaging in the delivery has not been fully completed" which indicates that there was an error during the packaging step. In addition to this message, you may also see other Errors such as:
- An exception has occurred during source package file creation.
- The path to extract does not exist <Path>
Please see the below screenshot of a log failure in this case as an example of this situation:
In this case, the initial abnormal termination was due to a Java heap error which then caused these subsequent errors in DMT. The Java heap error can be seen in the screenshot below:
Release | Yes/No |
|---|---|
| 8.2.x |  |
| 8.1.x | |
| 8.0.x | |
| 7.3.x | |
RDBMS | Yes/No |
|---|---|
| Oracle Server | |
| Microsoft SQL Server | |
| CSS2 | |
Below is the step-by-step scenario that lead to the problem:
- Use the Delivery Manager Tool (DMT) to scan and package the code for analysis.
The impact of the problem on the analysis or the dashboard is: No files delivered, so no files analyzed
To fix the problem, proceed as follows:
- Check the DMT packaging logs to understand the abnormal termination of the packaging step. This may be the result of problems such as memory resource limitation or disk space issues.
- Resolve the issue which resulted in the abnormal termination of the packaging step.
- Repackage and verify that the packaging step has properly completed by examining the Delivery Manager Tool logs for the packaging step.
For more information on finding logs for DMT, please see the following page:
