[jira] [Updated] (INFRA-11425) Simplify nightly builds

["Gavin (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/INFRA-11425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin updated INFRA-11425:
--------------------------
    Status: Waiting for user  (was: Waiting for Infra)

Feel free to go for it for your projects.

Subversion and Ofbiz for instance wanted the continued look from their websites. And from then on I just did every other one as well.

If you just want a dir listing with readme and header files thats fine, ensuring you keep the information regarding snapshots and that they are developer only etc etc...

> Simplify nightly builds
> -----------------------
>
>                 Key: INFRA-11425
>                 URL: https://issues.apache.org/jira/browse/INFRA-11425
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Buildbot
>            Reporter: Sebb
>
> The generation of the nightly build sites currently requires two stages:
> 1) creation of the archives (nightly build)
> 2) creation of the index page (site)
> These have to be co-ordinated, but are currently in two different repos using different SCMs. This is far from ideal.
> Is there any reason why the index page should not be created as another stage in the nightly build job?
> That should make it easier to synchronise any changes.
> Further, the site only need to be built if the build job succeeds.
> However I wonder whether there really needs to be a customised index page at all?
> I would have thought that the index generated by the HTTP server together with HEADER.html/README.html static pages would be sufficient.
> The index cron jobs could then be dropped.



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