[
https://issues.apache.org/jira/browse/SLING-7262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16264327#comment-16264327
]
Bertrand Delacretaz commented on SLING-7262:
--------------------------------------------
You're welcome! I have now also added a {{OncePerBuild}} mechanism that we
might use to create that modules json file, I think it's cleaner than having an
additional Maven setup?
The code that talks to Git should not run if the json file already exists, to
avoid slowing down interactive staging.
See commit https://github.com/apache/sling-site/commit/03c78d0
I'm not planning to implement the Git -> json code now but that should make it
easy for you to adapt what you have in your prototype.
> 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
>
> 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
(v6.4.14#64029)
