I would suggest that if we want a build job for Windows that we do it in Jenkins. We seem to have very little control over buildbot and watching failed builds go by for the last year without the ability to do anything has completely persuaded me to stay away from it.
Ralph > On Mar 2, 2016, at 9:50 PM, Chris Lambertus (JIRA) <[email protected]> wrote: > > > [ > https://issues.apache.org/jira/browse/INFRA-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Chris Lambertus updated INFRA-8279: > ----------------------------------- > Status: Waiting for user (was: Waiting for Infra) > > Are you asking for log4j2 installed on the windows build slaves, or are you > asking for windows build jobs? This is a 2 year old issue, so this may all be > moot. Please let us know one way or the other. > >> Add Log4j2 to Windows Buildbot >> ------------------------------ >> >> Key: INFRA-8279 >> URL: https://issues.apache.org/jira/browse/INFRA-8279 >> Project: Infrastructure >> Issue Type: New Feature >> Security Level: public(Regular issues) >> Reporter: Matt Sicker >> >> We've had numerous issues in the past regarding Windows-specific issues that >> weren't noticed for some time or are hard to reproduce outside a Windows >> environment. To help our code quality, we'd like to have an additional >> buildbot configuration that runs on one of the Windows buildslaves. >> Environmentally, we'd still need the same things as on the Linux buildslave: >> Maven 3.0.x, Java 1.6, and Git. >> If this would be more appropriate on a different build system (e.g., >> Jenkins), please let us know so we can do it there instead. Thanks! > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
