[jira] [Commented] (SLING-7161) Update site to reference git instead of svn
[ https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16264012#comment-16264012 ] Robert Munteanu commented on SLING-7161: [~kwin] - I think that's a good idea. I created SLING-7262 to track the creation of the JSON/XML file. > 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 >Assignee: 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)
[jira] [Commented] (SLING-7161) Update site to reference git instead of svn
[ https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16263993#comment-16263993 ] Konrad Windszus commented on SLING-7161: IMHO we should still provide a table with URLs to all Sling repositories (both Github and Gitbox). My branch at https://github.com/apache/sling-site/tree/scm-project-url-list provides such a thing. What about the plan of having a single job retrieving all repos and writing the information to JSON/XML? [~rombert] Can you quickly comment on that? > 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 >Assignee: 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)
[jira] [Commented] (SLING-7161) Update site to reference git instead of svn
[ https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16255096#comment-16255096 ] Bertrand Delacretaz commented on SLING-7161: > ...inconsistent spacing in Groovy templates (sometimes tabs, sometimes > spaces)... Totally my fault, I used a mix of editors when working on those, including some badly configured ones :-\ I suggest that we fix files when we need to touch them, ideally with separate formatting-only commits. > 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 >Assignee: 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)
[jira] [Commented] (SLING-7161) Update site to reference git instead of svn
[
https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (SLING-7161) Update site to reference git instead of svn
[
https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214366#comment-16214366
]
Konrad Windszus commented on SLING-7161:
I created a new branch for listing all Git repo urls with a dedicated JBake
template leveraging the Github API at
https://github.com/apache/sling-site/tree/scm-project-url-list in the site.
There are still some issues with that branch namely:
# a lot of code duplication between {{page.tpl}} and {{scm-projects.tpl}}. IMHO
a lot more should be moved into {{layout/main.tpl}}, like the breadcrumb.
# inconsistent spacing in Groovy template (sometimes tabs, sometimes spaces).
Can we agree on what should be used here?
# Github API has some rate limitation in place. Since just iterating over all
Apache repos requires a lot of requests (due to pagination) this hits us with
the second run of JBake. We should try out what limits there are with an OAuth
authentication. Do we already have a technical user with read access to Apache
or can we request one from INFRA?
> 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)
[jira] [Commented] (SLING-7161) Update site to reference git instead of svn
[ https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212324#comment-16212324 ] Bertrand Delacretaz commented on SLING-7161: Note that http://sling.apache.org/project-information.html should already mention our Git repositories, but for some reason the website is out of sync with the content published on its asf-site branch, INFRA-15330 > 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)
[jira] [Commented] (SLING-7161) Update site to reference git instead of svn
[ https://issues.apache.org/jira/browse/SLING-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16211158#comment-16211158 ] Konrad Windszus commented on SLING-7161: In addition it would be good to create a new page below http://sling.apache.org/project-information.html listing all Git Repository URLs (both Gitbox and Github). I think a dedicated JBake template should be used for that leveraging https://api.github.com/orgs/apache/repos to retrieve all sling repositories with each build automatically. > 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)
