I have been trying to upload my application specific JARs to the JFrog Artifactory using the rest API but couldn't find any methods to include the group id and the artifact id like maven does.
This command does deploy the jar to repository but without the groupId and artifactId;
curl -u username:password -X PUT "http://xx.xx.xxx.xx:8081/artifactory/libs-release-local/mail-1.4.3.jar" -T mail-1.4.3.jar
Are there any way that I could mention the Group id and Artifact Id while uploading the JARS to artifactory using Jfrog Rest API ?
There is nothing that will do it automatically for you, but you can definitely specify a full path that includes the groupId, artifactId and version of your artifact exactly like Maven would, i.e:
curl -u username:password -T mail-1.4.3.jar "http://xx.xx.xxx.xx:8081/artifactory/libs-release-local/org/someOrg/mail/1.4.3/mail-1.4.3.jar"
(p.s - you don't need to specify -XPUT if you specify -T)
BTW - unlike the REST API, the Artifactory UI does actually have the ability to fill in the full maven coordinates for you during upload. Have a look here:
https://www.jfrog.com/confluence/display/RTF/Deploying+Artifacts#DeployingArtifacts-DeployingMavenArtifacts
Related
I'm confused about how to perform this operation, it almost seems like it's not supported. Looking at the docs I see no examples for deleting a specific build version: https://www.jfrog.com/confluence/display/CLI/CLI+for+JFrog+Artifactory#CLIforJFrogArtifactory-DiscardingOldBuildsfromArtifactory
I use build discarding now, but that's not what this is. I want to remove a specific build version and its corresponding artifact, not use --max-days or --max-builds. How is this possible? I want to delete the build AND the artifact.
I use Jfrog to host an internal helm repo, helm has no built-in command to delete a chart from a remote repo.
For deleting a specific artifact of a build using jfrog cli run
jfrog rt delete --build build-name/build-number
Parse --dry-run to know which artifacts would have been deleted.
More info on CLIforJFrogArtifactory-DeletingFile.
I have been using Artifactory OSS and set it up with a deploy script. The deploy script also uploads some images with curl to a generic repo immediately after setup. Now I need to upload docker images as well so I made the switch to Artifactory JCR. JCR won't accept my curl push until I have accepted the EULA. Is it possible to accept it automatically? I have been looking for a EULA flag in files and the database but without success.
My environment is a docker container with artifactory-jcr:6.17.0 in Kubernetes.
One more option is to use this curl in the script, after JFrog Container Registry is installed:
curl -XPOST -vu username:password http://${ArtifactoryURL}/artifactory/ui/jcr/eula/accept
For deployments using a scripts, you can sign the JCR EULA in a YAML configuration file you have prepared ahead. As JCR is based on Artifactory, the configuration files are usually similar.
Create a YAML file at $JCR_HOME/etc/artifactory.config.import.yml
Add the below
GeneralConfiguration:
eula:
accepted: true
OnboardingConfiguration:
repoTypes:
- docker
- helm
Make sure to format it as YAML before writing to the file
I am trying to search for all files that are in my repo on Artifactory. I have Go installed, and am using Jfrog to query the search using:
jfrog rt s https://URL/artifactory/generic-sgca/
Which returns:
[Info] Searching artifacts...
[Info] Found 0 artifacts.
[]
Why is it not returning all folders in this repo? I believe my config is setup correctly too.
You are not supposed to be specifying the https://url/artifactory when using search function in the CLI.
you can check the CLI's search help using jfrog rt s -h and you'll see that the usage is:
jfrog rt s [command options] <search pattern>
where search pattern should:
Specifies the search path in Artifactory, in the following format: <repository name>/<repository path>
The URL is actually a command option --url=http://myurl:myport/artifactory which you can leave out if you use jfrog rt config to set the Artifactory server details before you run the search command.
You can read more and find some snippet example here
I'm using Travis(https://travis-ci.org/Orange-OpenSource/elpaaso-dbaas-wsdl) to build my maven project. I'm able to deploy artifacts and buildInfo to OSS JFrog and to promote snapshot to bintray. But my artifact is pushed into the wrong package.
Expected to be here: bintray.com/elpaaso/maven/elpaaso-dbaas-wsdl/view
But it's here : bintray.com/elpaaso/maven/elpaaso-plugins-management/1.63.12/view#files
I'm using curl to promote to bintray
curl --silent -X POST -u user:password http ://oss.jfrog.org/api/plugins/build/promote/snapshotsToBintray/elpaaso-dbaas-wsdl/12
How to choose target package when promoting from OSS Jfrog to bintray ?
As described in the user guide, the REST API call includes build name and build number as a part of the URI (not repo name and id as in your example).
Bintray details (the repo and the package) are associated with maven groupId that you provided during the request for inclusion of the package to jcenter.
I would like to make a permalink to the latest snapshot version of an artifact in Artifactory. If we are on 1.0-SNAPSHOT, I would like a URL that downloads the latest 1.0-SNAPSHOT JAR. I can find the latest artifact by locating the artifact on our server at http://hostname/artifactory/libs-snapshot/groupId/artifactId/1.0-SNAPSHOT/. Other than checking the timestamps, I can figure out which one if the latest by opening maven-metadata.xml and matching metadata/versioning/snapshot timestamp and buildNumber with a JAR in the same directory. This could be scripted, but ideally Artifactory already has a way to construct a permalink in this manner. Does Artifactory provide such a URL?
Doing the normal query for the entry with artifactId-1.0-SNAPSHOT.jar in the URL name should return automatically the latest snapshot.
See the doc here
One thing: This is base either on the latest creation date if no pom present, or latest creation of the pom if there are some. Mixing pom and non-pom deployment may results in strange results!
I tried using shell script and it worked for me.
Step1: Get an encrypted password for your user account by clicking on user name or create a common user. Go to using your secure password section in the following link
http://www.jfrog.com/confluence/display/RTF/Centrally+Secure+Passwords
Step 2: In your local machine create a temp folder and type this curl(may be wget for windows) command:
curl -o tmp/foo.jar --user <username>:<encrypted_password> <artifactory_url>/list/libs-snapshot-local/com/search/foo/1.0/foo-1.0-SNAPSHOT.JAR
Your foo.jar in tmp folder is latest version. If we dont give timestamp as like above, it will download latest artifact in that version. Hope this helps!
This might be helpful:
How to download the latest artifact from Artifactory repository?
Although there is no permalink ability in the free version of Artifactory, it can be scripted easily as you suggest. I have provided a quick script to do that in the referenced question.
Hope it helps.
Another portable option is to use the maven command line:
mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:get -DartifactId=[artifactId] -DgroupId=[groupId] -Dversion=[version] -Ddest=[dest file]
This works for me (no search API, just direct artifact URL):
curl -O -J --user <username>:<encrypted_password> http://hostname/artifactory/libs-snapshot/groupId/artifactId/1.0-SNAPSHOT/artifactId-1.0-SNAPSHOT.jar
Basically using 1.0-SNAPSHOT in the artifact name downloads the latest version of 1.0-SNAPSHOT snapshot.