Archive Expansion for Multiple Codebases Uploaded 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:
|
1.
|
Create project1 and upload the codebase codefiles1.zip, using the Uploaded file only option. The contents of codefile1.zip are extracted. Archives in these contents are not expanded. |
|
2.
|
Upload codefile2.zip to the same project (at the same codebase path), this time using the Uploaded file and all contained archives. (Keep in mind that codebase1.zip was previously expanded with no further expansion of any archives in its contents.) Now all archives at all levels are expanded within the codefile1 and codefile2 codebases. |
|
3.
|
Upload codefile3.zip to the same project, this time using Uploaded file and first-level archives only. Now only the first-level archives in all three codebases are expanded. |
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.