]
Nick Boldt commented on JBIDE-22248:
------------------------------------
Well, I needed a way to get Alpha1 out the door, so eng-ops' workaround was deployed
to make things work.
Given that Forge & Red Deer are still red, it would seem that the workaround is the
only solution that works for the moment, but it's incomplete (Forge) or hasn't
been applied (RD).
Some CI jobs fail at deploying to Nexus
---------------------------------------
Key: JBIDE-22248
URL:
https://issues.jboss.org/browse/JBIDE-22248
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.4.0.Alpha1
Reporter: Martin Malina
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.4.0.Alpha1
Nick, can you take a look why mvn deploy fails here?
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
It worked for us in the past.
It says:
{code}
[WARNING] Could not transfer metadata
org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to
jboss-snapshots-repository
(
https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized ,
ReasonPhrase:Unauthorized.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 04:49 min
[INFO] Finished at: 2016-04-26T09:42:02-04:00
[INFO] Final Memory: 19M/612M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata
org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata
org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to
jboss-snapshots-repository
(
https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized ,
ReasonPhrase:Unauthorized. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the
following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{code}
I'm not exactly sure how this works. Or is this something that is managed in jenkins
config, so should I raise this with the jenkins team?
Cc: [~rawagner]