--lc9FT7cWel8HagAv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Sagi is looking into this, the issue is that we are not triggering on draft created, nor draft published nor commit message only changes. Sagi is adding triggering for draft published event. For this specific patch, there's no way to retrigger (as the gerrit trigger patch only supports emulating the patchset created event for now). There's an open task to add a way on triggering in some other way, but for = now any of us can force it manually (or a rebase or any code change will also retrigger a job). I've triggered it manually for now [1] but that will not give you any revie= ws in you patch (another shortcoming of the trigger plugin). You might have to wait until it starts running for the below page to exist. [1] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/43 On 11/09, Piotr Kliczewski wrote:
The build was never triggered and I am not able to trigger manually a build for [1] patch. Can someone please take a look? =20 =20 [1] https://gerrit.ovirt.org/#/c/47637 _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
--=20 David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization R&D Tel.: +420 532 294 605 Email: dcaro@redhat.com Web: www.redhat.com RHT Global #: 82-62605 --lc9FT7cWel8HagAv Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWQOeEAAoJEEBxx+HSYmnDu9oH/389xNEmvQ0WTlj/487sxBQi +vrHCY1/TShy7giZbSPw8X6sUAotCtWcrILyRP7s5GbyQjIaZPD/2U+tZltIPxgi b63dIJsHZH5kVhVyxcMoQIAwhIgcnUGbInu1wjtcHPjlvlTtOyxYitFJnHwu+zeW 5pIup85sZz9HTt505XkRiBD5hWfk0mD2gMAfUCLGNN1+LvZs0UT2XZom/IF12Shs il9z803zE91q2RrpB793d6uy1wVGWrPNBvXARAO0ngdA9pAW6LMx2BpNLnWCLEF9 7YJbAX0e/ab3P5c4LsqxSOGe9CO6Luam8G5catVe+12m1wmlCb4YN52sv4M/VUI= =kTVl -----END PGP SIGNATURE----- --lc9FT7cWel8HagAv--