Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
MIME-Version: 1.0
Reply-To: keith.wall@gmail.com
In-Reply-To: <CAKYPbisRMb57GVg+u0L=hoQhEawTGyQwNhMFr21TsZs-FDaUFw@mail.gmail.com>
References: <CAFEMS4tzw_qgLd2n9kuk97PvYayaqnxVAM2TFC6Bq6Wg_QfQ-A@mail.gmail.com>
 <CAFEMS4tDpSRNWB6rOAAv73bJe5j+oa9ocC6K4VAfFEZiS+cGuQ@mail.gmail.com>
 <CAFEMS4tCAQ8wSbGrJVKNL-mUY33XR2gS2e75wsm+9U8toD6MRw@mail.gmail.com> <CAKYPbisRMb57GVg+u0L=hoQhEawTGyQwNhMFr21TsZs-FDaUFw@mail.gmail.com>
From: Keith W <keith.wall@gmail.com>
Date: Wed, 8 Jun 2016 23:15:02 +0100
Message-ID: <CAFEMS4vUkUOTvqZaJJz+FXfF3JDZAfQAAYiPYRKTnQXUF6vKkQ@mail.gmail.com>
Subject: Re: ubuntu-4 Non-parseable settings /home/jenkins/.m2/settings.xml:
To: builds@apache.org
Content-Type: text/plain; charset=UTF-8
archived-at: Wed, 08 Jun 2016 22:15:06 -0000

Pono,

Thanks for the update.  Much appreciated.

cheers, Keith

On 8 June 2016 at 21:02, Pono Takamori <pono@apache.org> wrote:
> The job just built correctly on ubuntu-4.  The jenkins-test-* images have
> been updated to use the correct settings.xml file.  You can file a ticket
> on JIRA if this is a recurring issue.
>
> Cheers,
> -Pono
>
> On Wed, Jun 8, 2016 at 7:51 PM, Keith W <keith.wall@gmail.com> wrote:
>
>> Hello builds,
>>
>> Would anyone be able to take a look at this please?
>>
>> Kind regards, Keith Wall.
>>
>> On 7 June 2016 at 14:41, Keith W <keith.wall@gmail.com> wrote:
>> > Hello Builds,
>> >
>> >
>> > We are still seeing this error. It just occurred a few minutes ago on
>> > jenkins-test-d2e.
>> >
>> >
>> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-JoramJMSTest/jdk=latest1.7,label=Ubuntu,qpid.joramtests=qpid-jms-client/497/
>> >
>> >
>> > [trunk] $ /home/jenkins/tools/maven/apache-maven-3.0.4/bin/mvn -f
>> > pom.xml -Dlabel=Ubuntu -Djdk=latest1.7
>> > -Dqpid.joramtests=qpid-jms-client -DskipTests=true clean verify -fae
>> > [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
>> >
>> >
>> > On 3 June 2016 at 09:16, Keith W <keith.wall@gmail.com> wrote:
>> >> Hello builds
>> >>
>> >> We (Apache Qpid) are seeing failures on Jenkins ubuntu-4 with the
>> >> following error for the last few builds.
>> >>
>> >>
>> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-JoramJMSTest/494/
>> >>
>> >> The job doesn't knowingly try to influence the contents of this file,
>> >> so I suspect something else has caused the file to become corrupted.
>> >>
>> >> Could someone take a look?
>> >>
>> >> No changes for http://svn.apache.org/repos/asf/qpid/java/trunk since
>> >> the previous build
>> >> [trunk] $ /home/jenkins/tools/maven/apache-maven-3.0.4/bin/mvn -f
>> >> pom.xml -Dlabel=Ubuntu -Djdk=latest1.7
>> >> -Dqpid.joramtests=qpid-amqp-1-0-client-jms -DskipTests=true clean
>> >> verify -fae
>> >> [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
>> >>
>> >> Kind regards, Keith Wall.
>>