Subversion Repositories DevTools

Rev

Show changed files | Directory listing | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
6663 2673 d 21 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 17 h dpurdie /ManagerSuite/Deployment_Manager/trunk/web/ [JATS-397] Fixing resource leaks  
5836 3457 d 22 h dpurdie /ManagerSuite/Deployment_Manager/trunk/web/ [JATS-48] Application code in production database. Removed use of some database tables that provided code.  
5513 3617 d 17 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Reorganized the directory structure  
5355 3679 d 17 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
 
4807 3981 d 14 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Modified handling of uploaded PDF files
They are now stored in the database in a BLOB
Previously stored on the web server disk
 
4217 4246 d 17 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Correct issues related to updating user details  
23 6719 d 12 h rsolanki /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
<b>BOM Difference Report</b>
This has been amended for the following reasons:
- fix some human errors that were present.
- include VTSUP database issues.
- include dependencies changed comments and fixed issues between the 2 versions of a product in a BOM.

<b>AutoProducts View Added</b>
Packages/Products from AutoProducts view from Release Manager would now be available for the user.

<b>Hide/UnHide Products/Patches</b>
This functionality has now been added to hide products/patches from a given node when you select the "Update Products" button from the menu. You can also unhide them by selecting the "Unhide Products" button.

<b>BOM Release Manager Reference</b>
The option to select the Release Manager Reference when creating a new BOM has been added.

<b>Node Versions</b>
Node Versions would now be updated depending on the changes in the BOM compared to the previous one when XML BOM generation is clicked.

<b>Obsolete Patches</b>
Bulk obsolete patches in a platform in a given node can now be removed in one go by selecting the obsolete icon.

<b>Upgrading Products with Patches in a Platform</b>
Deployment Manager had a slight issue where it would enable you to update/edit a package version even though patches related to that version existed. For example, ERGoracs 25.2.0000.syd had a number of patches in a given OS in a given node. Previously, you could then upgrade that package from 25.2.0000.syd to 25.2.1000.syd because of XYZ. That would mean that patches related to the previous version would still exist in the BOM.

To resolve this issue, I have put a routine check where if the patches that are related to a given package version exist then the buttons for editing would not be displayed


<b>Release Date:</b> 19-July-2006
 
13 6719 d 13 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