-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Artifact repositories #4
Comments
It seems me that conceptually, it's only file storage (we would have done this with FTP in the 90ies). Do you see an important concept that I'm missing here? |
I am not an expert on the topic but maybe @goranpaues is talking about something like this: https://jfrog.com/artifactory/ |
Yes, a repository like Artifactory is what I meant. To me, it's a file storage server with practical features like versioning, retention policies and licensing control. In the Java world, it is common to use Gradle or Maven scripts to build an application. In those scripts, any dependent libraries or components (artifacts!) will then be retrieved from the repository in a standarized way when the application is built. |
+1 for licensing control |
Merged with #24 Thanks again @goranpaues |
Built versions of applications need to be stored in some kind of artifact repository, from where they can be downloaded and installed.
Examples of solutions here are Artifactory and Nexus.
The text was updated successfully, but these errors were encountered: