Yaml-ized jobs: Can they be unstable?
Hey, is there a way how a yamlized job can become unstable? I'd liek to run some sanity node tests after a run, and mark a run as unstable if this happens. According to the jenkins docs, a job is unstable if one or more publishers fail. Can this be achieved with yamlized jobs? - fabian
----_com.boxer.email_1064904379815452 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 V2l0aCB0aGUgc3RhbmRhcmQgY2kgaXMgbm90IHBvc3NpYmxlLCBhcyB0aGUgaWRlYSBvZiAndW5z dGFibGUnIGFuZCAnZmFpbHVyZScgaXMgcXVpdGUgYW1iaWd1b3VzIGFuZCB1c3VhbGx5IGxlYWRz IHRvIGNvbmZ1c2lvbi4KClNvIHdlIGRlY2lkZWQgbm90IHRvIGhhdmUgdGhhdCB0aGlyZCBzdGF0 ZSwgcnVucyBlaXRoZXIgcGFzcywgb3IgZG8gbm90LgoKWW91IGNhbiBwcmludC9hcmNoaXZlL2xv ZyBhbnl0aGluZyB5b3Ugd2FudCB0byBhbGxvdyB5b3UgaGVscCBkZWJ1Z2dpbmcgdGhlIGlzc3Vl LCBidXQgb24gdGhlIGNpIHNpZGUsIHRoZSBkZWNpc2lvbiBpcyB0byAtMSBvciBub3QgYSBwYXRj aCwgc28ganVzdCB0d28gc3RhdGVzLgoKT3V0IG9mIHRoZSBzdGFuZGFyZCB5b3UgY2FuIGRlZmlu ZSBwb3N0LWJ1aWxkIHNjcmlwdHMgdGhhdCBjYW4gbW9kaWZ5IHRoZSBzdGF0ZSBvZiB0aGUgam9i ICh5b3UgY2FuIHNldCBpdCBhcyBmYWlsZWQsIHVuc3RhYmxlIG9yIGV2ZW4gcGFzcyBhIGpvYiB0 aGF0IG90aGVyd2lzZSB3b3VsZCBiZSBtYXJrZWQgYXMgZmFpbGVkKS4KClRob3VnaCBmb3IgdGhl IHJlYXNvbnMgSSBleHBvc2VkLCBJIGRvbid0IHJlY29tbWVuZCB0aGF0LgoKRGF2aWQgQ2FybwoK RWwgMjUvNC8yMDE2IDg6MzAgcC4gbS4sIEZhYmlhbiBEZXV0c2NoIDxmZGV1dHNjaEByZWRoYXQu Y29tPiBlc2NyaWJpw7M6CgpIZXksCgppcyB0aGVyZSBhIHdheSBob3cgYSB5YW1saXplZCBqb2Ig Y2FuIGJlY29tZSB1bnN0YWJsZT8KCkknZCBsaWVrIHRvIHJ1biBzb21lIHNhbml0eSBub2RlIHRl c3RzIGFmdGVyIGEgcnVuLCBhbmQgbWFyayBhIHJ1biBhcwp1bnN0YWJsZSBpZiB0aGlzIGhhcHBl bnMuCkFjY29yZGluZyB0byB0aGUgamVua2lucyBkb2NzLCBhIGpvYiBpcyB1bnN0YWJsZSBpZiBv bmUgb3IgbW9yZSBwdWJsaXNoZXJzIGZhaWwuCgpDYW4gdGhpcyBiZSBhY2hpZXZlZCB3aXRoIHlh bWxpemVkIGpvYnM/CgotIGZhYmlhbgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fXwpJbmZyYSBtYWlsaW5nIGxpc3QKSW5mcmFAb3ZpcnQub3JnCmh0dHA6Ly9s aXN0cy5vdmlydC5vcmcvbWFpbG1hbi9saXN0aW5mby9pbmZyYQoK ----_com.boxer.email_1064904379815452 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 PHAgZGlyPSJsdHIiPldpdGggdGhlIHN0YW5kYXJkIGNpIGlzIG5vdCBwb3NzaWJsZSwgYXMgdGhl IGlkZWEgb2YgJ3Vuc3RhYmxlJyBhbmQgJ2ZhaWx1cmUnIGlzIHF1aXRlIGFtYmlndW91cyBhbmQg dXN1YWxseSBsZWFkcyB0byBjb25mdXNpb24uPC9wPgo8cCBkaXI9Imx0ciI+U28gd2UgZGVjaWRl ZCBub3QgdG8gaGF2ZSB0aGF0IHRoaXJkIHN0YXRlLCBydW5zIGVpdGhlciBwYXNzLCBvciBkbyBu b3QuPC9wPgo8cCBkaXI9Imx0ciI+WW91IGNhbiBwcmludC9hcmNoaXZlL2xvZyBhbnl0aGluZyB5 b3Ugd2FudCB0byBhbGxvdyB5b3UgaGVscCBkZWJ1Z2dpbmcgdGhlIGlzc3VlLCBidXQgb24gdGhl IGNpIHNpZGUsIHRoZSBkZWNpc2lvbiBpcyB0byAtMSBvciBub3QgYSBwYXRjaCwgc28ganVzdCB0 d28gc3RhdGVzLjwvcD4KPHAgZGlyPSJsdHIiPk91dCBvZiB0aGUgc3RhbmRhcmQgeW91IGNhbiBk ZWZpbmUgcG9zdC1idWlsZCBzY3JpcHRzIHRoYXQgY2FuIG1vZGlmeSB0aGUgc3RhdGUgb2YgdGhl IGpvYiAoeW91IGNhbiBzZXQgaXQgYXMgZmFpbGVkLCB1bnN0YWJsZSBvciBldmVuIHBhc3MgYSBq b2IgdGhhdCBvdGhlcndpc2Ugd291bGQgYmUgbWFya2VkIGFzIGZhaWxlZCkuPC9wPgo8cCBkaXI9 Imx0ciI+VGhvdWdoIGZvciB0aGUgcmVhc29ucyBJIGV4cG9zZWQsIEkgZG9uJ3QgcmVjb21tZW5k IHRoYXQuPC9wPgo8cCBkaXI9Imx0ciI+RGF2aWQgQ2FybzwvcD4KPGRpdiBjbGFzcz0icXVvdGUi PkVsIDI1LzQvMjAxNiA4OjMwIHAuIG0uLCBGYWJpYW4gRGV1dHNjaCAmbHQ7ZmRldXRzY2hAcmVk aGF0LmNvbSZndDsgZXNjcmliacOzOjxiciB0eXBlPSdhdHRyaWJ1dGlvbic+PGJsb2NrcXVvdGUg Y2xhc3M9InF1b3RlIiBzdHlsZT0ibWFyZ2luOjAgMCAwIC44ZXg7Ym9yZGVyLWxlZnQ6MXB4ICNj Y2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+PHAgZGlyPSJsdHIiPkhleSwmIzEzOzxicj4KJiMx Mzs8YnI+CmlzIHRoZXJlIGEgd2F5IGhvdyBhIHlhbWxpemVkIGpvYiBjYW4gYmVjb21lIHVuc3Rh YmxlPyYjMTM7PGJyPgomIzEzOzxicj4KSSdkIGxpZWsgdG8gcnVuIHNvbWUgc2FuaXR5IG5vZGUg dGVzdHMgYWZ0ZXIgYSBydW4sIGFuZCBtYXJrIGEgcnVuIGFzJiMxMzs8YnI+CnVuc3RhYmxlIGlm IHRoaXMgaGFwcGVucy4mIzEzOzxicj4KQWNjb3JkaW5nIHRvIHRoZSBqZW5raW5zIGRvY3MsIGEg am9iIGlzIHVuc3RhYmxlIGlmIG9uZSBvciBtb3JlIHB1Ymxpc2hlcnMgZmFpbC4mIzEzOzxicj4K JiMxMzs8YnI+CkNhbiB0aGlzIGJlIGFjaGlldmVkIHdpdGggeWFtbGl6ZWQgam9icz8mIzEzOzxi cj4KJiMxMzs8YnI+Ci0gZmFiaWFuJiMxMzs8YnI+Cl9fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fJiMxMzs8YnI+CkluZnJhIG1haWxpbmcgbGlzdCYjMTM7PGJy PgpJbmZyYUBvdmlydC5vcmcmIzEzOzxicj4KaHR0cDovL2xpc3RzLm92aXJ0Lm9yZy9tYWlsbWFu L2xpc3RpbmZvL2luZnJhJiMxMzs8YnI+CjwvcD4KPC9ibG9ja3F1b3RlPjwvZGl2Pg== ----_com.boxer.email_1064904379815452--
Okay, thanks for the clarification. - fabian On Mon, Apr 25, 2016 at 9:38 PM, David Caro Estevez <dcaroest@redhat.com> wrote:
With the standard ci is not possible, as the idea of 'unstable' and 'failure' is quite ambiguous and usually leads to confusion.
So we decided not to have that third state, runs either pass, or do not.
You can print/archive/log anything you want to allow you help debugging the issue, but on the ci side, the decision is to -1 or not a patch, so just two states.
Out of the standard you can define post-build scripts that can modify the state of the job (you can set it as failed, unstable or even pass a job that otherwise would be marked as failed).
Though for the reasons I exposed, I don't recommend that.
David Caro
El 25/4/2016 8:30 p. m., Fabian Deutsch <fdeutsch@redhat.com> escribió:
Hey,
is there a way how a yamlized job can become unstable?
I'd liek to run some sanity node tests after a run, and mark a run as unstable if this happens. According to the jenkins docs, a job is unstable if one or more publishers fail.
Can this be achieved with yamlized jobs?
- fabian _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Fabian Deutsch <fdeutsch@redhat.com> RHEV Hypervisor Red Hat
participants (2)
-
David Caro Estevez -
Fabian Deutsch