Let's tackle your two questions one by one, since they tie into how Artifactory handles uploads under the hood:

1. Do partial files exist in JFrog Artifactory during an upload? #

Yes, Artifactory does create partial files during upload, but you won't ever see them in your regular repository views. When an upload starts, Artifactory writes the incoming data to temporary, internal files that are hidden from the web UI, API searches, and repository listings. These temp files are just part of the platform's way to manage ongoing transfers without cluttering your repository with incomplete artifacts.

Once the upload finishes successfully, Artifactory converts these temp files into the finalized artifact that appears in your repo. If the upload fails for any reason (like a network drop), those partial files get cleaned up automatically so they don't leave junk behind.

2. Will the 500MB archive be visible in the repository during the 25-second upload via TeamCity? #

For your specific setup using this Spec Schema:

{ "files": [ { "pattern": "/home/teamcity/.m2/temp/abcdef-*.tar.gz", "target": "abc-repository-xyz/" } ] }

During those 25 seconds of upload, the artifact will not appear in the abc-repository-xyz/ repository listing. The TeamCity Artifactory plugin uses Artifactory's native upload APIs, so it follows the same hidden partial file rule we covered earlier.

The 25-second log entry represents the total time it takes to send the entire file to Artifactory. Only after the full transfer is complete, and Artifactory finishes post-upload tasks (like validating file integrity and updating repository indexes), will the abcdef-*.tar.gz artifact show up in your target repository. If the upload were to fail mid-transfer, you wouldn't find any trace of it in the repo—Artifactory would discard the partial data immediately.

内容的提问来源于stack exchange，提问作者devcodes