All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: Andrew Geissler <geissonator@gmail.com>
Cc: openBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Gerrit and Jenkins server transition May 20th (Today)
Date: Mon, 23 May 2022 05:40:59 +0000	[thread overview]
Message-ID: <CACPK8XdOdO17kmHgWXbW-zW4AsxM43PghOTzya0Ttq1AytLfKQ@mail.gmail.com> (raw)
In-Reply-To: <6B50C209-4CB6-40DD-B2A0-50B5B207598D@gmail.com>

On Mon, 23 May 2022 at 00:06, Andrew Geissler <geissonator@gmail.com> wrote:
>
> ok, jenkins and gerrit are back up and fairly functional. Still a few kinks
> to be worked out in the #infrastructure discord channel. Please report
> any issues there or to me on the mailing list.
>
> Autoassign of reviewers does not seem to be working in gerrit so
> for now you’ll have to manually add reviewers to new reviews.
>
> I need to work with the Linux Foundation to add a SPF record
> for the gerrit.openbmc.org domain to help make the emails not
> look like spam to people.
>
> I’ll work on getting opengrok back up and going sometime this week.
>
> During this maintenance window I moved the apps to a different server,
> I upgraded gerrit and jenkins to the latest stable versions, and I
> moved our gerrit server to the gerrit.openbmc.org domain. This way
> we’ve now got gerrit, jenkins, and opengrok on the same domain.
> The old gerrit domain should still work fine (I just redirect it to
> the new domain)

Thanks for your work maintaining our services Andrew.

It's a minor detail but I think it's helpful that these services are
on the same domain now.

Cheers,

Joel

      reply	other threads:[~2022-05-23  5:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 14:12 Gerrit and Jenkins server transition May 20th Andrew Geissler
2022-05-20 12:24 ` Fwd: Gerrit and Jenkins server transition May 20th (Today) Andrew Geissler
2022-05-23  0:06   ` Andrew Geissler
2022-05-23  5:40     ` Joel Stanley [this message]

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=CACPK8XdOdO17kmHgWXbW-zW4AsxM43PghOTzya0Ttq1AytLfKQ@mail.gmail.com \
    --to=joel@jms.id.au \
    --cc=geissonator@gmail.com \
    --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.