From: "Nikolai Kondrashov" <Nikolai.Kondrashov@redhat.com>
To: "Cristian Marussi" <cristian.marussi@arm.com>,
"Tim Bird" <Tim.Bird@sony.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Guillaume Tucker" <guillaume.tucker@collabora.com>,
"Alice Ferrazzi" <alicef@gentoo.org>,
"Iñaki Malerba" <imalerba@redhat.com>,
kernelci@groups.io, "Vishal Bhoj" <vishal.bhoj@linaro.org>,
automated-testing@lists.yoctoproject.org
Subject: Re: #KCIDB v9 release
Date: Mon, 3 Jan 2022 13:49:42 +0200 [thread overview]
Message-ID: <5e7e52fd-8318-7ac0-b4d1-fd65acab6cb8@redhat.com> (raw)
In-Reply-To: <16BCB376A7748BB3.24346@groups.io>
Hi everyone,
On 12/1/21 20:01, Nikolai Kondrashov wrote:
> I'm proud to announce the release and deployment of KCIDB v9.
>
> Please see the detailed list of changes at
> https://github.com/kernelci/kcidb/releases/tag/v9
>
> Most important changes are listed below.
...
> * Rename the submission queue topic for production from "kernelci_new" to
> "kcidb_new", and for playground from "playground_kernelci_new" to
> "playground_kcidb_new". This is done to unify KCIDB namespace inside Google
> Cloud and to help automate deployments. The old names will keep working
> until Dec 31.
...
> * Remember to switch to the new submission topics (above) by Dec 31!
I see that there's still some data being sent to the old topics "kernelci_new"
and "playground_kernelci_new". Please switch to using "kcidb_new" and
"playground_kcidb_new" instead, respectively.
I will remove the old ones on Wednesday at 12:00 EET. After that, submissions
to the old topics will be failing and no data sent there will reach KCIDB.
Nick
next parent reply other threads:[~2022-01-03 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16BCB376A7748BB3.24346@groups.io>
2022-01-03 11:49 ` Nikolai Kondrashov [this message]
2022-01-05 10:10 ` #KCIDB v9 release Nikolai Kondrashov
2021-12-01 18:01 Nikolai Kondrashov
2022-06-07 6:11 ` Dmitry Vyukov
2022-06-07 13:43 ` Nikolai Kondrashov
2022-06-07 14:35 ` Dmitry Vyukov
2022-06-07 14:36 ` Nikolai Kondrashov
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=5e7e52fd-8318-7ac0-b4d1-fd65acab6cb8@redhat.com \
--to=nikolai.kondrashov@redhat.com \
--cc=Tim.Bird@sony.com \
--cc=alicef@gentoo.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=cristian.marussi@arm.com \
--cc=dvyukov@google.com \
--cc=guillaume.tucker@collabora.com \
--cc=imalerba@redhat.com \
--cc=kernelci@groups.io \
--cc=vishal.bhoj@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox