infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (INFRA-17987) Site Distribution for Plugins/Components moving to Git?
Date Sun, 17 Mar 2019 08:35:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794214#comment-16794214
] 

Hervé Boutemy edited comment on INFRA-17987 at 3/17/19 8:34 AM:
----------------------------------------------------------------

[~khmarbaise] can you define, please, "via SVN takes very long."?
I'm interested in multiple durations, per step:
1. svn checkout to your local machine,
2. svn checkin from your local machine
2. eventually svnpubsub update to live site, if this is an issue for you

> The first thought (naive) was to migrate the whole maven.apache.org site into a single
git repository but based on the history and several areas this will become quite large.
> An other thought might be to make separate git repos for different areas ...but the question
is how could that be configured on the Apache Web Site are?
I see that you understand our prerequisites that make any change not so easy :)

> The real issue is that the Maven project has ca. 100 Plugins/Components with it's sites.
yes, 1 plugin/component has many site instances: current, LATEST, and every version that we
choose not to delete
see for example http://maven.apache.org/components/plugins-archives/

> Furthermore I could think of generating the site on an Apache Build Server (with some
parameters for example a git tag? Need to think about more in detail). This would safe a lot
of time locally cause the transfer takes very long time locally...(svn commit a larger number
of small files)...
here, it seems you have network performance issue from your local machine to svn server
if we try to get real measure for one component, let's try with resolver since its size is
bigger than usual: from my machine (which is like you in Europe: I'm in Paris),

$ time svn co https://svn.apache.org/repos/asf/maven/website/components/resolver-archives/resolver-LATEST/
[... 9141 files in 1274 directories for 160,804 kB]
real    0m26,448s

26 seconds for only download, I suppose check-in takes a 3 or 4 times more: but given the
number of files and the size, that's to be expected

can you try do to the same and share results, please?


was (Author: hboutemy):
[~khmarbaise] can you define, please, "via SVN takes very long."?
I'm interested in multiple durations, per which step: svn checkout to your local machine,
svn checkin from your local machine and/or svnpubsub update to live site

> The first thought (naive) was to migrate the whole maven.apache.org site into a single
git repository but based on the history and several areas this will become quite large.
> An other thought might be to make separate git repos for different areas ...but the question
is how could that be configured on the Apache Web Site are?
I see that you understand our prerequisites that make any change not so easy :)

> The real issue is that the Maven project has ca. 100 Plugins/Components with it's sites.
yes, and having LATEST location for staging means that 1 plugin/component has many site instance
(current, LATEST, and every version that we choose not to delete: see for example http://maven.apache.org/components/plugins-archives/)

> Furthermore I could think of generating the site on an Apache Build Server (with some
parameters for example a git tag? Need to think about more in detail). This would safe a lot
of time locally cause the transfer takes very long time locally...(svn commit a larger number
of small files)...
here, it seems you have network performance issue from your local machine to svn server
if we try to get real measure for one component, let's try with resolver since its size is
bigger than usual: from my machine (which is like you in Europe: I'm in Paris),
$ time svn co https://svn.apache.org/repos/asf/maven/website/components/resolver-archives/resolver-LATEST/
[... 9141 files in 1274 directories for 160,804 kB]
real    0m26,448s

26 seconds for only download, I suppose check-in takes a 3 or 4 times more: but given the
number of files and the size, that's to be expected

> Site Distribution for Plugins/Components moving to Git?
> -------------------------------------------------------
>
>                 Key: INFRA-17987
>                 URL: https://issues.apache.org/jira/browse/INFRA-17987
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: GitBox, maven, Website
>            Reporter: Karl Heinz Marbaise
>            Priority: Minor
>
> Currently we deploy the sites for Plugins/shared component releases etc.  via Subversion
under this url https://svn.apache.org/repos/asf/maven/website/components/ which tooks often
very long.
> The question is: 
> Had there be ideas/requests of other projects to do that in different ways? 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message