Hi Olivier, yes, maybe it was the scanning flag, that was turned on for the stage repository. But I also added the retryFailedDeploymentCount flag to the deploy plugin, don't know which one of them fixed my problem. But during my research I found a JIRA ticket for maven deploy plugin, where someone mentioned, that archiva is sometimes not responding for a long time during upload. I think I will create a ticket in our JIRA for this and try to create a load test.
Cheers Martin Am Montag, 24. April 2017, 09:42:38 CEST schrieb Olivier Lamy: > Hi Martin > Sorry for delayed answer (busy weekend). > It looks you figure out how to deploy. > Not sure what is the cause.. I usually go to to target/checkout folder and > redeploy using -rf maven option. > > On 22 April 2017 at 09:10, Martin <[email protected]> wrote: > > Hi, > > > > I'm trying to release the new version, but I'm getting errors from the > > repository server archiva-repository.apache.org > > > > Error message: > > Failed to transfer file: http://www.apache.org/dev/ > > service_unavailable.html? > > site=archiva-repository.apache.org&code=502. Return code is: 405, > > ReasonPhrase: Method Not Allowed. > > > > On each run, the error occurs on a different stage of the build process, > > so I > > think there is something wrong with the archiva server. > > > > The redback build/upload yesterday ran fine. > > > > Olivier, do you have access to the log files there? > > > > Greetings > > > > Martin
