Skip to content

Conversation

@HannesWell
Copy link
Member

@HannesWell HannesWell commented Jun 24, 2025

Previously the I/Y-builds only added the just built p2-repository to their corresponding composite repository and a separate job, running twice a day, has trimmed down that repositorie's content afterwards to retain only two children.
This made the setup's and job configurations more cumbersome and the repository content less predictable.
Furthermore the the pruning only removed children that where located directly within the composite's directory and not absolute references to other repositories.

This simplifies this task by removing the oldest children while adding the new, just built one, making sure the composite contains at most three children. Just as indicated in

The buildtools composite repository, that was also cleaned up with this, is not updated for some time as it now only provides a snapshot repository as of:

Permanently fixes

Previously the I/Y-builds only added the just built p2-repository to
their corresponding composite repository and a separate job, running
twice a day, has trimmed down that repositorie's content afterwards to
retain only two children.
This made the setup's and job configurations more cumbersome and the
repository content less predictable.
Furthermore the the pruning only removed children that where located
directly within the composite's directory and not absolute references to
other repositories.

This simplifies this task by removing the oldest children while adding
the new, just built one, making sure the composite contains at most
three children.

Permanently fixes
- eclipse-platform#3123
@HannesWell HannesWell linked an issue Jun 24, 2025 that may be closed by this pull request
@HannesWell HannesWell merged commit e1f36dc into eclipse-platform:master Jun 24, 2025
4 of 6 checks passed
@HannesWell HannesWell deleted the prune-composite-immediatly branch June 24, 2025 21:56
@HannesWell
Copy link
Member Author

Today's two I builds demonstrated that both cases work as intended, adding a new child doesn't reach the limit and the child is just added and the case that the repo already has its target size and the oldest child is removed when a new one is added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove 4.36 from 4.37-I-builds

1 participant