Deployer 10.5 | Deploying Assets from Source webMethods Runtimes | Rebuilding a Build
 
Rebuilding a Build
The Status column on the Projects > project > Build page indicates whether each project build is in sync with the current project definition. If the build and the current project definition are in sync, the column shows . If the project definition has changed since the build was created, the column shows .
If a project build is out of sync with the current project definition or contains assets that you know have changed on the source servers, and you want to re-create the build to bring it up to date, click in the Rebuild column for the build.
If you want to see the progress report, click in the Progress Report column. The progress report displays the updates for build and rebuild requests as they occur. This is useful in the case where the deployment build is large and it takes a long time to finish.
Note:
Deployer does not take dependencies into account while rebuilding project builds.
If the project for which you are trying to create the build contains unresolved dependencies, you will receive a message to that effect and the build process will fail. When asset dependencies are changed on the source server, you must first remove the dependent asset from the deployment set and save the deployment set. Then, add the asset back and save the deployment set. When Deployer displays the changed dependencies, resolve the dependencies and rebuild the project. For instructions on displaying and resolving unresolved dependencies, see Resolving Dependencies.