Hi Sage, On 08/04/2015 18:59, Sage Weil wrote: > On Wed, 8 Apr 2015, Loic Dachary wrote: >> Hi Ceph, >> >> When a contribution is proposed to Ceph [1], a bot compiles and run >> tests with it to provide feedback to the developer [2]. When something >> goes wrong the failure can be repeated on the developer machine [3] for >> debug. This also helps the reviewer who knows the code compiles and does >> not break anything that would be detected by "make check". >> >> The bot runs on CentOS 7 and Ubuntu 14.04 only, and problems related to >> older operating systems (headers, compiler version, etc.) may be >> detected later, when building packages [4] and after the pull request >> has been merged in master. This is rare but requires extra attention >> from the reviewer and needs to be dealt with urgently when it happens. > > Do additional slaves block the message from appearing on the pull > request? I.e., what happens if a slave is very slow (e.g., armv7) or > broken (network issue)? I will make it so a comment is posted as soon as the first slave succeeds / fails (it currently waits for all to finish which is inconvenient). The first slave will always be a CentOS 7 running on a fast machine so that the worst that can happen is that it's the only one to run. If slow slaves lag behind too much it would be nice to have a jenkins plugin that discards jobs randomly to prevent the queue from growing out of proportion on that specific slave. > What are the connectivity requirements? Nothing more than the ability to git pull from a ceph repository. > Can slaves exist on other > (private) networks? Yes. In that case a ssh -f -n -L tunnel to the jenkins master will be established to allow it to probe the slave when necessary. > > Thanks! > sage > Cheers -- Loïc Dachary, Artisan Logiciel Libre
Attachment:
signature.asc
Description: OpenPGP digital signature
