The fastest and easiest explanation of JFrog Artifactory. The how, the what, the where, and the when to use Artifactory. From Developer to Distribution, all your DevOps hopes and dreams explain and more…
Who should attend:
Developers and DevOps engineers who are looking to get an overview of JFrog Artifactory and its common usage scenarios.
– What is JFrog Artifactory and why is it needed?
– Resolve dependencies
Following the webinar, these great questions were asked by the audience and might be of interest to you.
Great question, Anton. The main benefits are that we support far more package types (26 in total), we support a Highly Available setup for scalability and maximum up-time, we store binaries by checksum to save storage through deduplication, and we support replication for multi-site availability of binaries. We also provide 24/7 support.
Indeed. Check out our documentation for the Azure Devops and TFS Artifactory Extension.
The JFrog Artifactory extension for Azure DevOps supports:
Resolving your build dependencies from Artifactory.
Deploying your build artifacts to Artifactory.
Gaining full traceability of your builds by capturing your build-info from your builds and publishing to Artifactory.
So the answer is, yes. This is what most of our plugins do for CI builds.
Artifactory displays XRay scanning results in the artifact and build metadata tabs as well as reporting in the XRay UI.
Hi Ray! Yes, that is exactly what JFrog artifactory is for. You can use the different types of repositories to allow your developers to always have the same versions. It also makes it a little safer, because those versions are stored inside your datacenter as opposed to downloading them from the Internet every time. One benefit I really like as a developer is that I don't have to change my tools (I can do pip install or mvn install) when using Artifactory. We'll get into a lot more detail during the demo, so if you have any questions after that please drop us another Q.
While Artifactory doesn't natively support PEAR packages, you can use the generic repositories in Artifactory to do that. To be honest, I haven't tried it with PEAR packages so your mileage may vary
If you give them versions as you upload them, yes you'll have version information available. If you choose to overwrite them, you'll lose the previous versions.
We have an extension that can be found at our public GitHub repo.
Bintray is the tool used when needing to distribute packages to end-users. You would utilize Artifactory in the CI/CD pipeline and the final step would be to publish the release artifacts to Bintray. Click here
You are correct. A central location for all binaries to be stored and pulled through.
Artifactory does support versioning. This would be connected to the artifact metadata and would be specific to the repository type.