Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-2821

Remove unused incrementals

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      TBD whether we need to do this, but /incrementals repo uses 300GB, while actual /releases has just 220GB. If not now, then at some point in the not too distant future.

       

        Attachments

          Issue Links

            Activity

            Hide
            danielbeck Daniel Beck added a comment -

            Jesse Glick What criteria would be useful to determine which incrementals to delete? Artifactory offers the following in metadata:

            • Created date
            • Number of downloads
            • Date of last download

            The trivial one would be number of downloads = 0; but we may have scrapers than make this somewhat meaningless.

            Show
            danielbeck Daniel Beck added a comment - Jesse Glick What criteria would be useful to determine which incrementals to delete? Artifactory offers the following in metadata: Created date Number of downloads Date of last download The trivial one would be number of downloads = 0; but we may have scrapers than make this somewhat meaningless.
            Hide
            jglick Jesse Glick added a comment -

            From my PoV anything older than, say, a year can probably be deleted. Simple enough. In the unlikely event you still have an active PR referring to such an old version as a dependency which you are resurrecting work on, you should just switch the dep to a newer version (release or incremental, depending on whether or not the upstream PR has been released yet). You can also recreate the old incremental version locally (for non-CI exploration) via

            cd …/upstream
            git checkout $commithash
            mvn -Dset.changelist -DskipTests install
            
            Show
            jglick Jesse Glick added a comment - From my PoV anything older than, say, a year can probably be deleted. Simple enough. In the unlikely event you still have an active PR referring to such an old version as a dependency which you are resurrecting work on, you should just switch the dep to a newer version (release or incremental, depending on whether or not the upstream PR has been released yet). You can also recreate the old incremental version locally (for non-CI exploration) via cd …/upstream git checkout $commithash mvn -Dset.changelist -DskipTests install
            Hide
            jglick Jesse Glick added a comment -

            I should prioritize JENKINS-50804 though.

            Show
            jglick Jesse Glick added a comment - I should prioritize JENKINS-50804 though.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              danielbeck Daniel Beck
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: