...
- lightweight - no service(s) required to run when no jobs are building
- User cannot access the raw Docker socket used by Kubernetes
Cons:
- No access to Docker CLIrequires user to manually set up the build in order to integrate back into NDS Labstracking of build history, status, queues, etc
Result: Ideal and seemingly low-effort solution
...
- CI is very complex - we don't want to be in the business of supporting / fixing Jenkins problems
- we would need to enforce auth, although the 2.7.1 build of jenkins used for the dind tag makes you set up an admin user on first-run
- requires user to manually set up the build in order to integrate back into NDS Labs
Result: I feel like this should be a service that we offer to host for themon NDS Labs, but not necessarily force it on users or manage it for them
...