Remove 999999-SNAPSHOT version of Remoting from Artifactory

[basil]

Service(s)

Artifactory

Summary

Core isn't getting Dependabot PRs for Remoting anymore, forcing me to manually update it as in jenkinsci/jenkins#9412, or is getting nonsense PRs like jenkinsci/jenkins#9448. I suspect this is yet another manifestation of #3919. Looks like the current content in https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/remoting/999999-SNAPSHOT/ is a set of snapshots uploaded by @jtnord on May 15, presumably to test jenkinsci/remoting#741, jenkinsci/remoting#742, / jenkinsci/remoting#743, all of which have now been delivered. Assuming the snapshots in https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/remoting/999999-SNAPSHOT/ are no longer needed for testing, can we delete them from the server as a workaround for #3919? Ideally the root cause of the problem would be addressed, but I believe the above action would at least restore the status quo and re-enable automated Dependabot bumps to core.

Reproduction steps

No response

[jtnord]

Ideally the root cause of the problem would be addressed, but I believe the above action would at least restore the status quo and re-enable automated Dependabot bumps to core.

dependabot/dependabot-core#8514 (fixed) - perhaps this one is due to our setup that is using a single mirror for both snapshots and releases?

FWIW, I naively expected a snapshot clean-up policy to be in force, as such I would think that any SNAPSHOT (and certainly CD/incrementals based snapshot 999999-SNAPSHOT version) older than 2 weeks could be safely culled.

[timja]

incrementals are sometimes used for a lot longer than 2 weeks, but yes SNAPSHOTS generally aren't needed for long

[timja]

or we could swap to renovate to avoid this I expect

[timja]

Verified renovate handles this just fine: timja-org/jenkins#6

[timja]

Raised a renovate switch PR for discussion: jenkinsci/jenkins#9459

[basil]

Assuming the snapshots in https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/remoting/999999-SNAPSHOT/ are no longer needed for testing, can we delete them from the server as a workaround for #3919?

Any update on this ticket? I do not see any reason for us not to implement the workaround I described above, especially given that we have been unable to achieve a migration to Renovate.

[timja]

(FWIW renovate issues are resolved and that can proceed not that it blocks removing this: jenkinsci/jenkins#9459)

[dduportal]

Assuming the snapshots in https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/remoting/999999-SNAPSHOT/ are no longer needed for testing, can we delete them from the server as a workaround for #3919?

Any update on this ticket? I do not see any reason for us not to implement the workaround I described above, especially given that we have been unable to achieve a migration to Renovate.

Starting deletion of the artifact. I'll keep a copy of them in case we need to rollback.

[dduportal]

Assuming the snapshots in https://repo.jenkins-ci.org/artifactory/snapshots/org/jenkins-ci/main/remoting/999999-SNAPSHOT/ are no longer needed for testing, can we delete them from the server as a workaround for #3919?

Any update on this ticket? I do not see any reason for us not to implement the workaround I described above, especially given that we have been unable to achieve a migration to Renovate.

Starting deletion of the artifact. I'll keep a copy of them in case we need to rollback.

@basil artifact deleted: can you confirm it is ok on your side?

[basil]

jenkinsci/jenkins#9448 was closed as expected. Thanks!