6 ms·
I can and it would require porting my entire CI workflow to machine. We use a lot of docker-executor specific stuff, and if I'm going to spend the time to port
by lflux 4y ago
I can and it would require porting my entire CI workflow to machine. We use a lot of docker-executor specific stuff, and if I'm going to spend the time to port several thousand lines of CI config, I can just port it to a different CI platform instead.
- mtlynch 4y agoOh, gotcha. You have CI for multiple architectures already and you want to add arm64? I was thinking it was brand new code you wanted to write, but I get why you wouldn't want to rewrite everything.
- lflux 4y agoJust on amd64 right now, we want to move to add support for arm64. Sadly we adopted CircleCI early on and make heavy use of their support for multiple containers - if you specify a list of containers in a Docker job, it will execute the tests in the first container and connect the other containers as "data" containers (think redis, mysql et c) for use in tests.
- dugab 4y agoIf you need services for your tests in CI, you might want to look at what Gitlab CI "services" https://docs.gitlab.com/ee/ci/services/ https://docs.gitlab.com/ee/ci/services/