I would like to have a corporate deployment mechanism for making releases from Bamboo --> Artifactory --> Bintray, with approvals at each step. But, I still want the final Bintray instance to exist within our corporate domain, and off the web.
From Jfrog's website, it seems that there is not a site-hosted version available. Can anyone confirm that?
Yes, Bintray is not available as an on premise installation - yet... :)
(PS. I'm with JFrog)
Related
Recently I heard about bintray sunset starting 1st May 2021. Any idea how to download the artifacts hosted on bintray.
For eg I want to download https://github.com/americanexpress/nodes/ which is hosted on https://dl.bintray.com/americanexpress/maven.
When I open https://dl.bintray.com/americanexpress/maven/io/aexp/nodes/graphql/parent/0.5.0 it responds with forbidden, which I believe would be due to sunset of bintray.
Specifically - this artifact can be found on other repositories.
See search on mvnrepository.com.
In other cases, where the modules are not found, you should contact the developer or project owner asking for the new location of the module. They might need to publish it.
Maybe a dummy question: I have some Maven Artifacts on my maven.pkg.github.com repository and I would like to expose them, just for reading, without configuring the server credentials on settings.xml file?
just answering my own question: until today, July 11th, 2020, there is no option for using GitHub Packages without authorization. So in other words, it's not possible to use anonymous access with GitHub Packages. You can follow the discussion in the GitHub forum: https://github.community/t/download-from-github-package-registry-without-authentication/14407/10
Possible correlated: How to access maven dependecy from GitHub Package Registry (Beta)
First, I know that the upcoming Nexus 3.1 will offer migration of v2 to v3.
I also just applied for the beta migration for v2 to v3 (google forms).
My timing sucks, since the next few days I am going to setup and integrate a new Nexus 3 server.
Is it possible to manually copy my old Maven artifacts (from Nexus v2 server) to this new Nexus v3 server and let Nexus v3 reindex everything?
If so, how?
It's not possible to manually copy, however Nexus Repository Manager 3.1 is now released and you can use it to Upgrade.
As well, the incredible, edible Manfred Moser created this: https://github.com/simpligility/maven-repository-tools/tree/master/maven-repository-provisioner which you can use to take something from a file system into a Maven Repository AKA Nexus Repository Manager. I haven't used it myself, but it's probably exactly what you are looking for.
For those still checking this out, you can also use this simple bash script to import artifacts into Nexus Repository 3: https://gist.github.com/DarthHater/a4f2738e3bd40d242db22633b59dfd63
I'm wondering if it possible to run a private Maven repository using a simple WebDAV?
Apparently, you can use an FTP server.
Long story short, I don't have the necessary rights to install Artifactory our server (plus it's also quite low on resources). Thus, I have setup a basic WebDAV dedicated to being a Maven repository.
I'm getting publishing errors (grails plugin publishing) and was wondering if it was due to WebDAV. If it turns out that it'll never work, I'll just remove this post and my errors post.
Our team decided to start using Artifactory.
I have a Maven plugin that I want to share with outside world. Is there an official Maven repository I can deploy this plugin too ? What are the steps involved ?
Any links to documentation much appreciated
I've been reading http://www.sonatype.com/people/2008/11/adding-a-jar-to-a-maven-repository-with-sonatype-nexus/ but this just seems to describe deploying to internal Nexus repository, wheras I want to deploy to an external repo so any user can use it.
I would recommend:
Setting up an account in Github in order to have a place to host your source code.
Setting up an account in Cloudbee's BuildHive. This is a free Jenkins CI for Open Source projects. This will test your project on every push to Github.
Request rights to publish your project to Maven Central.
The bit with the request will take around up to a day normally and then you'll be able to publish your code directly to Maven Central.