Re: [shade] which java version

[Romain Manni-Bucau]

@Slawomir: It is mainly due to some dependencies like jdepndency which is
java 8 only so the plugin is overall java 8 now.

@Tibor: changing a 7 to a 8 in a pom, hope it does not take us a day ;)
If we say it is java 8, it will not change much but if we say it is java 7
we must revert a few things so hope we can just downgrade/revert some
dep/code, didn't check this option yet.

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | Book



Le mer. 21 juil. 2021 à 23:27, Tibor Digana  a
écrit :

> What's the cost of this task? A day?
> Do you want to include it in the release version  3.4.0?
>
>
> On Wed, Jul 21, 2021 at 8:09 AM Romain Manni-Bucau 
> wrote:
>
> > Hi all,
> >
> > shade plugin pom defines java version to 7 (1.7) but it uses streams
> which
> > are java 8 only, should javaVersion property be updated?
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Old Blog
> >  | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn  | Book
> > <
> >
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> > >
> >
>

New release of Maven Shade Plugin

[Tibor Digana]

Can we cut a new release of m-shade-p?
Is there any pending bug fix or improvement that you want to include in the
release?

Cheers
Tibor

Re: [JENKINS] - New Maven Controller for the project

[Tibor Digana]

In my company, I also used 1GB for Xmx of Java Heap for the Jenkins JVM and
it was enough.
The subprocesses like Maven need to have much more memory to allocate for
themself rather than Jenkins JVM.
T

On Wed, Jul 21, 2021 at 6:38 PM Arnaud Héritier  wrote:

> I am looking at our builds and I try to understand why our agents are often
> disconnected during the builds.
> We have in general a stacktrace like
>
> maven6 was marked offline: Connection was broken: java.io.IOException:
> Pipe closed after 0 cycles
> at
> org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:118)
> at
> org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:101)
> at
> hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:92)
> at
> hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:73)
> at
> hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)
> at
> hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
> at
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> at
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
>
>
>
> As far I can see we are using 16Gb "hosts" for linux agents
>
> Something very strange is that the jenkins agent (this small component
> doing the link between the build host and the controller) is configured
> with `-Xms8g -Xmx8g` thus we are reserving for it 50% of the server mem
> (even more because of the non-heap)
> This one in general should require in general really less. 1Gb is already a
> lot from my exp.
> Due to this, the OS can see it has the biggest process on the host and
> decide to kill it when the rest of the memory is used by the build.
> I think we should decrease this value.
> (I can do it but I don't know how was configured the ci.apache.org agents
> and I would like to not add more issue if this setting was here in the past
>
> I don't think it is the root cause of our instabilities (at least all) and
> there is something else I have to find but it's a cheap fix to try
>
> FYI our agents VMs are ~like this today:
>
> - Java
> + Home: `/usr/local/asfpackages/java/oraclejdk-1.8.0-291/jre`
> + Vendor: Oracle Corporation
> + Version: 1.8.0_291
> + Maximum memory: 7.67 GB (8232370176)
> + Allocated memory: 7.67 GB (8232370176)
> + Free memory: 6.03 GB (6470953760)
> + In-use memory: 1.64 GB (1761416416)
> + GC strategy: ParallelGC
> + Available CPUs: 4
>
> 8Gb is reserved, 1Gb is used (because the GC does nothing as the Free mem
> is high)
>
> I would be in favor to try to launch them with -Xms128m
> -Xmx1g -XX:+UseG1GC -XX:+UseStringDeduplication
>
> I think it's enough customization to start with
>
> Cheers
>
> On Wed, Jul 21, 2021 at 1:28 PM Arnaud Héritier 
> wrote:
>
> > I am not sure about the setup
> > AFAICS we don't use any JDK installer (
> > https://ci-maven.apache.org/configureTools/ ) thus I suppose that the
> > different JDKs are supposed to be installed directly on the agent ?
> > I am not sure how it was done on the previous environment
> >
> > On Sun, Jul 18, 2021 at 5:30 PM Tibor Digana 
> > wrote:
> >
> >> The new CI  system has the following issue:
> >>
> >> /home/jenkins/tools/java/latest1.7/bin/java: not found
> >>
> >>
> >>
> https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-surefire/job/master/104/execution/node/183/log/
> >>
> >>
> >>
> >> On Wed, Jun 30, 2021 at 8:03 PM Gavin McDonald 
> >> wrote:
> >>
> >> > Hi Maven folks.
> >> >
> >> > Infra has decided to separate off the Maven build jobs from
> >> > ci-builds.apache.org over to its very own Jenkins Controller and
> >> Agents.
> >> >
> >> > This means that Maven now has a dedicated Jenkins environment for
> >> itself.
> >> > It
> >> > also means that no other projects build jobs can build on the Maven
> >> nodes;
> >> > and
> >> > then Maven jobs will no longer  be able to build on the ci-builds
> jobs.
> >> >
> >> > Your new Controller is set up as https://ci-maven.apache.org and all
> >> Maven
> >> > Committers
> >> > can login via LDAP and create jobs.
> >> >
> >> > At the time of writing, there is one node/agent attached but I am
> >> building
> >> > 4 more  - all
> >> > Ubuntu 20.04 and based in our Azure account.
> >> >
> >> > We can automagically move all your jobs over from ci-builds to
> ci-maven
> >> - I
> >> > just need someone to tell me go ahead and do it.
> >> >
> >> > In the meantime, feel free to have a test. The remaining 4 agents will
> >> be
> >> > online
> >> > by tomorrow. We will review after a month if 5 is enough nodes.
> >> >
> >> > As with other projects having their own dedicated controller, who have
> >> > taken advantage
> >> > of this isolation by having some nodes/agents given to the project as
> a
> >> > 'targeted donation'
> >

Re: [shade] which java version

[Tibor Digana]

What's the cost of this task? A day?
Do you want to include it in the release version  3.4.0?


On Wed, Jul 21, 2021 at 8:09 AM Romain Manni-Bucau 
wrote:

> Hi all,
>
> shade plugin pom defines java version to 7 (1.7) but it uses streams which
> are java 8 only, should javaVersion property be updated?
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>

Re: [shade] which java version

[Slawomir Jaranowski]

Hi,

very interesting case but I can't see 1.8 streams in
https://github.com/apache/maven-shade-plugin/tree/master

Can you point where you found it?

By the way, maybe it's time to start switching plugins to 1.8 ...


śr., 21 lip 2021 o 08:09 Romain Manni-Bucau 
napisał(a):

> Hi all,
>
> shade plugin pom defines java version to 7 (1.7) but it uses streams which
> are java 8 only, should javaVersion property be updated?
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>


-- 
Sławomir Jaranowski

Re: [JENKINS] - New Maven Controller for the project

[Arnaud Héritier]

ok Gavin

Thanks for your feedback
It's what I wanted to be sure, I didn't want to break something you are
maintaining

On Wed, Jul 21, 2021 at 6:47 PM Gavin McDonald  wrote:

> Hi Arnaud
>
> Surem feel free to tweak the node configs directly, these configs are not
> in version control or puppet.
>
> On Wed, Jul 21, 2021 at 6:38 PM Arnaud Héritier 
> wrote:
>
>> I am looking at our builds and I try to understand why our agents are
>> often disconnected during the builds.
>> We have in general a stacktrace like
>>
>> maven6 was marked offline: Connection was broken: java.io.IOException: Pipe 
>> closed after 0 cycles
>>  at 
>> org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:118)
>>  at 
>> org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:101)
>>  at 
>> hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:92)
>>  at 
>> hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:73)
>>  at 
>> hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)
>>  at 
>> hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
>>  at 
>> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
>>  at 
>> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
>>
>>
>>
>> As far I can see we are using 16Gb "hosts" for linux agents
>>
>> Something very strange is that the jenkins agent (this small component
>> doing the link between the build host and the controller) is configured
>> with `-Xms8g -Xmx8g` thus we are reserving for it 50% of the server mem
>> (even more because of the non-heap)
>> This one in general should require in general really less. 1Gb is already
>> a lot from my exp.
>> Due to this, the OS can see it has the biggest process on the host and
>> decide to kill it when the rest of the memory is used by the build.
>> I think we should decrease this value.
>> (I can do it but I don't know how was configured the ci.apache.org
>> agents and I would like to not add more issue if this setting was here in
>> the past
>>
>> I don't think it is the root cause of our instabilities (at least all)
>> and there is something else I have to find but it's a cheap fix to try
>>
>> FYI our agents VMs are ~like this today:
>>
>> - Java
>> + Home: `/usr/local/asfpackages/java/oraclejdk-1.8.0-291/jre`
>> + Vendor: Oracle Corporation
>> + Version: 1.8.0_291
>> + Maximum memory: 7.67 GB (8232370176)
>> + Allocated memory: 7.67 GB (8232370176)
>> + Free memory: 6.03 GB (6470953760)
>> + In-use memory: 1.64 GB (1761416416)
>> + GC strategy: ParallelGC
>> + Available CPUs: 4
>>
>> 8Gb is reserved, 1Gb is used (because the GC does nothing as the Free mem
>> is high)
>>
>> I would be in favor to try to launch them with -Xms128m
>> -Xmx1g -XX:+UseG1GC -XX:+UseStringDeduplication
>>
>> I think it's enough customization to start with
>>
>> Cheers
>>
>> On Wed, Jul 21, 2021 at 1:28 PM Arnaud Héritier 
>> wrote:
>>
>>> I am not sure about the setup
>>> AFAICS we don't use any JDK installer (
>>> https://ci-maven.apache.org/configureTools/ ) thus I suppose that the
>>> different JDKs are supposed to be installed directly on the agent ?
>>> I am not sure how it was done on the previous environment
>>>
>>> On Sun, Jul 18, 2021 at 5:30 PM Tibor Digana 
>>> wrote:
>>>
 The new CI  system has the following issue:

 /home/jenkins/tools/java/latest1.7/bin/java: not found


 https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-surefire/job/master/104/execution/node/183/log/



 On Wed, Jun 30, 2021 at 8:03 PM Gavin McDonald 
 wrote:

 > Hi Maven folks.
 >
 > Infra has decided to separate off the Maven build jobs from
 > ci-builds.apache.org over to its very own Jenkins Controller and
 Agents.
 >
 > This means that Maven now has a dedicated Jenkins environment for
 itself.
 > It
 > also means that no other projects build jobs can build on the Maven
 nodes;
 > and
 > then Maven jobs will no longer  be able to build on the ci-builds
 jobs.
 >
 > Your new Controller is set up as https://ci-maven.apache.org and all
 Maven
 > Committers
 > can login via LDAP and create jobs.
 >
 > At the time of writing, there is one node/agent attached but I am
 building
 > 4 more  - all
 > Ubuntu 20.04 and based in our Azure account.
 >
 > We can automagically move all your jobs over from ci-builds to
 ci-maven - I
 > just need someone to tell me go ahead and do it.
 >
 > In the meantime, feel free to have a test. The remaining 4 agents
 will be
 > online
 > by tomorrow. We will review after a month if 5 is enough nodes.
 >
 > As with other projects having their own dedicat

Re: [JENKINS] - New Maven Controller for the project

[Gavin McDonald]

Hi Arnaud

Surem feel free to tweak the node configs directly, these configs are not
in version control or puppet.

On Wed, Jul 21, 2021 at 6:38 PM Arnaud Héritier  wrote:

> I am looking at our builds and I try to understand why our agents are
> often disconnected during the builds.
> We have in general a stacktrace like
>
> maven6 was marked offline: Connection was broken: java.io.IOException: Pipe 
> closed after 0 cycles
>   at 
> org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:118)
>   at 
> org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:101)
>   at 
> hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:92)
>   at 
> hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:73)
>   at 
> hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)
>   at 
> hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
>   at 
> hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
>   at 
> hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
>
>
>
> As far I can see we are using 16Gb "hosts" for linux agents
>
> Something very strange is that the jenkins agent (this small component
> doing the link between the build host and the controller) is configured
> with `-Xms8g -Xmx8g` thus we are reserving for it 50% of the server mem
> (even more because of the non-heap)
> This one in general should require in general really less. 1Gb is already
> a lot from my exp.
> Due to this, the OS can see it has the biggest process on the host and
> decide to kill it when the rest of the memory is used by the build.
> I think we should decrease this value.
> (I can do it but I don't know how was configured the ci.apache.org agents
> and I would like to not add more issue if this setting was here in the past
>
> I don't think it is the root cause of our instabilities (at least all) and
> there is something else I have to find but it's a cheap fix to try
>
> FYI our agents VMs are ~like this today:
>
> - Java
> + Home: `/usr/local/asfpackages/java/oraclejdk-1.8.0-291/jre`
> + Vendor: Oracle Corporation
> + Version: 1.8.0_291
> + Maximum memory: 7.67 GB (8232370176)
> + Allocated memory: 7.67 GB (8232370176)
> + Free memory: 6.03 GB (6470953760)
> + In-use memory: 1.64 GB (1761416416)
> + GC strategy: ParallelGC
> + Available CPUs: 4
>
> 8Gb is reserved, 1Gb is used (because the GC does nothing as the Free mem
> is high)
>
> I would be in favor to try to launch them with -Xms128m
> -Xmx1g -XX:+UseG1GC -XX:+UseStringDeduplication
>
> I think it's enough customization to start with
>
> Cheers
>
> On Wed, Jul 21, 2021 at 1:28 PM Arnaud Héritier 
> wrote:
>
>> I am not sure about the setup
>> AFAICS we don't use any JDK installer (
>> https://ci-maven.apache.org/configureTools/ ) thus I suppose that the
>> different JDKs are supposed to be installed directly on the agent ?
>> I am not sure how it was done on the previous environment
>>
>> On Sun, Jul 18, 2021 at 5:30 PM Tibor Digana 
>> wrote:
>>
>>> The new CI  system has the following issue:
>>>
>>> /home/jenkins/tools/java/latest1.7/bin/java: not found
>>>
>>>
>>> https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-surefire/job/master/104/execution/node/183/log/
>>>
>>>
>>>
>>> On Wed, Jun 30, 2021 at 8:03 PM Gavin McDonald 
>>> wrote:
>>>
>>> > Hi Maven folks.
>>> >
>>> > Infra has decided to separate off the Maven build jobs from
>>> > ci-builds.apache.org over to its very own Jenkins Controller and
>>> Agents.
>>> >
>>> > This means that Maven now has a dedicated Jenkins environment for
>>> itself.
>>> > It
>>> > also means that no other projects build jobs can build on the Maven
>>> nodes;
>>> > and
>>> > then Maven jobs will no longer  be able to build on the ci-builds jobs.
>>> >
>>> > Your new Controller is set up as https://ci-maven.apache.org and all
>>> Maven
>>> > Committers
>>> > can login via LDAP and create jobs.
>>> >
>>> > At the time of writing, there is one node/agent attached but I am
>>> building
>>> > 4 more  - all
>>> > Ubuntu 20.04 and based in our Azure account.
>>> >
>>> > We can automagically move all your jobs over from ci-builds to
>>> ci-maven - I
>>> > just need someone to tell me go ahead and do it.
>>> >
>>> > In the meantime, feel free to have a test. The remaining 4 agents will
>>> be
>>> > online
>>> > by tomorrow. We will review after a month if 5 is enough nodes.
>>> >
>>> > As with other projects having their own dedicated controller, who have
>>> > taken advantage
>>> > of this isolation by having some nodes/agents given to the project as a
>>> > 'targeted donation'
>>> > so someone here may know of a Company will to donate 5 - 10 or more
>>> nodes
>>> > specifically
>>> > for Maven Jenkins environment. Infra can afford to ha

Re: [JENKINS] - New Maven Controller for the project

[Arnaud Héritier]

I am looking at our builds and I try to understand why our agents are often
disconnected during the builds.
We have in general a stacktrace like

maven6 was marked offline: Connection was broken: java.io.IOException:
Pipe closed after 0 cycles
at 
org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:118)
at 
org.apache.sshd.common.channel.ChannelPipedInputStream.read(ChannelPipedInputStream.java:101)
at 
hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:92)
at 
hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:73)
at 
hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)
at 
hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)



As far I can see we are using 16Gb "hosts" for linux agents

Something very strange is that the jenkins agent (this small component
doing the link between the build host and the controller) is configured
with `-Xms8g -Xmx8g` thus we are reserving for it 50% of the server mem
(even more because of the non-heap)
This one in general should require in general really less. 1Gb is already a
lot from my exp.
Due to this, the OS can see it has the biggest process on the host and
decide to kill it when the rest of the memory is used by the build.
I think we should decrease this value.
(I can do it but I don't know how was configured the ci.apache.org agents
and I would like to not add more issue if this setting was here in the past

I don't think it is the root cause of our instabilities (at least all) and
there is something else I have to find but it's a cheap fix to try

FYI our agents VMs are ~like this today:

- Java
+ Home: `/usr/local/asfpackages/java/oraclejdk-1.8.0-291/jre`
+ Vendor: Oracle Corporation
+ Version: 1.8.0_291
+ Maximum memory: 7.67 GB (8232370176)
+ Allocated memory: 7.67 GB (8232370176)
+ Free memory: 6.03 GB (6470953760)
+ In-use memory: 1.64 GB (1761416416)
+ GC strategy: ParallelGC
+ Available CPUs: 4

8Gb is reserved, 1Gb is used (because the GC does nothing as the Free mem
is high)

I would be in favor to try to launch them with -Xms128m
-Xmx1g -XX:+UseG1GC -XX:+UseStringDeduplication

I think it's enough customization to start with

Cheers

On Wed, Jul 21, 2021 at 1:28 PM Arnaud Héritier  wrote:

> I am not sure about the setup
> AFAICS we don't use any JDK installer (
> https://ci-maven.apache.org/configureTools/ ) thus I suppose that the
> different JDKs are supposed to be installed directly on the agent ?
> I am not sure how it was done on the previous environment
>
> On Sun, Jul 18, 2021 at 5:30 PM Tibor Digana 
> wrote:
>
>> The new CI  system has the following issue:
>>
>> /home/jenkins/tools/java/latest1.7/bin/java: not found
>>
>>
>> https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-surefire/job/master/104/execution/node/183/log/
>>
>>
>>
>> On Wed, Jun 30, 2021 at 8:03 PM Gavin McDonald 
>> wrote:
>>
>> > Hi Maven folks.
>> >
>> > Infra has decided to separate off the Maven build jobs from
>> > ci-builds.apache.org over to its very own Jenkins Controller and
>> Agents.
>> >
>> > This means that Maven now has a dedicated Jenkins environment for
>> itself.
>> > It
>> > also means that no other projects build jobs can build on the Maven
>> nodes;
>> > and
>> > then Maven jobs will no longer  be able to build on the ci-builds jobs.
>> >
>> > Your new Controller is set up as https://ci-maven.apache.org and all
>> Maven
>> > Committers
>> > can login via LDAP and create jobs.
>> >
>> > At the time of writing, there is one node/agent attached but I am
>> building
>> > 4 more  - all
>> > Ubuntu 20.04 and based in our Azure account.
>> >
>> > We can automagically move all your jobs over from ci-builds to ci-maven
>> - I
>> > just need someone to tell me go ahead and do it.
>> >
>> > In the meantime, feel free to have a test. The remaining 4 agents will
>> be
>> > online
>> > by tomorrow. We will review after a month if 5 is enough nodes.
>> >
>> > As with other projects having their own dedicated controller, who have
>> > taken advantage
>> > of this isolation by having some nodes/agents given to the project as a
>> > 'targeted donation'
>> > so someone here may know of a Company will to donate 5 - 10 or more
>> nodes
>> > specifically
>> > for Maven Jenkins environment. Infra can afford to hand you over 5 right
>> > now.
>> >
>> > Let me know if you have any questions, otherwise let me know when I can
>> > make the
>> > transfer of your jobs.
>> >
>> > Thanks
>> >
>> > --
>> >
>> > *Gavin McDonald*
>> > Systems Administrator
>> > ASF Infrastructure Team
>> >
>>
>
>
> --
> Arnaud Héritier
> Twitter/Skype : aheritier
>


-- 
Arna

[GitHub] [maven-artifact-transfer] dependabot[bot] opened a new pull request #40: Bump slf4j-api from 1.7.5 to 1.7.32

[GitBox]

dependabot[bot] opened a new pull request #40:
URL: https://github.com/apache/maven-artifact-transfer/pull/40


   Bumps [slf4j-api](https://github.com/qos-ch/slf4j) from 1.7.5 to 1.7.32.
   
   Commits
   
   See full diff in https://github.com/qos-ch/slf4j/commits";>compare view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.slf4j:slf4j-api&package-manager=maven&previous-version=1.7.5&new-version=1.7.32)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [JENKINS] - New Maven Controller for the project

[Arnaud Héritier]

I am not sure about the setup
AFAICS we don't use any JDK installer (
https://ci-maven.apache.org/configureTools/ ) thus I suppose that the
different JDKs are supposed to be installed directly on the agent ?
I am not sure how it was done on the previous environment

On Sun, Jul 18, 2021 at 5:30 PM Tibor Digana  wrote:

> The new CI  system has the following issue:
>
> /home/jenkins/tools/java/latest1.7/bin/java: not found
>
>
> https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-surefire/job/master/104/execution/node/183/log/
>
>
>
> On Wed, Jun 30, 2021 at 8:03 PM Gavin McDonald 
> wrote:
>
> > Hi Maven folks.
> >
> > Infra has decided to separate off the Maven build jobs from
> > ci-builds.apache.org over to its very own Jenkins Controller and Agents.
> >
> > This means that Maven now has a dedicated Jenkins environment for itself.
> > It
> > also means that no other projects build jobs can build on the Maven
> nodes;
> > and
> > then Maven jobs will no longer  be able to build on the ci-builds jobs.
> >
> > Your new Controller is set up as https://ci-maven.apache.org and all
> Maven
> > Committers
> > can login via LDAP and create jobs.
> >
> > At the time of writing, there is one node/agent attached but I am
> building
> > 4 more  - all
> > Ubuntu 20.04 and based in our Azure account.
> >
> > We can automagically move all your jobs over from ci-builds to ci-maven
> - I
> > just need someone to tell me go ahead and do it.
> >
> > In the meantime, feel free to have a test. The remaining 4 agents will be
> > online
> > by tomorrow. We will review after a month if 5 is enough nodes.
> >
> > As with other projects having their own dedicated controller, who have
> > taken advantage
> > of this isolation by having some nodes/agents given to the project as a
> > 'targeted donation'
> > so someone here may know of a Company will to donate 5 - 10 or more nodes
> > specifically
> > for Maven Jenkins environment. Infra can afford to hand you over 5 right
> > now.
> >
> > Let me know if you have any questions, otherwise let me know when I can
> > make the
> > transfer of your jobs.
> >
> > Thanks
> >
> > --
> >
> > *Gavin McDonald*
> > Systems Administrator
> > ASF Infrastructure Team
> >
>


-- 
Arnaud Héritier
Twitter/Skype : aheritier