Sometimes the documentation was sort of messy because there are many possibilities for where and how to install Artifactory. So sometimes, I got a little bit lost, and it wasn't very clear which path in the documentation to take. But when I tested things and could just follow the manual, that was working fine. Sometimes the UI was not working as expected. Users were complaining that they didn't see their Artifactory, but they had to clear their browser cookies or something. It was just the browser taking some information from the caches of the user's PC. So sometimes, this can be better. The UI could get laggy; maybe because our environment reached its limit. We had a large number of assets. It could take time for all the artifacts to load. If there could be some better features for me, it would be being able to upgrade Artifactory directly from the UI. I think that is something that JFrog maybe offers with the cloud solution, but I don't know. For some reason, we still use the standalone on-premise solution. Maybe that version doesn't provide this functionality.
We're looking for something that has additional reporting capabilities on data growth and data aging. This goes back to storage lifecycle management so that the actual Artifactory itself can provide these reports to either the administrators or the users. I don't know if it has those capabilities. That's something we have to look into regarding the self-service dashboard, but the tool itself having those capabilities would be great rather than trying to do it at the underlying storage hardware layer. We moved from the internal Derby DB to the Postgres database last year or the year before. Because of the size and amount of objects in our instance, we were probably going to exceed the recommended number of objects for the default Derby DB. So, we moved to Postgres. The other option was MySQL. There weren't a lot of options. It could've been better. I felt that there wasn't a lot of knowledge base or support available to help with that migration for us. We had reached up to Artifactory support to see if they had a professional services type of engagement to do that, and they didn't have anything of that nature. So, we were left to our own devices to manage that database migration.
The latest version that I am using is 7.41. It has been upgraded graphics-wise, but there is a bit of slowness. They can improve the graphical interface for the admin jobs and make it faster. However, we rarely use the graphical interface. We only use it for enrollment, permissions, proxy bypassing, etc. All other things related to pushing or pulling images are done in the terminal mode via pipeline script. If it comes with an option for version control, it would be great. Instead of going to Git, everything can be done in a single tool.
We are currently having some migration issues and errors. It would be helpful if we could get some proper documentation on how to fix the current environment where we are currently struggling. I would like to see written technical support instead of having to contact them directly.
Jira integration is something that I would like to see improved. I have already talked with their support, and there is a development ticket open for that. If there is any Xray-related information that should be shared within the development pipeline for security remediation or license or whatever, then I would like to see a ticket to be created automatically in the right project. That's something that's not working with Jira Cloud at the moment. Hopefully, they will be able to address that. I've got Xray set up, which gives me notifications on when new vulnerabilities are found related to my binaries. One thing that would be nice to have is if that notification could be limited to the age of the binary. For instance, if a binary is already more than a year old and there are several new versions of it available, it would be interesting that you still get notified that there is a new security vulnerability available in that version when it's not found in a newer version. That's one thing that could be of interest.
JFrog Artifactory is a powerful enterprise product designed for storing and managing different types of binaries, including artifacts, Dockery majors, and builds created as part of the CI process. It offers end-to-end binary management capabilities, integration with different environments and cloud providers, and a centralized repository with multiple repositories for different artifacts.
Artifactory has helped organizations modernize and automate their development operations, reducing...
Sometimes the documentation was sort of messy because there are many possibilities for where and how to install Artifactory. So sometimes, I got a little bit lost, and it wasn't very clear which path in the documentation to take. But when I tested things and could just follow the manual, that was working fine. Sometimes the UI was not working as expected. Users were complaining that they didn't see their Artifactory, but they had to clear their browser cookies or something. It was just the browser taking some information from the caches of the user's PC. So sometimes, this can be better. The UI could get laggy; maybe because our environment reached its limit. We had a large number of assets. It could take time for all the artifacts to load. If there could be some better features for me, it would be being able to upgrade Artifactory directly from the UI. I think that is something that JFrog maybe offers with the cloud solution, but I don't know. For some reason, we still use the standalone on-premise solution. Maybe that version doesn't provide this functionality.
We're looking for something that has additional reporting capabilities on data growth and data aging. This goes back to storage lifecycle management so that the actual Artifactory itself can provide these reports to either the administrators or the users. I don't know if it has those capabilities. That's something we have to look into regarding the self-service dashboard, but the tool itself having those capabilities would be great rather than trying to do it at the underlying storage hardware layer. We moved from the internal Derby DB to the Postgres database last year or the year before. Because of the size and amount of objects in our instance, we were probably going to exceed the recommended number of objects for the default Derby DB. So, we moved to Postgres. The other option was MySQL. There weren't a lot of options. It could've been better. I felt that there wasn't a lot of knowledge base or support available to help with that migration for us. We had reached up to Artifactory support to see if they had a professional services type of engagement to do that, and they didn't have anything of that nature. So, we were left to our own devices to manage that database migration.
The latest version that I am using is 7.41. It has been upgraded graphics-wise, but there is a bit of slowness. They can improve the graphical interface for the admin jobs and make it faster. However, we rarely use the graphical interface. We only use it for enrollment, permissions, proxy bypassing, etc. All other things related to pushing or pulling images are done in the terminal mode via pipeline script. If it comes with an option for version control, it would be great. Instead of going to Git, everything can be done in a single tool.
We are currently having some migration issues and errors. It would be helpful if we could get some proper documentation on how to fix the current environment where we are currently struggling. I would like to see written technical support instead of having to contact them directly.
Jira integration is something that I would like to see improved. I have already talked with their support, and there is a development ticket open for that. If there is any Xray-related information that should be shared within the development pipeline for security remediation or license or whatever, then I would like to see a ticket to be created automatically in the right project. That's something that's not working with Jira Cloud at the moment. Hopefully, they will be able to address that. I've got Xray set up, which gives me notifications on when new vulnerabilities are found related to my binaries. One thing that would be nice to have is if that notification could be limited to the age of the binary. For instance, if a binary is already more than a year old and there are several new versions of it available, it would be interesting that you still get notified that there is a new security vulnerability available in that version when it's not found in a newer version. That's one thing that could be of interest.
The documentation is a bit sparse. That's our only complaint.