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