When attempting to create a Software Release—during the package creation process the package properties point to a Software Library folder, UNC path, or local folder that contains 50K of files, and exceeds 20GB in size.
When the root folder is selected the user may see a Java box with the following message:
Sending manifest to server…
Depending on the size it can take several minutes
The user may also see it processing each and every file within the folder hierarchy.
If Java logging is enabled the user can see the progress (very slow progress) being made on the entire process
The process may run for many hours but eventually times out and disconnects leaving the package and Software Release incomplete. Repeated attempts yield the same results.
The Console UI is designed to verify each file as it builds a manifest, and was apparently not expecting packages of this magnitude. Usually packages are built as MSI or EXEs containing one or a several large files, and not thousands. As a result it cannot build the package and present the folder hierarchy to the user in a timely manner for packages of this nature.
Since the user probably doesn’t need to see the folder hierarchy displayed by the UI there is a workaround that can be employed to get around this impasse when it occurs.
When creating the package point it to a desired folder, but one that is empty or contains only one or a few files. This will allow the package to be created and set the folder path to be used during package refresh.
When the package has been created manually copy the needed files into the folder that the package points to.
When all files have been copied into the staging folder open the Console and go to “Manage > All Resources > Package”
Find the package that was created and right click on it and select “Update Distribution Points”.
Behind the scenes the Package Refresh process, which requires no expensive UI to run will build a snapshot/manifest and signature file in a relatively short time (usually 3-4 minutes), for even for the largest packages.
Once this has been done the package is ready to be distributed to the designated Package Servers or directly to clients that request it.
Subscribing will provide email updates when this Article is updated. Login is required.