All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Reynolds <joseph-reynolds@charter.net>
To: openbmc@lists.ozlabs.org
Subject: Re: jenkins.openbmc.org server infrastructure
Date: Mon, 29 Oct 2018 09:42:45 -0500	[thread overview]
Message-ID: <30bb965b-31a4-b402-cfeb-855b92f6e53c@charter.net> (raw)
In-Reply-To: <mailman.13.1540515603.32722.openbmc@lists.ozlabs.org>

[-- Attachment #1: Type: text/plain, Size: 2564 bytes --]


> 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:

- GitHub (source code mirror), hosted by GitHub at 
https://github.com/openbmc (various repos).
  - Gerrit (code review tool), hosted by 
https://gerrit.openbmc-project.xyz (and redirected from gerrit.openbmc.org).
  - Jenkins (CI server), hosted by https://openpower.xyz, proposal to 
move to a new server at https://jenkins.openbmc.org.
  - Various CI build and test servers (run jobs on different hardware 
architectures).
  - See history in 
https://lists.ozlabs.org/pipermail/openbmc/2016-July/004280.html

Then reading questions into the email:

  * 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
>


[-- Attachment #2: Type: text/html, Size: 5195 bytes --]

       reply	other threads:[~2018-10-29 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.13.1540515603.32722.openbmc@lists.ozlabs.org>
2018-10-29 14:42 ` Joseph Reynolds [this message]
2018-10-30 15:33   ` jenkins.openbmc.org server infrastructure Andrew Geissler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30bb965b-31a4-b402-cfeb-855b92f6e53c@charter.net \
    --to=joseph-reynolds@charter.net \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.