On 04/20 10:25, Eyal Edri wrote:
On Wed, Apr 20, 2016 at 10:20 AM, Barak Korren <bkorren@redhat.com> wro= te: =20
On 20 April 2016 at 10:16, Eyal Edri <eedri@redhat.com> wrote:
On Wed, Apr 20, 2016 at 9:28 AM, Barak Korren <bkorren@redhat.com>
wrote:
I'd try that approach first, though the mirror is a good idea th=
at will
probably have to be implemented anyhow once we start adding slav= es, having real info on the network usage/errors will give us insight to actually determine what's the issue, and thus, what's the best solution.
@infra what do you think?
The issue with mirroring is how can you make sure that you mirror = fast enough to enable CI. Even if Gerrit can push to the mirror on patch submission, there will still be some time delta between the submis= sion happening (and the patch event showing up in Jenins) and the mirror being synced. This looks like a nasty race condition. What the mirror essentially does is make sure that bits are copied from Amazom to PHX just once. I wonder if we can get the same bene= fit with a simple HTTP proxy, how proxy-able is the Git HTTP protocol?
I think we should prioritize mirroring the GIT (not gerrit) repos t= o PHX, this will help:
Speed up all post merge jobs and reduce potential of errors from git clone (they will be in the same network) Reduce load (?) from the gerrit server and perhaps reduce errors of=
per
patch jobs that will still run from gerrit.ovirt.org (AMAZON) A longer goal will be either to migrate the gerrit server to PHX or= to find away to properly mirror the gerrit server (but then i fear there mi= ght be race/problem as mentioned)
Please look at my comment about possible race conditions caused by mirroring. Simple mirroring may cause more trouble then its worth. We need to consider proxying instead.
=20 I don't see how a race condition can occur with a merge commit, Can you elaborate? =20 =20 From the gerrit config on jenkins: =20 =20 Replication cache expiration time in minutes =20 If one of the server supports replication events, these events are cached= in memory because they can be received before the build is triggered and t= his plugin gets called to evaluate if the build can run. Cache allows the p= lugin to look if the replication events were already received when it gets = called to evaluate if the build can run. If the time elapsed between this p= lugin gets called and the time the build entered the queue is greated than =
--arYKMy5bKB/hcRo6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 04/20 09:40, David Caro wrote: the the cache expiration time, the plugin will assume that replication events w= ere received and will let the build run.
=20 Changing this value will only take effect when Jenkins is restarted=20 =20
And from the specific server options: Block builds in the queue until the replication events for the configured G= errit slave(s) are received.
=20
=20 =20 =20 =20 --=20 Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel =20 phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) =20 --=20 David Caro =20 Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D =20 Tel.: +420 532 294 605 Email: dcaro@redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com IRC: dcaro|dcaroest@{freenode|oftc|redhat} Web: www.redhat.com RHT Global #: 82-62605 --arYKMy5bKB/hcRo6 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJXFzKPAAoJEEBxx+HSYmnDyEUH/016JkPNKn2PXBgXOBap2ocm tgsELdNz77v0aom34FfsB70iMYvKJNkjLYkxwTldhz4orfuL6ZWOiBRR0VuQw2lT UKUK3iUmFewB5E+q/VEUlkIJEEi99WtA/2dw5nIroc5G7SF1BirHHNpsP4BAH4bV YRX46K/4t5OYJQIjGzQEh2N+tVCpH5P5V/Dw7rjz2juefjSxVDILd3nmhag9FXQe K7ci1ORDnRFbiZKmLjaWxqBzijaZG+drxDSQU9vNcE8PY9IQPARhp2jsW/TYigIj 7qZDqqQCwUJnN5QkAWaBOSg624S8BxPwwE15+WxKJdtqk7d43163HR8/1XKDHBI= =K/Fk -----END PGP SIGNATURE----- --arYKMy5bKB/hcRo6--