[
https://issues.apache.org/jira/browse/SLING-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341323#comment-16341323
]
Konrad Windszus edited comment on SLING-7262 at 1/26/18 5:33 PM:
-----------------------------------------------------------------
There is already the file {{default.xml}} within
https://github.com/apache/sling-aggregator which could be used instead as
starting point.
was (Author: kwin):
There is already the file {{.sling-module.xml}} within
https://github.com/apache/sling-aggregator which could be used instead as
starting point.
> Generate reusable list of repositories for machine consumption
> --------------------------------------------------------------
>
> Key: SLING-7262
> URL: https://issues.apache.org/jira/browse/SLING-7262
> Project: Sling
> Issue Type: Task
> Components: Build and Source Control
> Reporter: Robert Munteanu
> Priority: Major
>
> We currently have two 'clients' that query the github repos and the
> .sling-module.xml descriptors:
> * the jenkins job creation DSL script
> * the repo manifest creation script
> We've also discussed in SLING-7161 the possibility of listing all
> repositories on the website.
> To minimize the effort of talking to github in each location and reduce the
> number of calls to Github ( for rate limiting purposes ) we should generate a
> JSON/XML file that contains all information about the git repos. This file is
> in turns read by various "clients" that need the information.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
