I don’t know. I have never really looked at how Jenkins does the deploy.
> On Apr 10, 2018, at 7:16 PM, Matt Sicker <boa...@gmail.com> wrote:
> Is it possible to exclude that from the deploy task? The scala api build
> only publishes the api jars, not the samples, for example.
> On 10 April 2018 at 17:12, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>> Note that the Jenkins deployment uploads stuff that we don’t release.
>>> On Apr 10, 2018, at 9:57 AM, Matt Sicker <boa...@gmail.com> wrote:
>>> I've added a new pipeline for Log4j <
>>> https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we are
>>> doing in log4net, chainsaw, log4j scala api, log4j kotlin api, and
>>> parent. Thanks to Dominik for demonstrating that this was possible and
>>> how to run things on Windows.
>>> This pipeline is configured to run the build in parallel on three
>>> * Ubuntu with Oracle JDK 8 and 9
>>> * Ubuntu with IBM JDK 8 and Oracle JDK 9 (waiting to see if infra adds
>>> OpenJ9 or at least a JDK9 version of the IBM JDK as an option to make
>>> pipeline fully IBM)
>>> * Windows with Oracle JDK 8 and 9
>>> This is configured to fail fast if any one of those three builds fail.
>>> Afterwards, it archives test results and uploads snapshots to
>>> repository.a.o. Now I haven't seen all three builds pass together yet
>>> (there appears to be an issue with the embedded mongo tests that I don't
>>> know how to reproduce locally), but it's almost there! I'm considering
>>> ignoring those tests on jenkins for now to make sure everything else
>>> Once this pipeline is stabilized, we can remove the old windows jenkins
>>> project as well as the old log4j 2 3.x project. We can leave the
>>> release-2.x branch project available, or I can backport the jenkins
>>> pipeline to that branch as well to get rid of unnecessary jenkins
>>> Matt Sicker <boa...@gmail.com>
> Matt Sicker <boa...@gmail.com>