Skip to content
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

Set up p2.mirrorsURL property in result sites #350

Closed
lcaron opened this issue Jun 25, 2021 · 1 comment
Closed

Set up p2.mirrorsURL property in result sites #350

lcaron opened this issue Jun 25, 2021 · 1 comment
Labels
RELENG Release Engineering

Comments

@lcaron
Copy link
Contributor

lcaron commented Jun 25, 2021

Copy of https://bugs.eclipse.org/bugs/show_bug.cgi?id=373059

As per http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg07400.html


Johannes Faltermeier:

Hi,
I may have a look. I know that a lot of projects use https://wiki.eclipse.org/WTP/Releng/Tools/addRepoProperties for this.
But as this needs the information where the update site is uploaded to, I have to check how to integrate it with the current
build/build jobs

Johannes Faltermeier:

Yes, but today I finally found some time to work on this.
I have a first isolated draft that takes an existing p2 repository and creates a new repository including the p2.mirrorURL:
jfaltermeier@4fc44fa
This could run as part of the release job:

  1. "Mirror" the p2 repository to publish
  2. add p2 mirrorURL and recreate p2 repository
  3. upload this new repository

We could also change the regular build to (optionally) add the mirror urls. However this way one has to know that this build will be uploaded and where it will be uploaded to, so that the correct metadata is added.
Having wrong mirrorURLs is worse than having none at all as far as I know.

Problem with the approach on above branch is, that the category.xml is copied and the urls for the target platform as well. So this should be more closely aligned to the actual build to avoid overhead on release day.

@lcaron lcaron added the RELENG Release Engineering label Jun 25, 2021
@lcaron lcaron added this to the 2.6.0 milestone Jun 25, 2021
@lcaron lcaron modified the milestones: 2.6.0, 2.7.0 Dec 20, 2021
@lcaron lcaron modified the milestones: 2.7.0, 2.8.0 Jun 24, 2022
@lcaron lcaron removed this from the 3.0.0 milestone Mar 7, 2023
@lcaron
Copy link
Contributor Author

lcaron commented Mar 7, 2023

There is no activity on this bug, so I close it.

@lcaron lcaron closed this as completed Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RELENG Release Engineering
Projects
None yet
Development

No branches or pull requests

1 participant