More About Archive Expansion Behavior During Codebase Uploads

FlexNet Code Insight 2019 R3

The following topics describe important information about how archives are expanded when a codebase is uploaded

Retention of the Original Archive Files

The extraction of an archive’s contents occurs directly in the parent folder. No new folder is created to contain the archive contents, and the archive itself is retained in the parent folder. For example, suppose the archive AppsSport.zip is located in the coreApps directory in your codebase. This archive contains the files hockey1.exe and tennis.exe. When AppsSport.zip is expanded, the resulting codebase tree looks like this, where AppsSport.zip is retained at the parent-folder level:

coreApps
---AppsSport.zip
---hockey1.exe
---tennis1.exe

Expansion of Archives Containing an Intermediary .tar File

The .tar.gz, .tgz, .txz, .tar.xz archive types and similar archives contain an intermediary .tar archive. The codebase upload extracts the intermediary .tar file from the archive, but applies the Archive Expansion Options configuration starting with the expansion of the intermediary .tar file, not the initial archive. The following example demonstrates this expansion behavior.

Suppose the archive jars.tar.gz has these contents, where the intermediary file is jar.tar:

jars.tar.gz
--jars.tar
----file-1.txt
----file-2.txt
----jar.zip
------\jar
--------abc.jar (color)
--------xyz.jar
--------classes.zip
----------\classes
------------corporation.class
------------employee.class

The uploaded codebase looks like this if the None option for Archive Expansion Options is applied. The jars.tar is extracted from jars.tar.gz. The jars.tar archive is then expanded, but the jars.zip file (contained in jars.tar) is not expanded. Keep in mind that the original archive files are retained.

file-1.txt
file-2.txt
jars.zip

The uploaded codebase looks like this if the Uploaded file and first-level archives only option for Archive Expansion Options is used. The jars.tar is extracted from the initial jars.tar.gz. Once the jars.tar archive is expanded, the first-level jars.zip file (contained in jars.tar) is also expanded. However, the second-level classes.zip (contained in jars.zip) is not expanded.

file-1.txt
file-2.txt
jars.zip
\jar
---abc.jar
---xyz.jar
---classes.zip

The uploaded codebase looks like this if the Uploaded file and all contained archives option for Archive Expansion Options is used. The jars.tar is extracted from the initial jars.tar.gz. Once jars.tar archive is expanded, the first-level jars.zip file and the second-level classes.zip file are also expanded.

jars.tar
file-1.txt
file-2.txt
jars.zip
\jar
---abc.jar
---xyz.jar
---classes.zip
---\classes
------Corporation.class
------Employee.class

Multiple Codebase Uploads to the Same Project

If multiple codebases are uploaded to the same codebase path for a given project (and existing codebase files are not deleted), the archives within all the codebases for the project are expanded based on the current Archive Expansion Options configuration. The following process demonstrates this behavior:

If you upload multiple codebases to the same project, best practice is to keep track of the Archive Expansion Options configuration for each upload so that you can apply an appropriate configuration for the subsequent upload.

Open topic with navigation