Unable to deploy artifacts to Nexus

Tags: #<Tag:0x00007f1f7f456280>

Anyone know if there were any changes to the mavenrepo.openmrs.org credentials recently (sometime after 1pm yesterday, August 5th)?

All of sudden, our CI server here at PIH is unable to deploy to mavenrepo with error listed below–last successful upload was at 1:40pm yesterday.

Looks like OpenMRS CI is still deploying properly.

build 05-Aug-2015 17:26:54 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project pihcore: Failed to deploy artifacts: Could not transfer artifact org.openmrs.module:pihcore:pom:1.0-20150805.212654-584 from/to openmrs-repo-snapshots (http://mavenrepo.openmrs.org/nexus/content/repositories/snapshots): Failed to transfer file: http://mavenrepo.openmrs.org/nexus/content/repositories/snapshots/org/openmrs/module/pihcore/1.0-SNAPSHOT/pihcore-1.0-20150805.212654-584.pom. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

Did you check out the troubleshooting section at the bottom of this page?

https://wiki.openmrs.org/display/docs/Release+Process

When you are deploying a module to nexus repository using: mvn clean deploy command You may get an error message like:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project…Return code is: 401, ReasonPhrase:Unauthorized.

To solve this you need to add a server for the module repo by adding the following with Nexus repository credentials to the list of servers in the file /M2_HOME/settings.xml.

<server>
   <id>openmrs-repo-modules</id>
   <username>username</username>
   <password>password</password>
</server>

I’ll double-check, but we haven’t touched the settings.xml on our bamboo server in ages, so I was double-checking if there was any recent account management or clean-up where that account may no longer have access.

Is anyone else having this same issue with other accounts?

@ryan am getting the same exact problem right now. Though it has always been working before.

May be they’re having authentication issues in nexus that have nothing to do with us