We're using Bintray (via JCenter) to publish our open source Android packages. JFrog are ending Bintray and telling us to use JFrog Platform, but the OSS option for that product is not available yet.
What am I missing?
Related
When I create release bundles in Jfrog and then move them to a satellite, all artifacts on the satellite are placed in repositories from where I can download them. But they are stored there without reference to a specific release bundle. I can download any combination of artifacts. I am asking me if there is a possibility to download artifacts not from the repository but from the release bundle.
For that i would suggest to use the Jfrog CLI:
https://www.jfrog.com/confluence/display/CLI/JFrog+CLI
Thats a tool developed in Jfrog itself for ease of use.
After you configure it (`jfrog config add`) you can use the following command to download all the files of a release bundle:
`jfrog rt dl --bundle bundle_name/bundle_version`
In JCenter net.sourceforge.plantuml:plantuml module doesn't have version 1.2020.15 in maven-metadata.xml.
But, in Maven Central this module has this version listed in maven-metadata.xml.
However, I managed to successfully download net.sourceforge.plantuml:plantuml:1.2020.15 JAR from JCenter. Look like, in this case JCenter redirects me to repo.jfrog.org/artifactory/libs-release-bintray repository, which contains this version. And this artifactory repository also has this version listed in maven-metadata.xml.
JCenter documentations says that it's a mirror of Maven Central. The question is: shouldn't maven-metadata.xml be fully synchronized? It's critical for me, as I use a tool to update my dependencies to latest versions and this tool doesn't update plantuml to the latest version, because this versions isn't listed in maven-metadata.xml in JCenter.
The Synchronisation of packages in Bintray will happen from JCenter to Maven Central. So packages in Maven Central will not always be in JCenter when users request a package that does not exist on JCenter (hence, on-demand), Bintray will try to retrieve it from remote repositories and store it in JCenter.
Therefore, JCenter does not duplicate everything under Maven Central (to be reflected in JCenter). If the package is already linked to JCenter and once the latest version is uploaded to your Bintray account it will be mirrored in JCenter and then you can sync the latest version with Maven Central from your Bintray account.
Please refer the below link for more information on how Maven Central sync works with Bintray:
https://www.jfrog.com/confluence/display/BT/Syncing+with+Third-Party+Platforms
The webpage for JFrog's Artifactory OSS makes it seem like it's part of OSS https://www.jfrog.com/open-source/#conan. I'm trying it out in a Docker container and "Conan" doesn't show up as a clickable option in new local repository.
Am I misunderstanding what is the available in Artifactory OSS or did I set something up wrong?
The Artifactory community edition for C/C++ is a new version of Artifactory offering free support for Conan repositories
No, conan repositories are not available in Artifactory OSS.
If in https://www.jfrog.com/open-source/, you go to "Artifactory OSS", then "Compare to PRO", you will see the full comparison matrix between them.
Conan repositories are not available in Artifactory OSS. You need to pay for the Pro version. For Nexus OSS, there is a plugin available. We will be testing this in house shortly.
https://exchange.sonatype.com/details?extension=5596417057
The latest version of Nexus Repository Manager OSS supports a new artefact types: Docker, npm, RubyGems. But it appears to drop support for artefact formats supported in the previous version: Maven, P2, OBR, Yum. Why is that?
Maven should be there, in fact we setup default repos for it when it starts. P2, OBR, Yum have not been rebuilt for Nexus Repository Manager 3 as of yet. Yum will likely be the next up, P2 and then maybe OBR (jury is still out on if we have enough people using it to include it in the core product).
If you'd like to kickstart any of these, we would love that. A community member recently created an APT format for himself:
https://github.com/mpoindexter/nexus-repository-apt
You might be able to follow his example and create one for OBR for example.
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.