Need help with other JFrog products?
JFrog Enterprise+
JFrog Mission Control
JFrog Xray
JFrog Distribution
JFrog Pipelines
JFrog Bintray
JFrog Access
JFrog CLI
Section | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
To get account on OJO you must first have an account on Bintray.
maven2gradle
org.github.jbaruch.maven2gradle
After your request has been approved by the Bintray Team (usually within a few hours), you'll receive a confirmation email on the inclusion of your package in JCenter and the creation of your new OJO account.
Tip | ||
---|---|---|
| ||
OJO is just a regular Artifactory Pro server, so getting familiar with Artifactory is recommended. |
Info | ||
---|---|---|
| ||
When requesting an OJO account for a repository belonging to an Bintray organization, the permissions in OJO will be granted to all the organization members, not only the member who asked for the OJO account. |
Once your OJO account has been created, you (and all the team members in the case of an organization) should be able to login to OJO using your Bintray username and API key as the password.
You will see that a folder corresponding to the Maven Group ID has been created in OJO in the oss-release-local
and the oss-snapshot-local
repositories:
You have deploy permissions to these folders:
There is nothing unusual about working with repositories in OJO. You can configure your build tool to resolve release and snapshot dependencies from the libs-release
and the libs-snapshot
OJO virtual repositories, respectively; and to deploy build snapshots to the oss-snapshot-local
repository. As long as the <groupId>
in your pom (for Maven) or the project.group
(for Gradle) matches the group ID you requested during onboarding, the deployment should succeed.
Please consult the Artifactory documentation on how to set up Maven or Gradle for resolution and deployment.
Note | ||
---|---|---|
| ||
In order to release and promote snapshots to Bintray you need to deploy a Build Info BOM to Artifactory. The easiest way to achieve this automatically it is to use the Build Integration feature of Artifactory or the Gradle Artifactory Plugin; These and other options are described in the next section. |
Currently, you have two ways to deploy artifacts to Bintray:
Promotion from Jenkins is performed by invoking a custom "snapshotsToBintray" promotion plugin. Here's what you need to do:
oss-release-local
and oss-snapshot-local
as release and snapshot targets, respectively.Anchor | ||||
---|---|---|---|---|
|
1.0-SNAPSHOT
will be released to Bintray as version 1.0
.yyyyMMdd.HHmmss
) to the release version. Values of true
, y
or 1
will cause the timestamp suffix to be appended.If you don't use Jenkins or if you need fully automated promotion, you can issue an HTTP PUT request that will trigger promotion and release to Bintray. Promotion still operates on a Build Info BOM, previously saved in Artifactory.
Here's what you need to do:
Execute the build promotion plugin call. The call accepts the same parameters as the invocation of Jenkins promotion plugin. Here's an example using CURL:
Code Block |
---|
curl -X POST -u bintrayUser:apiKey http://oss.jfrog.org/api/plugins/build/promote/snapshotsToBintray/buildName/3 |