[JIRA] (JENKINS-59713) Glassfish 4 Failed deployment: org.codehaus.cargo.util.CargoException: Deployment has failed: null

0 views
Skip to first unread message

thestarkcoder@gmail.com (JIRA)

unread,
Oct 9, 2019, 10:00:03 AM10/9/19
to jenkinsc...@googlegroups.com
Francis Alcala updated an issue
 
Jenkins / Bug JENKINS-59713
Glassfish 4 Failed deployment: org.codehaus.cargo.util.CargoException: Deployment has failed: null
Change By: Francis Alcala
Summary: Glassfish 4 Failed deployment: org.codehaus.cargo.util.CargoException: Deployment has failed: null
[DeployPublisher][INFO] Attempting to deploy 1 war file(s)
[DeployPublisher][INFO] Deploying D:\webApp-3.0-SNAPSHOT-6.war to container GlassFish 4.x Remote with context bwlweb
ERROR: Build step failed with exception
org.codehaus.cargo.util.CargoException: Deployment has failed: null
at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.waitForProgressObject(AbstractJsr88Deployer.java:284)
at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.deploy(AbstractJsr88Deployer.java:133)
at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.redeploy(AbstractJsr88Deployer.java:210)
at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:81)
at hudson.plugins.deploy.CargoContainerAdapter$DeployCallable.invoke(CargoContainerAdapter.java:167)
at hudson.plugins.deploy.CargoContainerAdapter$DeployCallable.invoke(CargoContainerAdapter.java:136)
at hudson.FilePath.act(FilePath.java:1078)
at hudson.FilePath.act(FilePath.java:1061)
at hudson.plugins.deploy.CargoContainerAdapter.redeployFile(CargoContainerAdapter.java:133)
at hudson.plugins.deploy.PasswordProtectedAdapterCargo.redeployFile(PasswordProtectedAdapterCargo.java:95)
at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:113)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1074)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
at hudson.model.Run.execute(Run.java:1840)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Build step 'Deploy war/ear to a container' marked build as failure
SSH: Current build result is [FAILURE], not going to run.
Finished: FAILURE
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

thestarkcoder@gmail.com (JIRA)

unread,
Oct 9, 2019, 10:02:02 AM10/9/19
to jenkinsc...@googlegroups.com
Francis Alcala updated an issue
Change By: Francis Alcala
Environment: Jenkins ver. 2.190.1, Deploy to container plugin version 1.15
Failed deployment in glassfish 4 using *Deploy to container* plugin:

thestarkcoder@gmail.com (JIRA)

unread,
Oct 9, 2019, 10:03:03 AM10/9/19
to jenkinsc...@googlegroups.com
Francis Alcala updated an issue
Failed deployment in glassfish 4 using *Deploy to container* plugin:

[DeployPublisher][INFO] Attempting to deploy 1 war file(s)
[DeployPublisher][INFO] Deploying D:\webApp-3.0-SNAPSHOT-6.war to container GlassFish 4.x Remote with context bwlweb webApp

snoopi30@web.de (JIRA)

unread,
Oct 10, 2019, 2:50:02 PM10/10/19
to jenkinsc...@googlegroups.com
Robin Jansohn commented on Bug JENKINS-59713
 
Re: Glassfish 4 Failed deployment: org.codehaus.cargo.util.CargoException: Deployment has failed: null

I'm no GlassFish user so I can't reproduce this on my machine at the moment. I checked the code mentioned in the stack trace and the problem seems to be that the GlassFish deployment step returns failed instead of success. Maybe you can try deployment interactively to see if that is not working either?
Otherwise you need to give some more information, e.g. has it ever worked before, have you tried different different WAR locations (I see you are using drive D), are you using Jenkins slaves/agents, etc.

Reply all
Reply to author
Forward
0 new messages