Support update site management using p2.manager#2130
Conversation
|
Please consider this a draft. It needs some tweaks in the pipeline file to actually work on the project's ci instances; currently it's tested on Orbit's ci instance: https://ci.eclipse.org/orbit/job/wwd-build/ It has been fully tested/verify to produce this update site structure. https://download.eclipse.org/tools/orbit/archive/wildwebdeveloper/updates/ |
|
Do you have a copy of the original image you used for the avatar? https://avatars.githubusercontent.com/u/135985645?s=200&v=4 I found stuff here: https://www.eclipse.org/lists/wildwebdeveloper-dev/msg00005.html But I don't know if the really nice logo is stored somewhere already... |
|
From the |
|
Oh wow, *.svg representations! Awesome. These will be perfect!! |
merks
force-pushed
the
pr-p2.manager
branch
5 times, most recently
from
a6243ec to
77f0c27
Compare
- Rework the entire Jenkins pipeline. - Parameterize to make promotion option and to choose the type of build to promote. - Avoid signing PR content. - Integrate JustJ's p2.manager for promotion. - Display parameter/environment details on the build summary. - Promotion must run on a normal agent with SSH access so stash what's required from the container build for use during promotion. - Upgrade Tycho to 5.0.3. - Add filters to filter out the .git folder of vscode-eslint-ls-package-json/extension checkout to avoid the folder becoming locked as a repository by EGit. - Normalize the bundle and feature names and providers for consistency. - Use `<force>true</force>` for maven-clean-plugin because on Windows some files in a .git folder are marked read-only and need a stronger deletion mechanism. - Use `<skipCheckoutIfExists>true</skipCheckoutIfExists>` for maven-scm-plugin because on Windows, the checkout process often fails for incremental IDE builds where the checkout already exists. - Extract the PGP key to a gpg-keyname property. - Add a pom for promote, included via a promote profile, so that promotion can be done as a separate build step, which is important on the ci server because the container agent does not support ssh access.
2 participants
No description provided.