[
https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214412#comment-16214412
]
Robert Munteanu commented on SLING-7161:
----------------------------------------
{quote}Do we already have a technical user with read access to Apache or can we
request one from INFRA?{quote}
I asked at
https://lists.apache.org/thread.html/52199fba646b1c91edb79d2e022b0b4eecb7053807154d426a6a96c5@%3Cbuilds.apache.org%3E
, no reply yet.
Given that we need to issue lots of requests to the GitHub API and:
- it's slow
- it can become rate limited
- it becomes complicated to manage security credentials everywhere
I would suggest that we do the polling in a single place and write the output
to git. For instance have a Jenkins job that regenerates the project list in
XML or JSON format every 1 hour, and then every other 'client' can just use
that:
- Jenkins seed job
- repo manifest generation script
- website
I think it's faster, easier to manage and more secure. Also, at least for now,
we can regenerate the "master" repo list manually.
> Update site to reference git instead of svn
> -------------------------------------------
>
> Key: SLING-7161
> URL: https://issues.apache.org/jira/browse/SLING-7161
> Project: Sling
> Issue Type: Sub-task
> Components: Site
> Reporter: Robert Munteanu
>
> All the https://svn.apache.org/repos/asf/sling/... tags should be rewritten
> to the git repos.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
