sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bertrand Delacretaz <bdelacre...@apache.org>
Subject Re: apache/sling as github landing repository
Date Wed, 31 Jan 2018 09:00:04 GMT
Hi,

On Wed, Jan 31, 2018 at 9:23 AM, Robert Munteanu <rombert@apache.org> wrote:
> On Wed, 2018-01-31 at 00:13 +0000, Alexander Klimetschek wrote:
>>... 4. add the aggregator and new landing page readme on the master
>> branch, which will be push-able for committers...
>>
> ...The only downside would be that
> cloning the repository would be really slow due to the large size....

I think we need to have the aggregator [0] run a regular build to
update the list of Git repositories, soon. That becomes more important
as that list starts including tags, contrib/core/etc status and other
metadata that will change more often than now.

I don't think a large Git repository is a good place for such an
automatically built list of Git repositories metadata, as Jenkins
would need to transfer lots of unneeded data, a dedicated small
repository is much better for that. And I'm not sure right now how to
push the output of that to any branch from builds.apache.org, at this
point I only know how to commit to an asf-site branch (by tying the
Jenkins build to build nodes having the git-websites label).

-Bertrand

> [0] https://github.com/apache/sling-aggregator - which needs a Maven build to be automated

Mime
View raw message