Post-Installation Tasks → Troubleshooting → Troubleshooting Deployments
See the following if you have trouble with your deployment for help with resolving and continuing the deployment.
If a deployment request is stuck in the "In Progress" status, it usually means that it is waiting for an action from someone or a response from the integrating product. The provider now allows for provider polling in several of the plugins. See the documentation for your plugin for information on how to use this feature.
To progress the request, try resolving whatever is holding it up. Some common things you need to do to are as follows:
If a deployment requests fails and you want to edit the deployment tasks to fix an issue, you must first progress the release package or deployable release train to which it belongs back to a state that allows edit.
If the deployment task is part of a child release package you must progress the parent release package or deployable release train to which it belongs back to a state that allows edit.The highest level in the hierarchy controls the process.
If you are using the default implementation, manual deployment tasks have a required field, RLM_TASK_OWNER, that is required. It is an extended field, and therefore isn't marked as required in the form. If the submitted item has no owner, the task fails.
If you cannot determine the cause of a failure, you can view the rlc.log file to see more information.
To view the log file:
C:\Program Files\Serena\SBM\Common\Tomcat 7.0\server\default\logs
Copyright © 2012–2017 Serena Software, Inc. All rights reserved.