Skip to content

Conversation

@froozeify
Copy link
Member

@froozeify froozeify commented Jan 7, 2026

The modifications are based on docker recommendation

  • Switching to build matrix to improve build performance (using native platform should have a 10-20x performance gains)
    Native arm runner are available for free github project (so no problem for glpi-project/docker-images) or for paid enterprise plan
  • Update the cache logic so it's cached per platforms
  • Use github actions to simplify the build logic
  • Migrate to docker/metadata instead of ENV
  • Update docker sbom to have a docker scout rating of A (only done when image is pushed)
    Screenshot from 2026-01-08 12-05-44

@froozeify froozeify changed the title Swith to build matrix + docker/metadata Switch to build matrix + docker/metadata Jan 7, 2026
@froozeify froozeify force-pushed the ci-matrix-build-and-cache-update branch from 89259fd to 899c777 Compare January 7, 2026 14:12
@froozeify froozeify changed the title Switch to build matrix + docker/metadata Switch to native arm builder + docker/metadata Jan 8, 2026
@froozeify froozeify requested a review from cedric-anne January 8, 2026 11:35
@froozeify froozeify marked this pull request as ready for review January 8, 2026 11:35
@froozeify froozeify force-pushed the ci-matrix-build-and-cache-update branch from 6670b53 to 1571f44 Compare January 12, 2026 15:49
Copy link
Member

@cedric-anne cedric-anne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMHO, we should keep only the .github/workflows/_glpi-build.yml and trigger calls directly from GLPI.

Also, maybe we could add a on.push event with a step that uses default inputs, to trigger the ci build (without pushing images) when the workflow is updated.

Comment on lines 4 to 7
# Source GLPI environment variables (includes GLPI_MARKETPLACE_DIR detected at build time)
if [ -f /etc/glpi_env ]; then
export $(cat /etc/glpi_env | xargs)
fi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue with this is that it will erase any custom value defined by the admin.
We could decide to not support it if we do not find a better solution.

Copy link
Member Author

@froozeify froozeify Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't find any cleaner way to support both 10 and 11 at the build time. I guess that's why it was in the set variable step before.

I could rollback this commit and let it in the set variable step

@froozeify froozeify marked this pull request as ready for review January 14, 2026 12:22
@froozeify froozeify force-pushed the ci-matrix-build-and-cache-update branch from 0d9b5d2 to 07ca706 Compare January 14, 2026 13:33
@froozeify froozeify linked an issue Jan 14, 2026 that may be closed by this pull request
@cedric-anne cedric-anne merged commit 986d051 into main Jan 15, 2026
4 checks passed
@cedric-anne cedric-anne deleted the ci-matrix-build-and-cache-update branch January 15, 2026 09:02
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.

Add "plugins" folder to volume

3 participants