Gerrit CI bot should support picking up a comment with the word recheck to retest the change

[thomasmu...@yahoo.com]

Hi, the gerrit bot should support a recheck command that will retest the change. With this it will allow us to recheck changes without needing a new change.

[thomasmu...@yahoo.com]

[Logan Hanks]

Consider also triggering off deletion of its Verified vote.

On Thu, Mar 30, 2017, 08:25 thomasmulhall410 via Repo and Gerrit Discussion <repo-d...@googlegroups.com> wrote:

On Thursday, March 30, 2017 at 4:25:26 PM UTC+1, thomasmu...@yahoo.com wrote:

Hi, the gerrit bot should support a recheck command that will retest the change. With this it will allow us to recheck changes without needing a new change.

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Luca Milanesio]

Yes, this is a good idea when scheduling an ad-hoc build.

It should:

a) Reset existing vote

b) Re-run the build

c) Assign the new vote

Luca.

[thomasmu...@yahoo.com]

+1

[Luca Milanesio]

Here is the link to the "Change builder job":

https://gerrit-ci.gerritforge.com/job/Gerrit-verifier-change/build?delay=0sec

You would need to login using your GitHub credentials and then request permissions on the mailing list.

In the past the build button was enabled for everyone ... but there was a bit of abuse (bots?) and the CI was the overloaded.

I am open to suggestions on how to make it more accessible :-)

Ideally we would like to have  a button on the change screen that says "Build on CI" ... but I am aware that gerrit-review.googlesource.com doesn't support plugins.

Luca.

[Shawn Pearce]

On Thu, Mar 30, 2017 at 3:12 PM, Luca Milanesio <luca.mi...@gmail.com> wrote:

Here is the link to the "Change builder job":

https://gerrit-ci.gerritforge.com/job/Gerrit-verifier-change/build?delay=0sec

You would need to login using your GitHub credentials and then request permissions on the mailing list.

In the past the build button was enabled for everyone ... but there was a bit of abuse (bots?) and the CI was the overloaded.

I am open to suggestions on how to make it more accessible :-)

Ideally we would like to have  a button on the change screen that says "Build on CI" ... but I am aware that gerrit-review.googlesource.com doesn't support plugins.

Well... not entirely true. We run a number of open source plugins in our build. We might be willing to run a plugin that does this, but yes its more work to get installed than on most Gerrit servers.

[Luca Milanesio]

Oh, that's great news then :-)

Let me work on that in the next few days then.

In theory, should be a UX-only plugin that triggers a remote REST API.

Jenkins allows to generate a OAuth token to be used for this purpose. Having a "service user" with that token would be good enough to protect the REST API from abuse.

Luca.