About merging patches without tests
by David Caro
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--aRDxp1t8OJxB8Ou24htvVk9dCuM28RTPW
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi!
=46rom time to time we have some patches that are merged to master branch=
es
without having been tested mostly because the developer merges before hav=
ing any
response from the jenkins system.
Merging one of those patches makes any following test run on that branch =
to
fail, and creating a lot of noise and trouble around all patches and jobs=
=2E
So I wanted to stat a little discussion to bring up ideas on how to preve=
nt
that. Some random thoughts:
* -1 the patch at jenkins job start, and reset to 0 on success or infra f=
ailure,
and keep -1 if jenkins failure
* Only send a message to the patch with 'jenkins jobs started'
* Setup zuul as gateway, and make it block the patches if they do not pas=
s the tests
Cheers!
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Email: dcaro(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
--aRDxp1t8OJxB8Ou24htvVk9dCuM28RTPW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJTdO9RAAoJEEBxx+HSYmnDxTMH/iwCYfpzm+6SybWJ/VmSVxTE
tVIMNLnpYLnh483wBcMCrzzLyXnfQK8mqGyh/iBHc6q5TJYjW7NV6ySkABKm8n3z
RhLw9fB0267faD/8QGUjjVwLpF7fAYd2ODVlmCwRVgW8BOGK15xiNdjGZJve38GS
gyl2SuHje5/GFRbZvyLOTwB4yNOHONqzk/m3XFVs2D354WqdgRxXNJapND/UnQEJ
OmL88esg+zli/SDdrc1kKuccd6X/qcor8Jz5iDG4IrGCLPGXKJng0EVv/DG6V1jD
/ucsvV3cgkoLlBvphjTyMC3p55/0j5pbVpFF+ebbR3QXpQfwAA4InKugW7KIBi4=
=Cyei
-----END PGP SIGNATURE-----
--aRDxp1t8OJxB8Ou24htvVk9dCuM28RTPW--
10 years, 8 months
Lists.ovirt.org is full ( or almost )
by Michael Scherer
--=-UrVxZ3AA0NNelAMl+q0p
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Hi,
I just started to receive mail from postfix about insufficient storage
on lists.ovirt.org. So this would have blocked all ML.
I did some cleaning in urgency ( yum cache, etc ), but we would still
need to remove urgently lots of space to avoid seeing the issue again
next week.
So I would like to propose the following :
- short term
- remove the iso in /home/obasan , that's ovirt 3.3, we are at 3.4, so
maybe not needed. that's 1G.
- mid term
- do backup somewhere else than on this server. If the server crash,
having backup on it will be useless :) ( ie, the 9G of gerritt backup )
- have smarter backups. Doing a full backup of gerrit mean there is
lots of duplication. Not sure if we should backup tmp file, for example.
- remove texlive. it take half a gigabit, only for one version of
mediawiki. Which is weird on this server since it is not installed, IIRC
- longer term
- move to a bigger server
- have monitoring of the root partition usage so this can be detected
before it become a issue
- try to have less automated mails sent on ml, as they take space
(logwatch for one, but maybe others)
Any opinions ?
--=20
Michael Scherer
Open Source and Standards, Sysadmin
--=-UrVxZ3AA0NNelAMl+q0p
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAABAgAGBQJTe/CtAAoJEE89Wa+PrSK9vYwQAJqMgs/4k05vMVXg0ZGeoJsP
aBGzNu86Ll+c5/OJpQekjjNBHL2GtQ+3BSdRvAgu8aSRgksEDHt+3jCrOBP/iHQc
vqRFikjFl0DJJPA61zBguL3jtq9U9WKYc6/4fG4h10GzBauTwRMsb22/PqFTDk6m
Un7zNqj25HBBuuHZp2OtxEONZ1d8zW9uHtJhUw5X4ErgMhUYHmPFl+HxSwvAAhD2
zXsLfBPFdh7XPSx1QoU2lJZNx0DZR68pff5guLtLuOQVuRgSNKz0tnTo2BRuTkXK
I8MHsZK74OdTk4AgIBp+hZ+2exL3SLinlKBOhwjc6cRSJbPO0qaEUA+yM0YKTC85
nibGqP16t6ZcZ8Uak2o40/hERIiZKypWvp4yR5DuZgzkTiny7J0ymUAoZn9QCXej
Wtykm7mEA9s03gDo2k0pLpdF4L5lOZO3NvX8SXBEtuJTYzMpM3VGx1tgKbQO4RYv
/NjIFrlOMqdr1ABNCe8HV6amBviHfkwmFLrffaUrShiTVSVXyX5J2U9vf/yN+x4u
TIWGKC726WWEsBBIAD9LECZIhhs5jsi0ho40BsFimTdsmtXC00CbFMy44GBSNPR5
B2Oy27U4QqH0V70RY8eJ4q41wbF7WCWty+q3rMHrk8VnulWdAZU/2k/TfkKmmV82
Z/CFnJMBH1OJEy/+ej/4
=bHv+
-----END PGP SIGNATURE-----
--=-UrVxZ3AA0NNelAMl+q0p--
10 years, 8 months
Fwd: Change in ovirt-log-collector[master]: sos: require and support sos 3.1.1
by Sandro Bonazzola
Hi, there's an error in the gerrit trigger, ovirt-log-collector_master_create-rpms_merged should be started only when the patch is merged.
artifacts from ovirt-log-collector_master_create-rpms_merged are published in nightly snapshot so if we want to check that the package build per patch
we need a ovirt-log-collector_master_create-rpms_gerrit job as we did for other packages.
Can you fix that?
Thanks, Sandro
-------- Messaggio originale --------
Oggetto: Change in ovirt-log-collector[master]: sos: require and support sos 3.1.1
Data: Thu, 22 May 2014 02:32:13 -0400
Mittente: oVirt Jenkins CI Server <gerrit2(a)gerrit.ovirt.org>
A: Sandro Bonazzola <sbonazzo(a)redhat.com>
CC: automation(a)ovirt.org, Simone Tiraboschi <stirabos(a)redhat.com>
oVirt Jenkins CI Server has posted comments on this change.
Change subject: sos: require and support sos 3.1.1
......................................................................
Patch Set 1:
Build Failed
http://jenkins.ovirt.org/job/ovirt-log-collector_gerrit/152/ : SUCCESS
http://jenkins.ovirt.org/job/ovirt-log-collector_master_create-rpms_merge... : FAILURE
--
To view, visit http://gerrit.ovirt.org/27909
To unsubscribe, visit http://gerrit.ovirt.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: I74b1d24cff897d6cc393ee68edfe0d78030877c5
Gerrit-PatchSet: 1
Gerrit-Project: ovirt-log-collector
Gerrit-Branch: master
Gerrit-Owner: Sandro Bonazzola <sbonazzo(a)redhat.com>
Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com>
Gerrit-Reviewer: automation(a)ovirt.org
Gerrit-Reviewer: oVirt Jenkins CI Server
Gerrit-HasComments: No
10 years, 8 months