| 1 |
On Wed, 28 Jan 2015 17:22:21 +0100 |
| 2 |
Alexey Lapitsky <lex.public@×××××.com> wrote: |
| 3 |
> Here's a naive example how it might work: |
| 4 |
> |
| 5 |
> 1. A user creates a PR |
| 6 |
> 2. travis-ci automatically runs QA tests: repoman full on the PR, |
| 7 |
> reports the result back |
| 8 |
> 3. Github hook is emitted, a "system" does some processing: for |
| 9 |
> example, create a bug in bugzilla, notify the maintainer, comment on |
| 10 |
> the PR |
| 11 |
> 4. The relevant maintainer checks the PR, comments: "looks fine, |
| 12 |
> merging" 5. Github hook is emitted to "the system", which checks the |
| 13 |
> PR comments, does some sanity checks, merges commit back to cvs, |
| 14 |
> rejects the PR |
| 15 |
> |
| 16 |
> "The system" might be a simple script which has opt-in membership for |
| 17 |
> the subsystems / maintainers who wants to use it. |
| 18 |
> |
| 19 |
> Does it sound sane? |
| 20 |
|
| 21 |
Exherbo has been doing something along those lines for ages, and not |
| 22 |
just for repoman: there's also full build testing (from a clean system, |
| 23 |
to check dependencies are correct). It's not very hard to do. |
| 24 |
|
| 25 |
-- |
| 26 |
Ciaran McCreesh |
Archives