ferrit

mirror of https://github.com/gryf/ferrit.git synced 2026-02-07 16:55:47 +01:00

Go to file

gryf 9605cb22f0 Implement method /a/changes.

After gerrit recives an action (like creating a review, comment, and so
on) it will send appropriate json from ssh server. Jenkins, which is
listening on the ssh channel will receive this message and do
appropriate action (for example, it will do the build/test whatever),
and sends back notification back to HTTP gerrit server to /a/changes
endpoint. There are couple of requests to that url, which will indicate
what jenkins is doing (like starting build, sending result info).

2019-11-01 08:17:14 +01:00

img

Initial import

2019-10-24 14:01:49 +02:00

.gitignore

Tiny cleanup

2019-10-29 19:26:47 +01:00

gerrit_fake_http_server.py

Implement method /a/changes.

2019-11-01 08:17:14 +01:00

gerrit_fake_ssh_server.py

Use FIFO named queue for triggering actions on Jenkins side.

2019-11-01 08:17:13 +01:00

README.rst

Readme update

2019-11-01 08:17:14 +01:00

README.rst

Ferrit is a fake Gerrit server implementation created for functional testing of events in Jenkins & Gerrit Trigger ecosystem.

Architecture

Ferrit consists of two servers, http and ssh and companion script for generating payload for the ssh server.

We relay on real Jenkins installation, so it has to be configured up front. See next section for details.

Having Jenkins up and running, we can simultaneously run ssh and http servers by invoking:

$ python3 gerrit_fake_http_server.py

and

$ python3 gerrit_fake_ssh_server.py

Output of the last command will provide fifo file name used for triggering events in json format which can be generated using third part of the Ferrit - script generate_event.py.

Installation

Prerequisites

Python

Ferrit modules are written in Python and depends on two external libraries:

paramiko for ssh server
bottle for http server

Please note, Python 2.x is not supported.

Ferrite image by Karl-Martin Skontorp is on Attribution 2.0 Generic (CC BY 2.0) license.