[JIRA] (JENKINS-16198) Redeploy Artifacts functionality add ability to change build's status according to redeploy status.

Fri, 28 Dec 2012 02:36:57 -0800

In the fact build is ok. But fail only "Deploy artifacts to maven" post-build action. In this case I don't recive any email by the way.

In the log I see such:
22:58:02 [INFO] ------------------------------------------------------------------------
22:58:02 [INFO] BUILD SUCCESS
22:58:02 [INFO] ------------------------------------------------------------------------
22:58:02 [INFO] Total time: 48:01.737s
22:58:02 [INFO] Finished at: Thu Dec 27 22:58:02 IST 2012
22:58:03 [INFO] Final Memory: 265M/1051M
22:58:04 [INFO] ------------------------------------------------------------------------
22:58:04 Waiting for Jenkins to finish collecting data
22:58:07 channel stopped
22:58:08 Maven RedeployPublished use remote maven settings from : /var/lib/jenkins/.m2/settings.xml
22:58:09 [ERROR] uniqueVersion == false is not anymore supported in maven 3
.....[cut].....
22:58:18 at org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader.read(MetadataXpp3Reader.java:1189)
22:58:18 at org.apache.maven.artifact.repository.metadata.io.xpp3.MetadataXpp3Reader.read(MetadataXpp3Reader.java:1122)
22:58:18 at org.apache.maven.repository.internal.MavenMetadata.read(MavenMetadata.java:97)
22:58:18 ... 17 more
22:58:18 [INFO] Deployment failed after 9.4 sec
22:58:18 Build step 'Deploy artifacts to Maven repository' changed build result to FAILURE

But build is ok, there no any compilation error or something wrong. To fix the build need only to perform redeploy.

Our PM and Builds Manager very frustrating for this because buid is "red", but in the fact it "green".
Redeploy is not changing the status of the build.

I'm understading your position, but in general I think that such post-build action can change build status in case if it's was a reason due to which build is failed.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to