Skip to content

Required retention policy for Y-build artifacts #3328

@HannesWell

Description

@HannesWell

In the context of unifying the clean-up jobs in the RelEng Jenkins instance (#3322) and generally refining the preparation of a new release cycle I stumbled upon the question for how long Y-builds, i.e. the drops and the corresponding p2 repos are actually required and should be retained.

The release notes explain that the Y-builds should be retained if a new release happens shortly after the Eclipse release (usually for odd versions):

- For the Y and P build parameters it's important to know whether or not Y and P builds were run during the release. Since they correspond to java releases on a 6 month cycle, typically they are built in odd-numbered releases.
The existing builds are kept for one release, then cleaned up before the next stream that will have Y and P builds. it's convoluted and I dont want to type it out. Remove Y builds on even releases.

Which matches what has been explained in #3273 (comment).
And given that P-builds are now handled by JDT directly in the JDT JIPP and download space, I think we can disregard P-builds from further discussions.

This leads me to the following more specific questions:

  • For how long should are the Y-build drops at the download page are needed and should be retained?
    For I-builds only all the drops younger than five days are retained and for older I-builds of the current release, only one per week (roughly summarized). Would something similar also fit for Y-build drops? At the moment I cannot tell what actually cleans-up the Y-build drops (but it could be aligned with [Build] Unify clean-ups jobs as Jenkins pipelines and inline scripts #3322).

  • How long should the Y-build p2-repos be retained?

    • According to the doc linked above and my understand of the process, generally some time after the Java-release (i.e. the composite)
    • But are all p2 repos of all builds required until after the release or are you just interested in the latest build's repos anyways (e.g. the last five or so)? Especially as you keep the relevant bundles in the jdt/P-builds repo any ways.
    • And for how long are they required after the release?
      In the past the Y-build repos have been deleted a year later.
  • Are the Y-build drops for Equinox actually interesting for anybody or can they be removed?

And besides the general questions above, I wonder specifically if the old 4.XX-Y-builds, 4.XX-P-builds or 4.XX-P-builds-old directories/composite repositories are still required in the Eclipse downloads area or can be deleted?
I assume the eclipse/updates/P-builds composite can be deleted too?

@stephan-herrmann, @mpalat, @jarthana could you help me by answering these questions? I'm trying to find elegant solutions to clean up Y-builds automatically as far as possible while respecting JDT's demands for releasing the ECJ-patches when new Java versions are released.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions