I have committed more changes to the LOG4J2-913 branch. These are primarily for
testing the performance of various appenders in delivering log events to a
forwarder / aggregator in a different docker container or somewhere else.
I have updated the staging area for the Log4j web site with the re
Well, something with dependencies that need updating would help... but
sure, go for it.
Gary
On Sun, Mar 31, 2019 at 9:06 PM Rob Tompkins wrote:
> Do you guys want to try this on something in commons first? We could try
> it on a lesser used component to see how it performs.
>
> -Rob
>
> > On M
Do you guys want to try this on something in commons first? We could try it on
a lesser used component to see how it performs.
-Rob
> On Mar 31, 2019, at 8:25 PM, Matt Sicker wrote:
>
> It files a PR which kicks off a CI build. I think you can configure it to
> automatically merge if the build
It files a PR which kicks off a CI build. I think you can configure it to
automatically merge if the build passes. Otherwise it’s jus another open PR.
On Sun, Mar 31, 2019 at 17:17, Gary Gregory wrote:
> Might be worth a try. I take it it only flies PRs if a build passes all
> tests?
>
> Gary
>
Might be worth a try. I take it it only flies PRs if a build passes all
tests?
Gary
On Mon, Mar 25, 2019, 14:23 Matt Sicker wrote:
> I wasn't thinking of automating this fully at any point. The bot does
> file PRs for each dependency individually. I'm not sure how
> configurable everything is,
