From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: lex.public@gmail.com
Subject: Re: [gentoo-project] Official rsync->git mirror & 'Git mirror' project announcement
Date: Wed, 28 Jan 2015 13:45:21 -0500 [thread overview]
Message-ID: <CAGfcS_mD6WUz0YirS-7Toe1vDA+3TBgSpqqZO0HE4bSOKXkYhQ@mail.gmail.com> (raw)
In-Reply-To: <20150128175619.714227bf@googlemail.com>
On Wed, Jan 28, 2015 at 12:56 PM, Ciaran McCreesh
<ciaran.mccreesh@googlemail.com> wrote:
> On Wed, 28 Jan 2015 17:22:21 +0100
> Alexey Lapitsky <lex.public@gmail.com> wrote:
>> Here's a naive example how it might work:
>>
>> 1. A user creates a PR
>> 2. travis-ci automatically runs QA tests: repoman full on the PR,
>> reports the result back
>> 3. Github hook is emitted, a "system" does some processing: for
>> example, create a bug in bugzilla, notify the maintainer, comment on
>> the PR
>> 4. The relevant maintainer checks the PR, comments: "looks fine,
>> merging" 5. Github hook is emitted to "the system", which checks the
>> PR comments, does some sanity checks, merges commit back to cvs,
>> rejects the PR
>>
>> "The system" might be a simple script which has opt-in membership for
>> the subsystems / maintainers who wants to use it.
>>
>> Does it sound sane?
>
> Exherbo has been doing something along those lines for ages, and not
> just for repoman: there's also full build testing (from a clean system,
> to check dependencies are correct). It's not very hard to do.
>
Including having two repositories both being committed to, with a
delayed propagation of commits from each to the other? Somehow I
doubt that is what you're doing with exherbo.
The CI isn't the part I'm picking on here. The idea of still working
in cvs while having a separate CI and commit path in git that applies
back to cvs is the part that sounds rather prone to breakage. That
seems like a massive hack. The real solution is to get the heck off
of cvs.
--
Rich
next prev parent reply other threads:[~2015-01-28 18:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 20:12 [gentoo-project] Official rsync->git mirror & 'Git mirror' project announcement Michał Górny
2015-01-26 20:23 ` Seemant Kulleen
2015-01-27 15:19 ` Ben de Groot
2015-01-28 15:51 ` Alexey Lapitsky
2015-01-28 15:58 ` Rich Freeman
2015-01-28 16:22 ` Alexey Lapitsky
2015-01-28 17:56 ` Ciaran McCreesh
2015-01-28 18:45 ` Rich Freeman [this message]
2015-02-15 5:59 ` [gentoo-project] " NP-Hardass
2015-02-15 7:29 ` Michał Górny
2015-01-28 21:48 ` [gentoo-project] " Markos Chandras
2015-01-28 22:30 ` Michał Górny
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=CAGfcS_mD6WUz0YirS-7Toe1vDA+3TBgSpqqZO0HE4bSOKXkYhQ@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=lex.public@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox