All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Sage Weil <sage@newdream.net>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Call for jenkins slaves to improve multi operating system support
Date: Wed, 08 Apr 2015 19:31:04 +0200	[thread overview]
Message-ID: <552565D8.1000006@dachary.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1504080957210.4469@cobra.newdream.net>

[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]

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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-04-08 17:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 10:56 Call for jenkins slaves to improve multi operating system support Loic Dachary
2015-04-08 13:21 ` Duan, Jiangang
2015-04-08 13:32   ` Loic Dachary
2015-04-09 10:30     ` Duan, Jiangang
2015-04-09 12:55       ` Loic Dachary
2015-04-08 16:59 ` Sage Weil
2015-04-08 17:31   ` Loic Dachary [this message]
2015-04-18 21:13 ` Loic Dachary

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=552565D8.1000006@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.