infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <>
Subject [jira] [Updated] (INFRA-18812) Jenkins slaves .mavenrc file overrides MAVEN_OPTS value
Date Fri, 02 Aug 2019 06:28:00 GMT


Hervé Boutemy updated INFRA-18812:
    Status: Waiting for Infra  (was: Waiting for user)

[~gmcdonald] Hi Gavin
Shardingshpere merged the commit: their Jenkins jobs won't pollute with .mavenrc any more
can you cleanup existing /home/jenkins/.mavenrc files on every slaves, please?

> Jenkins slaves .mavenrc file overrides MAVEN_OPTS value
> -------------------------------------------------------
>                 Key: INFRA-18812
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>         Environment:
>            Reporter: Hervé Boutemy
>            Assignee: Gavin
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
> we have 4 Maven core ITs failing for 1 month on some Linux slave nodes: never Windows,
not every Linux slave (but most)
> after hard debug session, we found that the value of MAVEN_OPTS defined during the IT
is not taken into account
> And we finally found the root cause: there is a /home/jenkins/.mavenrc script that defines
MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=256m
> this fully overrides MAVEN_OPTS value that was defined before and that our IT requires
> I could not find this .mavenrc file in Puppet.
> I suppose removing this file is not really an option: could you update this file on every
slave to define:
> MAVEN_OPTS=-Xmx1024m -XX:MaxPermSize=256m ${MAVEN_OPTS}
> thanks in advance

This message was sent by Atlassian JIRA

View raw message