Subversion Repositories DevTools

Rev

Show changed files | Details | Compare with Previous | Blame | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
6663 2673 d 20 h dpurdie /ManagerSuite/Deployment_Manager/trunk/web/ Added version Number to resources. Bump the version number when DM is released to overcome caching issues  
5958 3414 d 15 h dpurdie /ManagerSuite/Deployment_Manager/trunk/web/ [JATS-397] Fixing resource leaks  
5513 3617 d 15 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Reorganized the directory structure  
5355 3679 d 15 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Add FavIcon support. With configuration via global.asa
Made page footer format the same as the rest of the Manager Suite		  
5337 3686 d 14 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Detect empty array of states when determining available states for display / warning  
4534 4102 d 17 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ [JATS-303] Fix issues associated with having multiple 'BOM CREATOR's allocated to a project  
13 6719 d 11 h rsolanki /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
SBOM Difference Report

XML Bom Generation Path Modified


DEVI-021016: Need deployment manager support for managing what patch goes to which node
Stephen,
As per your suggestions, I have written 2 scripts to support this. One has been implemented in the Deployment Manager GUI.
The other can be run from the server to extract data required by you for the patches without the HTML contents.
(For example, run_patch.asp?project=SYDNEY (SYD)&release=SITS Legacy&sbom=1.4.2&node=Central System Off-line Server(OFS)&OS=Solaris))

Regards,
Rupesh


<b>Release Date:</b> 31-Jan-2006