(Apologies for cross-posting)
Hi all,
This coming Thursday, Shimon Stein will be giving a deep dive into
performance analysis on Foreman instances. We'll be looking at:
1. Installation of tooling in dev env
2. Simple request breakdown (view, sql)
3. Debugging API request
4. Time graph (flamegrap
On úterý 6. června 2017 9:54:12 CEST Tomas Strachota wrote:
> On Mon, Jun 5, 2017 at 4:14 PM, Lukas Zapletal wrote:
> > On Mon, Jun 5, 2017 at 2:48 PM, Tomer Brisker wrote:
> >> My suggestion is that we replace the katello test currently running on
> >> every PR with a test that installs the top
Mass scratch rebuild was a success, we have all packages green except few:
foreman-plugins-nightly-fedora24,
rubygem-smart_proxy_abrt-0.0.8-3.git.0.5b8894c.git.0.5b8894c.fc24.src.rpm
foreman-plugins-nightly-fedora24,
rubygem-foreman_docker-3.0.0-1.fm1_16.git.700.5b8894c.fc24.src.rpm
foreman-plugin
Assuming the DNS still points to the restored koji, you need to do this:
34.226.218.207 koji.katello.org kojihub.katello.org
I kicked off scratch builds of all our packages into nightly, looks
good so far. It is not yet finished but processing at very good rate
of about several tasks per minute (
