-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Maven Integration plugin 2.14
Jenkins ver. 2.19.3
We use a keystore with client certificates to authenticate with remote severs. We normally use MAVEN_OPTS to pass JDK -Djavax.net.ssl.keyStore parameters to Maven
This works for a Maven project, and Invoke top-level Maven targets steps.
However the setting is ignored in the Deploy artifacts to Maven repository step/publisher. Setting a normal MAVEN_OPTS via EnjInject plugin also seems to have no effect
Sample output (with haproxy's verify optional):
Maven RedeployPublisher use remote IQ-449a33ad36b4 maven settings from : /tmp/settings2743001247239769636.xml [INFO] Deployment in https://mvnrepo.acme-it.com/content/repositories/snapshots/ (id=,uniqueVersion=true) Deploying the main artifact aggregator-29.3.0-SNAPSHOT.pom Downloading: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/acme/aggregator/29.3.0-SNAPSHOT/maven-metadata.xml ERROR: Failed to retrieve remote metadata com.acme:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.acme:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata com.acme:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.acme:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.
Also adding a per-step JVM Options field (like Invoke top-level Maven targets) would be nice
[JENKINS-40011] Deploy artifacts to Maven repository ignores Global MAVEN_OPTS
Description |
Original:
We use a keystore with client certificates to authenticate with remote severs. We normally use MAVEN_OPTS to pass JDK {{-Djavax.net.ssl.keyStore}} parameters to Maven This works for a Maven project, and Invoke top-level Maven targets steps. However the setting is ignored in the Deploy artifacts to Maven repository step/publisher. Setting a normal MAVEN_OPTS via EnjInject plugin also seems to have no effect Sample output: {code}[INFO] Deployment in https://mvnrepo.acme-it.com:5972/content/repositories/snapshots/ (id=snapshots,uniqueVersion=true) Deploying the main artifact aggregator-0.0.1-SNAPSHOT.pom Downloading: https://mvnrepo.acme-it.com:5972/content/repositories/snapshots/com/acme/aggregator/0.0.1-SNAPSHOT/maven-metadata.xml ERROR: Failed to retrieve remote metadata com.acme:aggregator:0.0.1-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.acme:aggregator:0.0.1-SNAPSHOT/maven-metadata.xml from/to snapshots (https://mvnrepo.acme-it.com:5972/content/repositories/snapshots/): Received fatal alert: handshake_failure org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata com.acme:aggregator:0.0.1-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.acme:aggregator:0.0.1-SNAPSHOT/maven-metadata.xml from/to snapshots (https://mvnrepo.acme-it.com:5972/content/repositories/snapshots/): Received fatal alert: handshake_failure{code} Also adding a per-step JVM Options field (like Invoke top-level Maven targets) would be nice |
New:
We use a keystore with client certificates to authenticate with remote severs. We normally use MAVEN_OPTS to pass JDK {{-Djavax.net.ssl.keyStore}} parameters to Maven This works for a Maven project, and Invoke top-level Maven targets steps. However the setting is ignored in the Deploy artifacts to Maven repository step/publisher. Setting a normal MAVEN_OPTS via EnjInject plugin also seems to have no effect Sample output: {code}Maven RedeployPublisher use remote IQ-449a33ad36b4 maven settings from : /tmp/settings2743001247239769636.xml [INFO] Deployment in https://mvnrepo.acme-it.com/content/repositories/snapshots/ (id=,uniqueVersion=true) Deploying the main artifact aggregator-29.3.0-SNAPSHOT.pom Downloading: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/purato/aggregator/29.3.0-SNAPSHOT/maven-metadata.xml ERROR: Failed to retrieve remote metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.{code} Also adding a per-step JVM Options field (like Invoke top-level Maven targets) would be nice |
Description |
Original:
We use a keystore with client certificates to authenticate with remote severs. We normally use MAVEN_OPTS to pass JDK {{-Djavax.net.ssl.keyStore}} parameters to Maven This works for a Maven project, and Invoke top-level Maven targets steps. However the setting is ignored in the Deploy artifacts to Maven repository step/publisher. Setting a normal MAVEN_OPTS via EnjInject plugin also seems to have no effect Sample output: {code}Maven RedeployPublisher use remote IQ-449a33ad36b4 maven settings from : /tmp/settings2743001247239769636.xml [INFO] Deployment in https://mvnrepo.acme-it.com/content/repositories/snapshots/ (id=,uniqueVersion=true) Deploying the main artifact aggregator-29.3.0-SNAPSHOT.pom Downloading: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/purato/aggregator/29.3.0-SNAPSHOT/maven-metadata.xml ERROR: Failed to retrieve remote metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.{code} Also adding a per-step JVM Options field (like Invoke top-level Maven targets) would be nice |
New:
We use a keystore with client certificates to authenticate with remote severs. We normally use MAVEN_OPTS to pass JDK {{-Djavax.net.ssl.keyStore}} parameters to Maven This works for a Maven project, and Invoke top-level Maven targets steps. However the setting is ignored in the Deploy artifacts to Maven repository step/publisher. Setting a normal MAVEN_OPTS via EnjInject plugin also seems to have no effect Sample output (with haproxy's {{verify optional}}): {code}Maven RedeployPublisher use remote IQ-449a33ad36b4 maven settings from : /tmp/settings2743001247239769636.xml [INFO] Deployment in https://mvnrepo.acme-it.com/content/repositories/snapshots/ (id=,uniqueVersion=true) Deploying the main artifact aggregator-29.3.0-SNAPSHOT.pom Downloading: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/purato/aggregator/29.3.0-SNAPSHOT/maven-metadata.xml ERROR: Failed to retrieve remote metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.{code} Also adding a per-step JVM Options field (like Invoke top-level Maven targets) would be nice |
Description |
Original:
We use a keystore with client certificates to authenticate with remote severs. We normally use MAVEN_OPTS to pass JDK {{-Djavax.net.ssl.keyStore}} parameters to Maven This works for a Maven project, and Invoke top-level Maven targets steps. However the setting is ignored in the Deploy artifacts to Maven repository step/publisher. Setting a normal MAVEN_OPTS via EnjInject plugin also seems to have no effect Sample output (with haproxy's {{verify optional}}): {code}Maven RedeployPublisher use remote IQ-449a33ad36b4 maven settings from : /tmp/settings2743001247239769636.xml [INFO] Deployment in https://mvnrepo.acme-it.com/content/repositories/snapshots/ (id=,uniqueVersion=true) Deploying the main artifact aggregator-29.3.0-SNAPSHOT.pom Downloading: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/purato/aggregator/29.3.0-SNAPSHOT/maven-metadata.xml ERROR: Failed to retrieve remote metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.purato:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.{code} Also adding a per-step JVM Options field (like Invoke top-level Maven targets) would be nice |
New:
We use a keystore with client certificates to authenticate with remote severs. We normally use MAVEN_OPTS to pass JDK {{-Djavax.net.ssl.keyStore}} parameters to Maven This works for a Maven project, and Invoke top-level Maven targets steps. However the setting is ignored in the Deploy artifacts to Maven repository step/publisher. Setting a normal MAVEN_OPTS via EnjInject plugin also seems to have no effect Sample output (with haproxy's {{verify optional}}): {code}Maven RedeployPublisher use remote IQ-449a33ad36b4 maven settings from : /tmp/settings2743001247239769636.xml [INFO] Deployment in https://mvnrepo.acme-it.com/content/repositories/snapshots/ (id=,uniqueVersion=true) Deploying the main artifact aggregator-29.3.0-SNAPSHOT.pom Downloading: https://mvnrepo.acme-it.com/content/repositories/snapshots/com/acme/aggregator/29.3.0-SNAPSHOT/maven-metadata.xml ERROR: Failed to retrieve remote metadata com.acme:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.acme:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. org.apache.maven.artifact.deployer.ArtifactDeploymentException: Failed to retrieve remote metadata com.acme:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml: Could not transfer metadata com.acme:aggregator:29.3.0-SNAPSHOT/maven-metadata.xml from/to (https://mvnrepo.acme-it.com/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.{code} Also adding a per-step JVM Options field (like Invoke top-level Maven targets) would be nice |
Component/s | New: deploy-plugin [ 15520 ] | |
Component/s | Original: maven-plugin [ 16033 ] |
Component/s | New: maven-plugin [ 16033 ] | |
Component/s | Original: deploy-plugin [ 15520 ] |