All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: John Spray <jspray@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: RFC: teuthology field in commit messages
Date: Sun, 29 Nov 2015 21:25:48 +0100	[thread overview]
Message-ID: <565B5F4C.30308@dachary.org> (raw)
In-Reply-To: <CALe9h7edX3zQVri_KRRNRmjOnvcxhxq0EJXn=5nhF+AQY51g3g@mail.gmail.com>

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



On 29/11/2015 21:08, John Spray wrote:
> On Sat, Nov 28, 2015 at 3:56 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Ceph,
>>
>> An optional teuthology field could be added to a commit message like so:
>>
>> teuthology: --suite rbd
>>
>> to state that this commit should be tested with the rbd suite. It could be parsed by bots and humans.
>>
>> It would make it easy and cost effective to run partial teuthology suites automatically on pull requests.
>>
>> What do you think ?
> 
> Hmm, we are usually testing things at the branch/PR level rather than
> on the per-commit level, so it feels a bit strange to have this in the
> commit message.

Indeed. But what is a branch if not the HEAD commit ?

> However, if a system existed that would auto-test things when I put
> something magic in a commit message, I would probably use it!
> 
> John
> 
> 
>>
>> --
>> Loïc Dachary, Artisan Logiciel Libre
>>

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-11-29 20:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-28 15:56 RFC: teuthology field in commit messages Loic Dachary
2015-11-29 11:51 ` Joao Eduardo Luis
2015-11-29 14:58   ` Loic Dachary
2015-11-29 20:08 ` John Spray
2015-11-29 20:25   ` Loic Dachary [this message]
2015-11-29 20:47     ` John Spray
2015-11-29 21:25       ` Loic Dachary
2015-11-29 22:55         ` John Spray
2015-11-29 23:15           ` Loic Dachary
2015-11-30 15:15             ` Gregory Farnum

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=565B5F4C.30308@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=jspray@redhat.com \
    /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.