Message: 1
Date: Thu, 25 Oct 2018 14:49:20 -0500
From: Andrew Geissler <geissonator@gmail.com>
To: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: jenkins.openbmc.org ?
Message-ID:
	<CALLMt=pqTesc1qD3wCsv6GTZVRgh2CM1_zF+PM3VVGiDyKf6Qg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

I'd had on my list for a while to move us over to a jenkins instance
running on the same server as our gerrit server. The reasoning was:

1. OpenBMC has grown to the point where it deserves it's own jenkins
instance, and tying it to openpower.xyz doesn't really fit anymore.
2. The gerrit server (and the new jenkins server) are running within
Softlayer which has 24x7 support (openpower.xyz is running on donated
hardware from Rackspace, which is awesome, but support is mainly 2nd
hand via emails to contacts we have at Rackspace)
3. There have been a few instances where the openpower builds have
affected openbmc (and vice versa).

I went ahead and created a new jenkins instance at the above domain,
but haven't done anything with it. I've been kind of wishy-washy on
whether the extra work is really worth it. It's been quite nice having
Joel maintain our openpower.xyz server with all the security updates
and such :)

Thoughts from the community?

Andrew, your email reads like a plea for help with OpenBMC project infrastructure (systems that host OpenBMC servers for Gerrit, Jenkins, and related CI).  If so, it may help to understand the current configuration.  Here is my understanding:

• Are community members comfortable with these Gerrit and Jenkins servers in terms of ownership and administration privileges?
• Should we have a larger variety of CI servers?
  
• Do we need help administering these servers (workload: reboot servers, update Jenkins version, restart CI jobs, etc.)?
• What are the project ideals?

ps: gerrit.openbmc.org will also redirect to our gerrit in case anyone
was interested.

Andrew