-
Notifications
You must be signed in to change notification settings - Fork 1
Add a second eosdev
tree
#152
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
base: main
Are you sure you want to change the base?
Conversation
This is a precursor to having multiple OSTree outputs. As we need to apply the same preparation scripts to each tree, and we do not want to be duplicating it.
This is going to contain multiple trees, not just `eos` as previously.
This adds a new `eosdev` filesystem, which has the same dependencies as `eos`, but includes everything in the "doc" and "debug" split-rules domains as well. So it is larger, and is intended mainly as a developer toolkit or SDK.
Here are timings from job 51796508698:
The new Compare with the last build of 'main' (job 51758579199 which took the following to build
The reason repo.bst is slow to build is twofold:
A possible workaround could be to add an optimization in the Github Actions workflow as follows:
|
Contents of the repo with this change:
And so on. |
Makes sense and should be. |
This adds a new
eosdev
filesystem, which has the same dependencies aseos
, but includes everything in the "doc" and "debug" split-rules domains as well. So it is larger, and is intended mainly as a developer toolkit or SDK.All trees are built and exported as a single
repo.bst
element. This is the same as before except now the repo.bst has multiple branches, and I moved it out of theeos/
directory.It makes sense to combine all trees in one repo because: