kurt.r.taylor at gmail.com
Thu Nov 1 07:46:26 AEDT 2018
On 10/30/18 10:49 AM, Andrew Geissler wrote:
> Based on some recent discussion in this area, I'm contemplating
> forming an Infrastructure workgroup. The focus would be on improving
> our CI infrastructure and the scripts and tools around it.
Actually, when I was suggesting this, I was thinking even broader. There
is a need for folks interested in keeping *all* of our services and
system resources healthy, not just our test systems.
I would think that the Test WG would take care of defining and
automating test, the infrastructure WG would take care of the resources
that Test needed for CI.
That said, it makes sense for the first order of work for the Infra WG
would be to bolster the CI Test services and resources. There will be
big early overlaps for sure.
I'll be happy to help as I can, at least initially. I have CI/DevOps
experts in my network that I can get recommendations from as well.
Kurt Taylor (krtaylor)
> There's been a lot of great community effort already around our CI
> build scripts.
> Some thoughts on goals:
> - Documenting the existing flow
> - Alternatives to existing flow (ability to use freely provides clouds
> for open source projects, ...)
> - Managing the Jenkins nodes - Bringing new nodes online quickly
> (chef, puppet, ansible?)
> - Managing and optimizing the CI flow (repository CI, meta CI, openbmc CI)
> -- Which systems do we build?
> - Process for adding hardware CI (mechanism for individuals to add HW
> CI to gerrit commits)
> - Optimizations to existing scripts (docker building, CI, QEMU)
> - Gerrit, Jenkins, and build node periodic update process
> - Overall maintenance and responsibilities for infrastructure
> Thoughts or interest?
More information about the openbmc