Overview
When customers use the JFrog CLI to publish builds, particularly with the
jf rt u command, they often notice that the builds are flagged as GENERIC in the JFrog platform instead of the expected package type (e.g., Maven, Python).
This article explains why this happens and why it is considered expected behavior.
Why Is This Expected?
The JFrog CLI offers multiple commands to upload and publish builds to Artifactory. Among these, jf rt u is a generic upload method. When this command is used:
-
Artifactory treats the incoming files as a generic package type because the method of upload does not specify or enforce a particular build type.
-
This behaviour is similar to using cURL or other generic HTTP clients to upload artifacts, where Artifactory has no context about the package type.
-
jf rt u does not inherently carry the metadata needed to classify the build as a specific package type.
-
As a result, Artifactory defaults to classifying such uploads under the GENERIC package type.
Conclusion
If you are seeing your builds flagged as GENERIC while using the jf rt u command, this is not a bug but an expected outcome. To achieve proper classification, use the corresponding package-specific CLI commands. This approach ensures better visibility and organization of your builds in the JFrog platform.