You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/03/05 02:51:40 UTC

[jira] [Resolved] (INFRA-8278) Update Log4j 2 Buildbot config for site generation

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

Chris Lambertus resolved INFRA-8278.
------------------------------------
    Resolution: Fixed

The build config has been removed and will take effect once the next successful buildbot reconfig runs.

> Update Log4j 2 Buildbot config for site generation
> --------------------------------------------------
>
>                 Key: INFRA-8278
>                 URL: https://issues.apache.org/jira/browse/INFRA-8278
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Matt Sicker
>            Assignee: Chris Lambertus
>
> After running {{mvn site}}, the site needs to be run through {{mvn site:stage-deploy -DstagingSiteURL=file:///tmp/log4j2}} or somewhere similar. Then that can be copied over. Otherwise, our site is fragmented across the various submodules and don't get merged in the build process.
> See [this compile step|http://ci.apache.org/builders/log4j2-nightly/builds/100/steps/compile_1] for what I'm talking about. There's an upload task that comes after which I don't know what it's doing as there is no stdio log. It may be possible to just use {{-DstagingSiteURL=scp:///etc...}} in that process to really make things work more easily. Whichever method works best for you guys.



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