NFD

I will not say it is not possible to set up travis to do this work, but I'm kind of pessimistic about the benefits vs. time spent on figuring out how everything can work.

From what I gathered during brief experiments, it would be way easier to set up our own Jenkins server and create a job that would dispatch upon notification from gerrit and post reviews. In the simple scenario (and I would go for now with it), we need to set up environments (=servers/machines/or vms) in which code will be compiled (linux, freebsd, osx)---what I mean is that we just install all necessary dependencies once and compile code multiple times. When everything works, we can think how to check dependencies (do we really need to check them every time?).

This task focuses on the feasibility of Gerrit-Travis CI setup.
If assignee thinks it's infeasible (incl taking too much work), the response should be "infeasible" and this task is completed.

I will write another task about setting up Gerrit-Jenkins.

I've done writing python script to create two branches and tested that travis can pick up two pull-requets (for ubuntu and osx). Also, a second script that discard the two pull requests and delete the branches is almost done. I think the only thing I'm not sure is that how to hook and pull patch-set from Gerrit and how to get those two scripts triggered.

Yi Huang wrote:

I think the only thing I'm not sure is that how to hook and pull patch-set from Gerrit and how to get those two scripts triggered.

Gerrit-to-GitHub script can be triggered with patchset-created hook.

Pulling patch-set from Gerrit is simply a git pull command, once you know the numeric change id.

I'm not sure how Travis CI notifies about a successful or failed build.
If it has a web hook, you can trigger the script via CGI.
If it sends an email, you can configure postfix mail server to trigger the script.

I'm not sure how Travis CI notifies about a successful or failed build.
If it has a web hook, you can trigger the script via CGI.
If it sends an email, you can configure postfix mail server to trigger the script.

There are a number of different ways Travis CI allow notificateions (http://docs.travis-ci.com/user/notifications/). The simplest and fastest way seem to be Webhook notification (with proper authorization of course).

Junxiao Shi wrote:

Yi Huang wrote:
Gerrit-to-GitHub script can be triggered with patchset-created hook.

Pulling patch-set from Gerrit is simply a git pull command, once you know the numeric change id.

I read the doc page and I just want to make sure I understand how patchset-created hook works.
Does that mean my script should be called patchset-created and should be placed in the hook directory. Gerrit will call it with the command "patchset-created --change --is-draft --change-url --project --branch --topic --uploader --commit --patchset " when a patchset is created?

And what is the clone url for our gerrit server? I think I can't use "git pull-request" on this clone url since it is not GitHub. Is that correct?

Also I think it will be better for me to have access to our gerrit server to explore more about it.

Gerrit looks in '$site_path'/hooks for executables with names listed below.

This needs SSH access to the Gerrit server machine.
I suggest you try the setup on a virtual machine with a separate instance of Gerrit.
gerrit.named-data.net is a production environment, you shouldn’t experiment on it. Once you know the method and write down the steps, we could deploy it there.

I remember that in the slides, author mentions that interested users could contact him to obtain some information.
If the assignee of this task hasn't done so, he should contact the author.

Yi. I think we are wasting time trying to make travis-ci do something that is too complicated. I would suggest you to create a simple .travis.yml and submit it to gerrit, so we can actually start using it (at least with linux).

After that, please move to the new issue #1164 to set up jenkinks, create jenkins job, and figure out which plugins we need to use to connect it to gerrit.