infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17987) Site Distribution for Plugins/Components moving to Git?
Date Fri, 15 Mar 2019 21:25:00 GMT

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

Karl Heinz Marbaise commented on INFRA-17987:
---------------------------------------------

Sorry wasn't clear enough.

The idea is to deploy the web site of the plugin (for example https://maven.apache.org/resolver/)
not via Subversion which took very long maybe via Git ? 

Currently during the publishing of the Web Site we checkout https://svn.apache.org/repos/asf/maven/website/components/resolver-archives/resolver-LATEST
change the content and commit that back to Subversion which is published https://maven.apache.org/resolver-archives/
this can be shown via https://maven.apache.org/resolver-archives/resolver-LATEST/ and later
this can be move/copied via Subversion to the live site. Described in detail https://maven.apache.org/developers/website/deploy-component-reference-documentation.html#Publishing_versioned_component_reference_documentation

The problem at the moment is that the updating of the content / committing via SVN takes very
long..

The issue at the moment by using gitpubsub is that a single git repository represents a web
site...and If I correctly understand that (We are using the for the https://maven.apache.org/)
we don't have a staging site which we will simulate by using the above setup with /resolver-archives/...
cause we need the separation of staged sites (used during the VOTE) and the life sites and
the archiving feature to have older states available...

Currently we are using the https://builds.apache.org/job/maven-box/job/maven-site/job/master/8/console
which generates the site for maven.apache.org but does the same and commits to Subversion....

The question is: Is there something we can think of to make that easier/faster ? 

I thought about some possible ideas for solutions. 

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?
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)...

> 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