-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Reduce Artifactory storage and bandwidth use #4533
Comments
I mean the atlassian one should be fairly easy to resolve, just swap it to includes only. |
Update: we've granted access to @darinpope to Artifactory so he can drive this topic:
|
I wonder if we still need the jcenter-cache as well? |
Let's now track work for each subject on associated issues:
=> there might be subsqiuent follows up issue. |
Yes, we do. It has artifacts which have been deleted from remotes as far as I remember. Worth checking this subject but let's not get carried away: if @darinpope is able to solve the atlassian and incremental, we'll see immediate results to share with JFrog |
@dduportal I've dug around and cannot find a way to implement MFA on my admin account. Is that another switch you need to set on my account? |
My mistake: MFA is only available on the JFrog portal, not on Artifactory. Sorry for wasting your time on this one. Ref. #4472 (comment):
@darinpope I've set your account as admin, you should have access now |
Service(s)
Artifactory
Summary
Jenkins artifact storage use has increased to greater than 10 TB and bandwidth use has recently increased significantly, almost to the bandwidth use prior to the work done in:
jcenter
, andoss.sonatype.org-releases
repositories frompublic
virtual repository; reconfigure Atlassian remote repositories #3842JFrog sponsors open source without charging the open source project. They have asked us to reduce our storage to less than their 5 TB open source sponsorship plugin. We also want to reduce our bandwidth use to be much closer to the bandwidth we were using in early 2024.
Reproduction steps
The text was updated successfully, but these errors were encountered: