You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our project would like to use a consistent buildx build both locally and on ci. We believe this is a general pattern that could benefit other projects as well.
Our general setup is as follows:
multiple platforms configured (arm64, amd64)
build phase is correctly invoking only the local architecture
NOTE: uses the mavendocker-container buildx driver, resulting in slower builds due to I/O inherent with the docker-container driver. We would like to avoid this extra I/O on local builds.
We don't ever run the deploy phase locally - so we never build multiple platforms (and thus don't need the docker-container output later in the docker-maven-plugin's lifecycle)
For continuous integration, we use a ci Maven profile that skips the build phase, allowing the multiple platform builds that occur at this time to happen simultaneously (which speeds up most of our docker modules)
We'd like to be able to set the buildx builder-name to be default to allow the use of the default buildx driver on local builds. This has the following benefits:
Faster builds due to lower I/O and buildx improvements
Better visual output
Consistent docker execution with our ci approach (some modules seem to build differently when not using buildx - we have not narrowed down why yet, but it doesn't matter with this proposed change - but suspect we have some buildx-specific features).
Description
Our project would like to use a consistent buildx build both locally and on ci. We believe this is a general pattern that could benefit other projects as well.
Our general setup is as follows:
maven
docker-container
buildx driver, resulting in slower builds due to I/O inherent with thedocker-container
driver. We would like to avoid this extra I/O on local builds.docker-container
output later in thedocker-maven-plugin
's lifecycle)ci
Maven profile that skips the build phase, allowing the multiple platform builds that occur at this time to happen simultaneously (which speeds up most of our docker modules)We'd like to be able to set the buildx
builder-name
to bedefault
to allow the use of the default buildx driver on local builds. This has the following benefits:We have a simple PR for this change with a corresponding unit test.
Info
mvn -v
) : 3.9.6The text was updated successfully, but these errors were encountered: