www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-8625) projects.apache.org not being updated since move to svnpubsub
Date Fri, 21 Nov 2014 18:52:33 GMT

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

Sebb commented on INFRA-8625:
-----------------------------

The projects website is now nearly 3 weeks old (the contents were committed on Nov 4th).

Is there any ETA for fixing this?

> projects.apache.org not being updated since move to svnpubsub
> -------------------------------------------------------------
>
>                 Key: INFRA-8625
>                 URL: https://issues.apache.org/jira/browse/INFRA-8625
>             Project: Infrastructure
>          Issue Type: Bug
>            Reporter: Sebb
>            Assignee: Geoffrey Corey
>
> The projects.apache.org site is still being generated OK, but is not being published
since the move to svnpubsub.
> In the past, publication was achieved by using rsync to push the contents of projects/html
to /www/projects.apache.org/ on minotaur.
> However, projects.apache.org now uses svnpubsub so the rsync has no effect.
> Note that the people.apache.org site is updated by the same cron job, using rsync, and
that still works. I think this is partly because people.a.o uses the same host as minotaur.
> Possible solutions are:
> 1) revert to using rsync for projects.apache.org.
> or
> 2) provide a way for the cron job to update the files in svnpubsub
> 1) would presumably require moving projects.a.o to minotaur and abandoning the use of
svnpubsub for it.
> 2) would require caching the SVN credentials somewhere.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message