We have it set up as a convenience for PRs, though in theory we could make
Jenkins do it instead. The ASF has a policy of using our own resources for
most things, so I don't think we can even use Travis as our primary CI
anyways.

As for the Scala module there, we're almost ready to migrate them into
their own repository, so we'll remove those from the core repository after
it's released.

On Thu, Apr 20, 2017 at 11:34, Chandra <[email protected]>
wrote:

> lol, I digged in a little bit, seems to be the issue of OOM.
>
>
> [INFO] Apache Log4j Scala 2.11 wrapper for Log4j API ...... FAILURE [
> 29.531 s]
> ...
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jar-plugin:3.0.0:jar (default-jar) on
> project log4j-api-scala_2.11: Error assembling JAR: Problem creating jar:
> Execution exception: Java heap space -> [Help 1]
>
> so, you guys aren’t using the travis for CI? oO
>
> thanks,
> Chandra
>
> On 20 Apr 2017, 11:59 PM +0530, Matt Sicker <[email protected]>, wrote:
> > That was a Travis build failure, right? That system is even less reliable
> > than our normal Jenkins system.
> >
> > On Wed, Apr 19, 2017 at 20:01, Chandra <
> [email protected]
> > wrote:
> >
> > > Yeah. I believe you. was just wondering why the all build failures. ;)
> > >
> > > thanks,
> > > Chandra
> > >
> > > On 20 Apr 2017, 5:33 AM +0530, Matt Sicker <[email protected]>, wrote:
> > > > Don't worry about the build failure. We can still merge it. :)
> > > >
> > > > On 19 April 2017 at 00:43, Chandra <
> [email protected]
> > > > wrote:
> > > >
> > > > > Hi List,
> > > > >
> > > > > I had a minor update on the documentation for which I sent a pull
> > > request.
> > > > > Not sure what happened but, the travis build failed.
> > > > > I see a lot of build failures from the PRs, any reason for that?
> > > > >
> > > > > Here’s my pull request.
> > > > >
> > > > > https://github.com/apache/logging-log4j2/pull/72
> > > > >
> > > > > thanks,
> > > > > Chandra
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Matt Sicker <[email protected]
> > >
> > --
> > Matt Sicker <[email protected]
>
-- 
Matt Sicker <[email protected]>

Reply via email to