[libcxx-commits] [libcxx] Refactor dockerfile to support Buildkite AND Github Actions (PR #71954)

[Aiden Grossman via libcxx-commits]

boomanaiden154 wrote:

Is there a reason that these container images and other parts of the libc++ infrastructure (e.g., https://github.com/libcxx/actions) are under/going to be under the libcxx organization rather than the llvm organization? We don't have any container images setup currently, but we do have our own actions repository (https://github.com/llvm/actions). If possible/easy, I would like for the infrastructure to be unified so the rest of LLVM can take advantage of some of the great efforts that libc++ is putting into CI and so libc++ can benefit from future work on common LLVM CI infrastructure.

We don't have any docker images currently, but there was some discussion recently about potentially putting them in https://github.com/llvm/actions along with triggerable/scheduled workflows to build them. Given that these images don't build anything and just install packages, it seems like that may be an option at some point?

Not trying to require/suggest anything be done now, but eventually I would like a mostly unified CI infrastructure across the project that is useful/people enjoy working with. I'm happy to help contribute at some point in the future if the main issue right now is a lack of precedent in the rest of LLVM/people to help do it.

https://github.com/llvm/llvm-project/pull/71954