Hi, have some limited experience with Jenkins2 aka Pipeline. IMO this resolves 3) quite nicely.
Regarding 2) imo our deployment with docker compose is dead-end. Docker is simply not designed to support whole machine scenarios white systemd as a init process and predictive networking. while lxc seems to be more suitable, I think we should not hardcode a toy/test environment with lxc. Would propose Terraform here, that ideally should enable our users to use other infra as well. Regarding 1) If we have Terraform for 2) we can even manage our own build infra with that (minus the ppc64le and arm64 slaves). What do you think? Olaf Von meinem iPad gesendet > Am 26.04.2020 um 13:58 schrieb Evans Ye <[email protected]>: > > Hi folks, > > I've been thinking about the revamp of bigtop's CI infra. > Currently what we have is purely a Jenkins cluster with manual managed: > 1. hardware/machine resource > 2. build env: docker, docker compose are all manual installed > 3. job definition: all jobs are manual created and the definition is not > tracked w/ version control system. > > I think for 2,3 there're some tools/solutions that can better manage and > automate the things. So that user can just take the code and build their CI > directly. > > At Yahoo! there's a tool called screwdriver[1] which is a framework to do > CICD, however I don't think it fits our scenario well as we're not facing > production CD. Probably Jenkins 2.0 is more suitable? Anyone has experience > and suggestions? > > [1] https://screwdriver.cd/ > > Evans
