Skip to content

ci: create shared build workspace and filters - #3249

Draft
Lewluu wants to merge 3 commits into
mainfrom
create-xilinx-shared-build-workspace
Draft

ci: create shared build workspace and filters#3249
Lewluu wants to merge 3 commits into
mainfrom
create-xilinx-shared-build-workspace

Conversation

@Lewluu

@Lewluu Lewluu commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Pull Request Description

Implement shared build workspace. Currently, each runner contain an independed build workspace with cache. This results in heavy ocuppied space per runnner workspace. With this implementation, current runners can build in parallel using the same build workspace as well, using project build path .lock file mecahnism and storing non built projects and re-checks.
Another feature is the filtering of projects to build based on paths from the git changes.

Please replace this with a detailed description and motivation of the changes.
You can tick the checkboxes below with an 'x' between square brackets or just check them after publishing the PR.
If this PR contains a breaking change, list dependent PRs and try to push all related PRs at the same time.

PR Type

  • Bug fix (change that fixes an issue)
  • New feature (change that adds new functionality)
  • Breaking change (has dependencies in other repos or will cause CI to fail)

PR Checklist

  • I have followed the Coding style guidelines
  • I have complied with the Submission Checklist
  • I have performed a self-review of the changes
  • I have commented my code, at least hard-to-understand parts
  • I have build all projects affected by the changes in this PR
  • I have tested in hardware affected projects, at the relevant boards
  • I have signed off all commits from this PR
  • I have updated the documentation (wiki pages, ReadMe etc), if applies

@Lewluu Lewluu self-assigned this Aug 5, 2026
@github-actions github-actions Bot added the CI label Aug 5, 2026
@Lewluu
Lewluu force-pushed the create-xilinx-shared-build-workspace branch 13 times, most recently from 588bbb5 to 9dd0585 Compare August 11, 2026 12:38
@analogdevicesinc analogdevicesinc deleted a comment from CLAassistant Aug 12, 2026
@Lewluu
Lewluu force-pushed the create-xilinx-shared-build-workspace branch from bda8ea1 to 9ec9878 Compare August 12, 2026 10:41
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Lewluu
❌ cseci
You have signed the CLA already but the status is still pending? Let us recheck it.

@Lewluu
Lewluu force-pushed the create-xilinx-shared-build-workspace branch 4 times, most recently from d549b48 to 0b6a65a Compare August 12, 2026 14:29
Lewluu added 2 commits August 12, 2026 21:26
Implement shared build workspace. Currently, each runner
contain an independed build workspace with cache. This
results in heavy ocuppied space per runnner workspace.
With this implementation, current runners can build in
parallel using the same build workspace as well, using
project build path .lock file mecahnism and storing
non built projects and re-checks.
Another feature is the filtering of projects to build
based on paths from the git changes.

Signed-off-by: Iuliu Antoniu-Popovici <iuliu-antoniu.popovici@analog.com>
Using the shared build workspace would always cause fresh build.
Replacing the cmake cache old values with new ones based on current
runner directory will ensure that the build won't run fresh when
building from another workspace.

Signed-off-by: Iuliu Antoniu-Popovici <iuliu-antoniu.popovici@analog.com>
@Lewluu
Lewluu force-pushed the create-xilinx-shared-build-workspace branch 5 times, most recently from dadb3bd to 3383d28 Compare August 13, 2026 12:45
Signed-off-by: Iuliu Antoniu-Popovici <iuliu-antoniu.popovici@analog.com>
@Lewluu
Lewluu force-pushed the create-xilinx-shared-build-workspace branch from 3383d28 to 41ddfa4 Compare August 13, 2026 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants