| 1 |
Alexey Lapitsky <lex.public <at> gmail.com> writes: |
| 2 |
|
| 3 |
> |
| 4 |
> Hi, |
| 5 |
> |
| 6 |
> Looks awesome, great initiative! |
| 7 |
> |
| 8 |
> I'm wondering if it makes sense to integrate travis-ci to run QA tests |
| 9 |
> automatically? |
| 10 |
> |
| 11 |
> > Since the changes will be re-committed in CVS manually, we will end up |
| 12 |
updating the commit message anyway. |
| 13 |
> |
| 14 |
> It should be possible to automate this step as well. Is there a reason |
| 15 |
> why not to do that? |
| 16 |
> |
| 17 |
> -- |
| 18 |
> |
| 19 |
> Alexey |
| 20 |
|
| 21 |
Looks like they opted to roll their own system to use travis with repoman. |
| 22 |
(https://github.com/gentoo/gentoo-portage-rsync- |
| 23 |
mirror/blob/master/.travis.yml) |
| 24 |
Just a FYI, there is also repoman-travis (https://github.com/mrueg/repoman- |
| 25 |
travis) from mrueg, though it doesn't make sense to use repoman-travis in |
| 26 |
this situation, since repoman-travis assumes that you don't have the gentoo |
| 27 |
tree set up, and imports a copy of it, prior to running repoman. I use |
| 28 |
repoman-travis in all of my overlays. |
Archives