shci
Joined 5 years ago
Karma
4
Submissions
12
Member since
May 23
Recent submissions
Comment · 5 years ago
I wrote an installer that sets up a VirtualBox VM, installs docker in it and sets everything up with a single command. It has a few drawbacks but might be good enough for a lot of use cases: https://github.com/dziemba/mobymac
Comment · 5 years ago
On macOS you can always run things in a VirtualBox VM if you're only concerned about Docker Desktop, not Docker itself.
Here's a convenient installer for that: https://github.com/dziemba/mobymac
It does however have some rather annoying limitations. Also no Apple Silicon support.
Comment · 5 years ago
How about Periskop? https://github.com/soundcloud/periskop
Comment · 5 years ago
That seems like a good approach when you have only a few pipelines. Unfortunately we have roughly 1000 pipelines/repos that all our our somewhat custom tooling that spawns up more docker containers with various volume mounts. For better or worse we're stuck with that for now, and we don't really have the capacity or desire to migrate all these projects to a completely new way of doing things.
So ideally the worker would just run commands on the worker host directly (no containers) and lets the containerization up to the executed jobs themselves. I'm not sure that's possible with Concourse (it looks like it does that for windows+darwin, but not on linux).
Comment · 5 years ago
Looks interesting! So if I'm reading that correctly, the server-side is hosted by them but then you have the workers on your own infrastructure? That's seems like the best of both worlds (if it works ;).
Comment · 5 years ago
I had a brief look at Concourse. It looks promising but seems to be very focused on running things in containers.
That approach is great when starting out fresh, but with our 1000 existing pipelines (that mainly use Makefiles as entrypoints, which then use docker with custom tooling) it would be a pain to migrate.
Does anyone have experience running Concourse at scale? Does it also support running tasks "old-school" (without any containers)?
Comment · 5 years ago
What advantages (in terms of CI setup) does that have over using GitHub.com?
Comment · 5 years ago
This seems like a great solution, I will definitely investigate that. I'm a bit worried about feature completeness (Vault integration comes to mind). Does anyone have experience with using this on a large scale?
Comment · 5 years ago
Maybe "not maintained" was a bit harsh. Until end of 2020 ThoughtWorks spent a lot of resources on developing new features. This has stopped now, so I'm a bit concerned that while GoCD seems to be actually maintained (there are some very recent bugfix commits in the repo), general development of new features might be slow/nonexistant in the future.
Here's the official announcement: https://groups.google.com/g/go-cd/c/EXwfvZZeLrM
Comment · 5 years ago
That sounds interesting. We're currently using GitHub for hosting our repos (with a ton of integrations, so probably can't switch anytime soon). Is it possible to use GitLab CI with the repos being hosted on GitHub?