AutoDevops support for multiarch
Problem to solve
Support multi-arch builds as part of AutoDevops
- Simone (Software Engineer in Test)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Devon (DevOps Engineer)
Current AutoDevops is x86_64 centric, support ability to target multiple architectures simultaneously (perhaps based on settings->CI/CD configuration of which architectures).
Potential model for how this can work is in the Arm64 CI blog -> https://community.arm.com/developer/research/b/articles/posts/continuous-cross-architecture-integration-with-gitlab
But with autodevops instead of having to manually configure cross-arch, enable it as a drop down setting in gitlab interfaces (maybe even when configuring autodevops)
Permissions and Security
Same as any other Autodevops configuration
Augment autodevops documentation with instructions.
Availability & Testing
Can utilize resources at packet or AWS with Arm servers to verify it works for at least arm and arm64.
What does success look like, and how can we measure that?
Default behavior is to build for multiple architectures allowing all gitlab projects to at least try and build for multi-arch whether they have architecture native resources or not. This can lead to broader packaging of Arm, Power, etc. binaries, packages, and docker images.
What is the type of buyer?
Folks wanting to take advantage of lower cost of ownership cloud resources like AWS graviton.
Is this a cross-stage feature?
Autodevops and UX