| |
Results |
|
MCLG: Unix: Post-Deployment Clean-up of Removed Files May Fail during incremental deploy.
|
MCLG: Unix: Post-Deployment Clean -up of Removed Files May Fail during incremental deploy.
|
|
|
|
General maintenance for slow deploys or hanging deploys or take longer than usual in the initializing stage.
|
The following items can be used for general clean up and troubleshooting of deploys hanging or not starting. After using Collage for a while more and more deploy activity is stored in the administration database with not a real automatic way of cleaning it up. Over time you may see deploys hanging, not starting or generally taking a long time in the initializing stage.
|
|
|
|
MCLG 4.5.1+: New changed asset deploy fixes require absolute path for FTP transfer
|
In Collage 4.5.1, there were many improvements and bug fixes related to changed asset deploys. To implement these changes, it is now required that the FTP remote directory be an absolute path. This allows the deploy to accurately delete and clean up files during a changed asset deploy.
|
|
|
|
MCLG: Activities Running on other servers shows deploy activities that are no longer running when load balanced.
|
This can happen if the deploy server is unable to update the deploy log when the deploy is finished. This can happen when the deploy server loses contact with the admin database before the deploy is finished. In order to clean these entries up follow these steps.
|
|
|
|
MCLG: Changed asset deploy is generating assets it should not generate
|
Workaround: The DeployAssetDependencies table is indexed by the deploy map's asset id number. So, if you create a new deploy map, it will get a new asset id number and allow the table to start clean . This will only fix the problem temporarily. Over time, the changed asset deploys will again start deploying files that it thinks are referenced, just like it does now.
|
|
|
|
MCLG: Deploy gives "The deployment process failed For input string: "test,37"
|
8. The workaround is to do a Full deploy which will clear out the changed asset deploy queue. One bad thing about this error is the user may decide to delete the folder causing the problem and even empty the recycle bin but the changed asset deploy will still complain about it until a full deploy is done and cleans out the changed asset deploy queue. The number 37 in the error is the assetid of the parent folder where this folder with a comma lives.
|
|
|
|
MCLG: MEx: Migration Express Supplemental
|
Examine the entire site carefully, and look for anything that may need to be cleaned up. Section 3.0 of the readme lists some known issues to look for.
|
|
|
Serena® Collage® Version 5.1.3 Release Notes
|
2.8 Deployment DEF72571: Deployment performance is poor until the /cmsessions folder is cleaned up. Collage needs to clean up this folder in order to improve deployment performance.
|
|
|
Introduction to Serena Collage
|
This hides them from your view in your Inbox. For example, if you have 20 notifications in your Inbox for a specific task, you can clean up your Inbox by marking each of the notifications as read, as you finish reviewing them. The notifications that you have marked as read are no longer visible from your Inbox.
|
|
|
|
Serena Collage Project Manager's Guide
|
On the Collage Server for each custom root, after the root is transferred to a temporary location in the server directory. You can use this to run a clean -up command on the directory, after Collage has retrieved files from it.
|
|
|
