Usage: PUT /api/build?project= -H "Content-Type: application/json" --upload-file build.json Consumes: application/json (application/vnd.org.jfrog.build.BuildsByName+json)Example: curl -X PUT " :8081/artifactory/api/build?project=projectKey" -H "Content-Type: application/json" --upload-file build.jsonSample format:
Since: 3.5.0Security: Requires a valid user with deploy permissions and Bintray credentials defined (for more details, please refer to Bintray Settings).Usage: POST /api/build/pushToBintray/build.name/build.number?gpgPassphrase=[&gpgSign=true\false]Consumes : application/json (application/vnd.org.jfrog.artifactory.build.BintrayDescriptorOverrideParams+json) Sample Input:
Jfrog Artifactory Encrypted Password Crack
Description: Folder InfoFor virtual use, the virtual repository returns the unified children. Supported by local, local-cached and virtual repositories. Since: 2.2.0Security: Requires a privileged user (can be anonymous)Usage: GET /api/storage/repoKey/folder-pathProduces: application/json (application/vnd.org.jfrog.artifactory.storage.FolderInfo+json)Sample Output:
Description: File InfoFor virtual use the virtual repository returns the resolved file. Supported by local, local-cached and virtual repositories.Since: 2.2.0Security: Requires a privileged user (can be anonymous)Usage: GET /api/storage/repoKey/filePathProduces: application/json (application/vnd.org.jfrog.artifactory.storage.FileInfo+json)Sample Output:
Description: Returns the last modified item at the given path. If the given path is a folder, the latest last modified item is searched for recursively. Supported by local and local-cached repositories.Since: 2.2.5Notes: Requires Artifactory ProSecurity: Requires a valid user with deploy permissionsUsage: GET /api/storage/repoKey/item-path?lastModifiedProduces: application/json (application/vnd.org.jfrog.artifactory.storage.ItemLastModified+json)Sample Output:
Description: Item Properties. Optionally return only the properties requested. Since: 2.2.1Security: Requires a privileged user (can be anonymous)Usage: GET /api/storage/repoKey/itemPath?properties[=x[,y]]Produces: application/json (application/vnd.org.jfrog.artifactory.storage.ItemProperties+json)Sample Output:
Description: Returns an archive file (supports zip/tar/tar.gz/tgz) containing all the artifacts related to a specific build, you can optionally provide mappings to filter the results, the mappings support regexp capturing groups which enables you to dynamically construct the target path inside the result archive file.Notes: Requires Artifactory ProSince: 2.6.5Security: Requires a privileged user (can be anonymous)Usage: POST /api/archive/buildArtifacts -H "Content-Type: application/json"Consumes: application/json (application/vnd.org.jfrog.artifactory.build.BuildArtifactsRequest+json)Produces: application/zip (for zip archive type), application/x-tar (for tar archive type), application/x-gzip (for tar.gz/tgz archive type)Sample Usage:
Description: Create new directory at the specified destination.Notes: You can also attach properties as part of creating directories.Security: Requires a user with 'deploy' permissions (can be anonymous)Usage: PUT /repo-key/path/to/directory/Produces: application/json (application/vnd.org.jfrog.artifactory.storage.ItemCreated+json)Sample Output:
Description: Deploy an artifact to the specified destination.Notes: You can also attach properties as part of deploying artifacts.Security: Requires a user with 'deploy' permissions (can be anonymous)Usage: PUT /repo-key/path/to/artifact.extProduces: application/json (application/vnd.org.jfrog.artifactory.storage.ItemCreated+json)Sample Usage:
Description: Deploy an artifact to the specified destination by checking if the artifact content already exists in Artifactory.If Artifactory already contains a user readable artifact with the same checksum the artifact content is copied over to the new location and returns a response without requiring content transfer.Otherwise, a 404 error is returned to indicate that content upload is expected in order to deploy the artifact.If the X-Checksum-Deploy header is set to false, the artifact will be uploaded successfully with a 201 response, even if it didn't exist before, and submitted checksums will have status Uploaded: Identical. Notes : You can also attach properties as part of deploying artifacts. Security : Requires a user with 'deploy' permissions (can be anonymous) Usage : PUT /repo-key/path/to/artifact.ext Headers : X-Checksum-Deploy: true, X-Checksum-Sha1: sha1Value, X-Checksum-Sha256: sha256Value, X-Checksum: checksum value (type is resolved by length) Produces : application/json (application/vnd.org.jfrog.artifactory.storage.ItemCreated+json) Since : 2.5.1 Sample Output :
Security: Requires a valid user with deploy permissions and Bintray credentials defined (for more details, please refer to Bintray Settings). Usage : POST /api/bintray/push?descriptor=pathToDescriptorFile[&gpgPassphrase=passphrase][&gpgSign=true\false] Since : 3.5.0 Produces : application/json (application/vnd.org.jfrog.artifactory.bintray.BintrayPushResponse+json)
Description: Copy an artifact or a folder to the specified destination. Supported for local, remote and federated repositories only. Optionally suppress cross-layout module path translation during copy.You can test the copy using a dry run.Copy item behaves similarly to a standard file system and supports renames. If the target path does not exist, the source item is copied and optionally renamed. Otherwise, if the target exists and it is a directory,the source is copied and placed under the target directory.Notes : Requires Artifactory Pro Security : Requires a privileged user (can be anonymous) Usage : POST /api/copy/srcRepoKey/srcFilePath?to=/targetRepoKey/targetFilePath[&dry=1][&suppressLayouts=0/1(default)][&failFast=0/1] Produces : application/json (application/vnd.org.jfrog.artifactory.storage.CopyOrMoveResult+json) Since : 2.2.2 Sample Output :
Description: Moves an artifact or a folder to the specified destination. Supported by local repositories only. Optionally suppress cross-layout module path translation during move.You can test the move using dry run.Move item behaves similarly to a standard file system and supports renames. If the target path does not exist, the source item is moved and optionally renamed. Otherwise, if the target exists and it is a directory, the source is moved and placed under the target directory.Notes: Requires Artifactory ProSecurity: Requires a privileged user (can be anonymous)Usage: POST /api/move/srcRepoKey/srcFilePath?to=/targetRepoKey/targetFilePath[&dry=1][&suppressLayouts=0/1(default)][&failFast=0/1]Produces: application/json (application/vnd.org.jfrog.artifactory.storage.CopyOrMoveResult+json)Since: 2.2.2Sample Output:
Description: Returns the replication configuration for the given repository key, if found. Supported by local and remote repositories. Note: The 'enableEventReplication' parameter refers to both push and pull replication.Notes: Requires Artifactory ProSecurity: Requires an admin userUsage: GET /api/replications/repoKeyProduces: application/json (application/vnd.org.jfrog.artifactory.replications.ReplicationConfigRequest+json) Since: 3.1.1 (update to include / exclude pattern on replication added in Artifactory 7.24.4)Sample Usage:
Description: Add or replace replication configuration for given repository key. Supported by local and remote repositories. Accepts the JSON payload returned from Get Repository Replication Configuration for a single and an array of configurations. If the payload is an array of replication configurations, then values for cronExp and enableEventReplication in the first element in the array will determine the corresponding values when setting the repository replication configuration. Notes: Requires Artifactory ProSecurity: Requires an admin user Usage: PUT /api/replications/repoKeyConsumes: application/json (application/vnd.org.jfrog.artifactory.replications.ReplicationConfigRequest+json)Since: 3.1.1 (update to include / exclude pattern on replication added in Artifactory 7.24.4) Note: Enabling the checkBinaryExistenceInFilestore flag requires an Enterprise+ license. For more information, see Repository Replication. This flag will work for multi-push replication as well. Sample Usage: 2ff7e9595c
Comments