On 07/09/2013 05:08 PM, Eyal Edri wrote:
i assume you mean restarting a failing gerrit jenkins job and not the
master server right?
there is a special link to exactly that, no need to rebases...
just put in your change id or sha1, click search and trigger it.
or just hit the rebase button?
----- Original Message -----
> From: "Keith Robertson" <kroberts(a)redhat.com>
> To: engine-devel(a)ovirt.org
> Cc: "Spenser Shumaker" <sshumake(a)redhat.com>
> Sent: Tuesday, July 9, 2013 3:35:34 PM
> Subject: [Engine-devel] Recommended mechanism to restart Jenkins
> What is the recommended mechanism to restart the oVirt Jenkins CI server job
> when it fails due to an issue unrelated to a pushed patch? Should I...
> a) Add some newline/space to the commit message and re-push the patch (clunky
> but it shd work).
> b) Remove/add the 'oVirt Jenkins CI Server' reviewer from the Reviewer's
> and re-add? (have no idea if this actually works)
> c) Something else here...
> Keith Robertson
> Engine-devel mailing list
Engine-devel mailing list