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] [Resolved] (INFRA-11425) Simplify nightly builds
Date Mon, 14 Mar 2016 11:25:33 GMT

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

Sebb resolved INFRA-11425.
    Resolution: Fixed

> Simplify nightly builds
> -----------------------
>                 Key: INFRA-11425
>                 URL: https://issues.apache.org/jira/browse/INFRA-11425
>             Project: Infrastructure
>          Issue Type: Wish
>          Components: Buildbot
>            Reporter: Sebb
>            Assignee: Gavin
>            Priority: Trivial
> 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

View raw message