| 1 |
On Thu, 16 Jun 2016 08:59:44 -0500 |
| 2 |
james <garftd@×××××××.net> wrote: |
| 3 |
|
| 4 |
> On 06/16/2016 02:51 AM, Alexander Berntsen wrote: |
| 5 |
> > -----BEGIN PGP SIGNED MESSAGE----- |
| 6 |
> > Hash: SHA512 |
| 7 |
> > |
| 8 |
> > On 16/06/16 09:39, Daniel Campbell wrote: |
| 9 |
> >> I guess what I mean is these outside developers could continue |
| 10 |
> >> hacking and/or breaking things, or whatever else, without worrying |
| 11 |
> >> about their "official" branch. We could have a standard that |
| 12 |
> >> assumes Gentoo pulls their 'master' branch and they keep other |
| 13 |
> >> stuff in 'dev', or some other model. We'll need to decide on *some* |
| 14 |
> >> branch, but putting it in writing would make things clearer for |
| 15 |
> >> prospective repo maintainers. |
| 16 |
> |
| 17 |
> > OK, then I think that it would be a good idea to have a gentoo-ci |
| 18 |
> > branch, or similar, if the assumption is merely that this is where |
| 19 |
> > Gentoo developers will look when evaluating your repository. |
| 20 |
> > |
| 21 |
> Ok, if we go this route, here is a basic simple question. Why can't the |
| 22 |
> "gentoo-ci" be a package, or group of packages that runs in a private |
| 23 |
> persons own resources, regardless it is a single gentoo server or a |
| 24 |
> small cluster (openstack)? That way, those gentoo-ciruns can be |
| 25 |
> performed by the proxy or the author thus reducing the workload for QA |
| 26 |
> or other devs. I guess what I'm really asking is/will the gentoo-ci be |
| 27 |
> packaged up for the gentoo community to use, on a small set of packages? |
| 28 |
|
| 29 |
dev-util/pkgcheck is the QA tool used (you want -9999). |
| 30 |
|
| 31 |
https://github.com/gentoo/travis-repo-checks is the wrapper that is |
| 32 |
used to run it in parallel. A lot of hackery, and master is outdated |
| 33 |
for -9999. No time to fix it. The repo-mirror-ci branch is better but |
| 34 |
then, I updated it recently for some local hacks. |
| 35 |
|
| 36 |
https://bitbucket.org/mgorny/pkgcheck-result-parser is the thingie used |
| 37 |
to turn pkgcheck XML reports into pretty HTML. Also a bit hacky, |
| 38 |
especially with the error & warning lists hardcoded. |
| 39 |
|
| 40 |
https://bitbucket.org/mgorny/repo-mirror-ci all the extra scriptery |
| 41 |
used to run it all. No time to clean it up more than I already did. |
| 42 |
|
| 43 |
-- |
| 44 |
Best regards, |
| 45 |
Michał Górny |
| 46 |
<http://dev.gentoo.org/~mgorny/> |
Archives