Write latest master build to downloads.eclipse.org

[akurtakov]

Using https://download.eclipse.org/pde/builds/master/ as destination so it can be tested more broadly.
Mainly motivated to have a permanent download space which wasn't there as discovered in
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4172

[akurtakov]

@HannesWell wdyt? It's not giving any immediate benefits but it's one more step towards decoupling it from Platform.
Once this is in I plan on trying to add this repo in releng.aggregator and have the pde bundles be used from it instead of rebuilt during I-build.

[github-actions]

Test Results

   291 files  +   98     291 suites  +98   59m 54s ⏱️ + 27m 32s
 3 526 tests ±    0   3 468 ✅ +    2   58 💤  -  1  0 ❌  - 1 
10 875 runs  +3 677  10 699 ✅ +3 608  176 💤 +70  0 ❌  - 1 

Results for commit 6b3dcd5. ± Comparison against base commit f26df87.

♻️ This comment has been updated with latest results.

[HannesWell]

@HannesWell wdyt? It's not giving any immediate benefits but it's one more step towards decoupling it from Platform.

Regarding this change, the binaries published should probably be jar-signed, shouldn't they?

Once this is in I plan on trying to add this repo in releng.aggregator and have the pde bundles be used from it instead of rebuilt during I-build.

Please don't do that before the cycles are cut. As long as there are other plugins in the SDK that depend on PDE, we should not do that. Otherwise we probably make the situation worse than it is now.

Looking at the Dependencies of pde.build (which is the plugin on that actually every other plugin in PDE depends on) I see mainly the following plugins with PDE dependencies:

• org.eclipse.e4.tools
• org.eclipse.e4.tools.emf.editor3x
• org.eclipse.e4.tools.emf.ui

Plus ant.test.core/ui and jdt.apt.tests.
And having a quick look at that I would say that it is probably possible, but not trivial to change.

[laeubi]

I see mainly the following plugins with PDE dependencies:

See

• Migrate the e4 tools to PDE #898

[akurtakov]

Regarding this change, the binaries published should probably be jar-signed, shouldn't they?

Also done.

[laeubi]

Please don't do that before the cycles are cut. As long as there are other plugins in the SDK that depend on PDE, we should not do that. Otherwise we probably make the situation worse than it is now.

See

• Migrate the e4 tools to PDE #1081

[laeubi]

@akurtakov now the e4 tools are part of this repo we maybe want to include the features in the updatesite

[akurtakov]

@akurtakov now the e4 tools are part of this repo we maybe want to include the features in the updatesite

Should be done now.

[HannesWell]

Looks good for a first attempt.

But on the long run we should discuss and have a more sophisticated repo structure.

[akurtakov]

Looks good for a first attempt.

But on the long run we should discuss and have a more sophisticated repo structure.

Definetly, esp with regards of releases and etc. We are far from such state yet and every step that would make things easier to go to the next step while not causing issue for anything else should be taken.

[laeubi]

Looks good for me

[laeubi]

I don't know yet why but now master build fails :-\

https://ci.eclipse.org/pde/job/eclipse.pde/job/master/554/

[iloveeclipse]

See #1095

[akurtakov]

It still fails even after the test fix is in and this is most likely caused by signing as it fails in the very same way as figured in eclipse-platform/eclipse.platform.releng.aggregator#1673 .

[akurtakov]

If I fail to figure what's going wrong with comparison in the next few hours I'll revert the signing part only.