You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2016/06/05 08:15:59 UTC

[jira] [Updated] (INFRA-12040) Maven Integration builds Problems with settings.xml

     [ https://issues.apache.org/jira/browse/INFRA-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise updated INFRA-12040:
----------------------------------------
    Description: 
Hi. currently the build of the [integration test|https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/job/core-integration-testing-maven-3-jdk-1.7/1774/console] is failing based on wrong {{settings.xml}} file which is configured to use the global {{settings.xml}

I would suggest to provided a {{settings.xml}} via config file provider if exists ?


{noformat}
OS name: "linux", version: "3.13.0-30-generic", arch: "amd64", family: "unix"
[ERROR] Error executing Maven.
[ERROR] 1 problem was encountered while building the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected character in markup % (position: START_TAG seen ...</username>\n     <password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18

Build step 'Invoke top-level Maven targets' marked build as failure
Recording test results
{noformat}

Update:
https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x/1292/console This build fails based on the same issue.



  was:
Hi. currently the build of the [integration test|https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/job/core-integration-testing-maven-3-jdk-1.7/1774/console] is failing based on wrong {{settings.xml}} file which is configured to use the global {{settings.xml}

I would suggest to provided a {{settings.xml}} via config file provider if exists ?


{noformat}
OS name: "linux", version: "3.13.0-30-generic", arch: "amd64", family: "unix"
[ERROR] Error executing Maven.
[ERROR] 1 problem was encountered while building the effective settings
[FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected character in markup % (position: START_TAG seen ...</username>\n     <password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18

Build step 'Invoke top-level Maven targets' marked build as failure
Recording test results
{noformat}



> Maven Integration builds Problems with settings.xml
> ---------------------------------------------------
>
>                 Key: INFRA-12040
>                 URL: https://issues.apache.org/jira/browse/INFRA-12040
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>         Environment: Building remotely on jenkins-test-b2e (jenkins-cloud-4GB cloud-slave Ubuntu ubuntu jenkins-cloud-8GB)
>            Reporter: Karl Heinz Marbaise
>            Priority: Blocker
>
> Hi. currently the build of the [integration test|https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/job/core-integration-testing-maven-3-jdk-1.7/1774/console] is failing based on wrong {{settings.xml}} file which is configured to use the global {{settings.xml}
> I would suggest to provided a {{settings.xml}} via config file provider if exists ?
> {noformat}
> OS name: "linux", version: "3.13.0-30-generic", arch: "amd64", family: "unix"
> [ERROR] Error executing Maven.
> [ERROR] 1 problem was encountered while building the effective settings
> [FATAL] Non-parseable settings /home/jenkins/.m2/settings.xml: unexpected character in markup % (position: START_TAG seen ...</username>\n     <password><%... @14:18)  @ /home/jenkins/.m2/settings.xml, line 14, column 18
> Build step 'Invoke top-level Maven targets' marked build as failure
> Recording test results
> {noformat}
> Update:
> https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x/1292/console This build fails based on the same issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)