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

Use submodule to include the equinox.binaries #467

Closed
wants to merge 1 commit into from

Conversation

laeubi
Copy link
Member

@laeubi laeubi commented Jan 4, 2024

Currently the user needs to checkout two repositories side-by-side and specify the location of it at the commandline to fully build equinox.

This includes the other repository as a submodule now to make it easier for users/buildscripts as they can see the content of both repositories as one linear directory structure.

@laeubi laeubi requested a review from akurtakov January 4, 2024 14:45
@akurtakov
Copy link
Member

Please verify that releng.aggregator repo works with this change. I assume some scripts will need adjustments for submodules.

@iloveeclipse
Copy link
Member

Can that have negative effect on platform aggregator / SDK build (including all the scripts/jobs) - they assume all "other" repositories to be "usual" git repos, and may fail to perform proper git commands to checkout right state?

@laeubi
Copy link
Member Author

laeubi commented Jan 4, 2024

Please verify that releng.aggregator repo works with this change. I assume some scripts will need adjustments for submodules.

Will do once it is working here, as the aggregator build already uses submodules a lot I don expect anything specifically here but who knows :-)

Copy link

github-actions bot commented Jan 4, 2024

Test Results

   24 files  ±0     24 suites  ±0   11m 22s ⏱️ +38s
2 150 tests ±0  2 105 ✅ ±0  45 💤 ±0  0 ❌ ±0 
2 194 runs  ±0  2 149 ✅ ±0  45 💤 ±0  0 ❌ ±0 

Results for commit 04ea5e2. ± Comparison against base commit 1d9eb47.

♻️ This comment has been updated with latest results.

Currently the user needs to checkout two repositories side-by-side and
specify the location of it at the commandline to fully build equinox.

This includes the other repository as a submodule now to make it easier
for users/buildscripts as they can see the content of both repositories
as one linear directory structure.
@laeubi
Copy link
Member Author

laeubi commented Jan 8, 2024

Build is now working, so next would be to test it with the aggregator build....

@laeubi
Copy link
Member Author

laeubi commented Jan 8, 2024

@HannesWell
Copy link
Member

Did you verify that building the natives still works?
I haven't looked into the build config yet, so cannot tell if including the binaries repo as sub-module is really relevant, but we should be sure.

@laeubi
Copy link
Member Author

laeubi commented Jan 10, 2024

The binaries should never be build here, the binary repos is only used to copy the files into the feature.

@iloveeclipse
Copy link
Member

Shouldn't we use git-lfs instead? That would make everything even easier.

@laeubi
Copy link
Member Author

laeubi commented Jan 10, 2024

Shouldn't we use git-lfs instead? That would make everything even easier.

I won't mind but last time git-lfs makes "everything easier" it took > 1 year to do so.

@iloveeclipse
Copy link
Member

This is irrelevant, discussion took so long because there were no one to work on, not because git-lfs.
We are talking about decisions that have long term effects.
From my point of view same criteria apply here as for SWT.
So instead of changing to git modules and still have multiple repos, we could simplify that and have one repo.

@laeubi
Copy link
Member Author

laeubi commented Jan 10, 2024

This is irrelevant, discussion took so long because there were no one to work on, not because git-lfs.

So can you work on merging both repos using git-lfs? I have only limited knowledge about equinox binary repos and can only tell this one wants to copy a file that is there to execute the maven build, while for SWT there was a lot more involved, on the other hand the binaries here are only build on request...

So for me any solution would sufficient as long as it is performed.

@HannesWell
Copy link
Member

This is already discussed in eclipse-equinox/equinox.binaries#1.

I think it would be good to continue there.

I'll try to have a look at making the binaries compile on demand automatically like SWT in the equinox pipeline (although this is somewhat orthogonal).

@laeubi
Copy link
Member Author

laeubi commented Jan 11, 2024

I'll try to have a look at making the binaries compile on demand automatically like SWT in the equinox pipeline (although this is somewhat orthogonal).

Before butting effort in it please note that the goal is not to compile the binaries as part of the build, they are changing very infrequently (sometimes not for years) and therefore seems a bit waste of CI resources to compile them with each change.

@laeubi laeubi closed this Mar 12, 2024
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.

4 participants