Following these instructions we have a job to deploy an xCP application. However, we have noticed that the "Publish xCP Application" action always sets the build status to "Failed" even though the deployment was successful.
Below are the last few lines returns by xMS on successful deploy:
---->>>>----INFO:Finished BAM deployment
---->>>>----INFO:Bam deployer execution time = 40 secs
---->>>>----INFO:No actions needed during xPlore upgradeData
---->>>>----INFO:Started SearchDeployer 'PostDeploy'
---->>>>----INFO:No actions needed during xPlore PostDeploy
---->>>>----INFO:Finished executing SearchDeployer 'PostDeploy' (Execution time = 0 secs)
---->>>>----INFO:Application URL: http://localhost:8080/Test
---->>>>----INFO:AppDeploymentManager deployedin....654secs
---->>>>----INFO:Registering deployed application into catalog: environment: xCP-2.2-Developer-Environment-X1, name = Test, namespace = tst, version = 1.0.0
---->>>>----INFO:Deploying application was successful
---->>>>----INFO:CommandRequest ID is com.emc.xms.execution.CommandRequest@52f2aeea
---->>>>----Deploy XCP Applicaion command executed
In XMSExecutionWrapper.java it is expecting the last output from xMS to contain "SUCCESS" which xMS does not return. Hence, the build status is always set to "Failed".
return (result != null && result == 0 && "SUCCESS".equals(outputLine));
Following these instructions we have a job to deploy an xCP application. However, we have noticed that the "Publish xCP Application" action always sets the build status to "Failed" even though the deployment was successful.
Below are the last few lines returns by xMS on successful deploy:
In XMSExecutionWrapper.java it is expecting the last output from xMS to contain "SUCCESS" which xMS does not return. Hence, the build status is always set to "Failed".