[ 
https://issues.apache.org/jira/browse/MNG-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489728#comment-16489728
 ] 

Samir Shaik commented on MNG-6416:
----------------------------------

[~michael-o]: The logs don't have consistent failure reasons, so have not 
attached the logs. Also I am unable to reproduce this in the local machine, it 
fails in Jenkins running on Jenkins Centos. I have already attached the images 
which show different reasons for the same build to fail, run one after the 
other. If you would like to look at the log file then I don't mind masking 
company internal details and attaching the logs.

> Parallel Build with option "-T 1C" fails on Maven 3.5.3 + Linux Centos + 
> Jenkins
> --------------------------------------------------------------------------------
>
>                 Key: MNG-6416
>                 URL: https://issues.apache.org/jira/browse/MNG-6416
>             Project: Maven
>          Issue Type: Bug
>          Components: Bootstrap & Build, Performance
>    Affects Versions: 3.5.3
>         Environment: Linux Centos
>            Reporter: Samir Shaik
>            Priority: Major
>
> +*Environment*+
> *OS:* Linux Centos
> *CI/CD Tool:* Jenkins
> *Maven:* 3.5.3
> *Model:* multi module project
> With Maven version 3.5.0 we were having issues with metadata.xml being 
> wrongly updated by Maven on Nexus3. So we upgraded to 3.5.3 to resolve the 
> issue around metadata.xml issue. With 3.5.3 we are unable to run parallel 
> builds with "-T 1C" option.
> Note that the same setup works smooth on my local machine which has Windows 7 
> OS. This has to do something with Maven3.5.3 + Linux + Jenkins. Would 
> appreciate if you can take a look and get to the root cause of this issue. We 
> are ready to provide more details if that helps.
>  
> *Expected behavior:* Build would run successfully.
> *Actual Behavior:* Build fails every time with different reasons. Ran build 4 
> times and the results are attached to this ticket



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to