.successful a, .successful a:visited, .successful a:link, .successful a:hover,.successful a:active {color:#393} .failed a, .failed a:visited, .failed a:link, .failed a:hover,.failed a:active {color:#d62829} td a, td a:link, td a:visited, td a:hover, td a:active {background:transparent;font-family: Arial, sans-serif;text-decoration:underline;} td a:link {color:#369;} td a:visited {color:#444;} td a:hover, td a:active {color:#036;} td a:hover {text-decoration:none;}

Cargo > Containers - JBoss 7.1.x > #76 has failed 3 times. This build was triggered at the scheduled time of 1:30 PM 1/14 tests failed. This plan has been failing since CARGO-SAMPLESJBOSS71X-74 (Scheduled build, 2 days before). Failing Jobs Default Job (Default Stage) Duration: 7 minutes Tests: 1 of 14 failed Logs | Artifacts Code Changes This build does not have any commits. Tests See full test details Existing Test Failures (1) ExistingConfigurationTest : Deploy war statically (Default Job) Fixed Tests (4) ExistingConfigurationTest : Start with one expanded war deployed (Default Job) RemoteDeploymentTest : Deploy undeploy redeploy war remotely (Default Job) RemoteDeploymentTest : Change war context and deploy undeploy remotely (Default Job) WarCapabilityContainerTest : Deploy war defined with relative path (Default Job) Email generated by Atlassian Bamboo - if you wish to stop receiving these emails edit your user profile or notify your administrator

Actions View Online Add Comments Link to JIRA issue