www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra IRC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-8278) Update Log4j 2 Buildbot config for site generation
Date Fri, 02 Jan 2015 13:20:15 GMT

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

#asfinfra IRC Bot commented on INFRA-8278:
------------------------------------------

This issue is being automatically transitioned to 'Pending Closed' because it has been waiting
for user feedback for at least 3 days.  

The issue will be automatically closed in 7 days if not further action is taken.

To prevent the issue from being closed all you need to do is update the issue. 

> 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
>          Components: Buildbot
>            Reporter: Matt Sicker
>            Assignee: Gavin
>
> 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)

Mime
View raw message