On Tue, May 10, 2011 at 8:04 AM, Niklas Gustavsson <nik...@protocol7.com>wrote:
> On Mon, May 9, 2011 at 7:00 PM, Reto Bachmann-Gmuer
> <reto.bachm...@trialox.org> wrote:
> > Since the begginning of May all Clerezza builds failed with the
> > follwoing error message:
> >
> > [INFO] *[deploy:deploy {execution: default-deploy}]*[JENKINS]
> > Archiving
> /home/hudson/hudson-slave/workspace/clerezza-trunk-1.6/trunk-1.6/slf4j-scala-api/target/slf4j-scala-api-1.6.1-sources.jar
> > to
> /home/hudson/hudson/jobs/clerezza-trunk-1.6/modules/org.apache.clerezza.ext$slf4j-scala-api/builds/2011-05-06_10-10-10/archive/org.apache.clerezza.ext/slf4j-scala-api/1.6.1/slf4j-scala-api-1.6.1-sources.jar
> > [INFO]
> ------------------------------------------------------------------------[ERROR]
> > BUILD ERROR[INFO]
> > ------------------------------------------------------------------------
> > [INFO] Error deploying artifact: Authentication failed: Cannot
> > connect. Reason: java.net.ConnectException: Connection refused
> >
> > How can this be fixed?
>
> We need more information here. To where is it trying to connect? Do
> you see this only in Jenkins or also when running on your own
> machines?
>
I first didn't have a login/password for repository.apache.org configured in
my local settings.xml, so this failed with a good reason. But after adding
the server section with a password for ci-hudson (which I once found on the
build server) I could deploy from local. I don't think that I have the
permissions to edit the settings.xml on jenkins to put this (back) in there.
Our pom repository-section looks as follows:
<repository>
<id>apache.releases.https</id>
<name>Apache Release Distribution Repository</name>
<url>
https://repository.apache.org/service/local/staging/deploy/maven2</url>
</repository>
<snapshotRepository>
<id>apache.snapshots.https</id>
<name>Apache Development Snapshot Repository</name>
<url>
https://repository.apache.org/content/repositories/snapshots</url>
</snapshotRepository>
Cheers,
Reto
>
> /niklas
>
