| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 6663 |
2673 d 18 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/web/ |
Added version Number to resources. Bump the version number when DM is released to overcome caching issues |
|
| 5646 |
3548 d 17 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/web/ |
[JATS-60] Sort Feature of Deployment Manager is Broken and Unorders Ordered Products |
|
| 5642 |
3549 d 19 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/web/ |
Added popup menu bar and extended main menu options in line with Release Manager |
|
| 5513 |
3617 d 14 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/ |
Reorganized the directory structure |
|
| 5355 |
3679 d 13 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 |
|
| 3947 |
4514 d 18 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/ |
ClearQuest interactions
Removed use of 4 ,unused and unavailable, ClearQuest databases
Release Notes
Migrated the storage of the Deployment Manager Release Notes from the (deprecated) MASS Wiki into the Deployment Manager tool itself.
Merged several features from Release Manager into Deployment Manager
The use of an internal Wiki Engine
Common header generation on all pages
Common header to highlight use on non-Production machines and databases
Tooltips
Authentication process
Use Authentication domain as provided by Access Manager
No password when used on Development Database
Account Details Pages
These have been enabled. Some changes have been imported from Release Manager. In particular the ability to display details on the users access permissions. |
|
| 25 |
6719 d 9 h |
rsolanki |
/ManagerSuite/Deployment_Manager/trunk/ |
DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
<b>Escrow Report - Paul Blain Request</b>
Added the functionality to generate the escrow report.
<b>BOM Base Configuration Products</b>
Added a new tab that would show the Base Configurations for a given BOM
<b>Find Product In BOM</b>
This has been added under the Tools > Advanced Search section.
<b>BOM NOTE Functionality - George Christidis Request</b>
All BOMs should display the BOM Notes regardless of the state of the BOM.
<b>Release Date:</b> 13-October-2006 |
|
| 23 |
6719 d 9 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 |
|
| 19 |
6719 d 9 h |
rsolanki |
/ManagerSuite/Deployment_Manager/trunk/ |
DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
<b>Support to Add Patch Electronic Name</b>
This functionality has been added to support the generation of patch names in the XML BOMs.
<b>NodeSpec File Generation</b>
The process change in the nodespec files generation is:
1. Emailing of the nodespec files to the user.
2. Generating of the nodespec files under releases in auperaunx26.
(NB: Nodespec filenames should be existing for these to take place)
<b>Message Board Added</b>
Important messages or tasks can be scheduled and posted on the message board.
<b>BOM Diff and Merge Manager re-located</b>
These have been moved under the "Tools" section on the top-right menu bar. This is where useful tools would be placed so as to assist the business process.
<b>All Process Fields Editable</b>
Pkg_health_tag and package/product fields for a process in a given OS in a node can now be changed upon user request.
<b>Release Date:</b> 12-May-2006 |
|
| 17 |
6719 d 9 h |
rsolanki |
/ManagerSuite/Deployment_Manager/trunk/ |
DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
<b>BOM History Report</b>
This tool has been added under the new "Reports" link on the header menu on the home page.
Select the "BOM History Tracker" from the "Bom History" as this is the initial report functionality that has been officially released. This would help users in identifying the Bom, Node, OS changes that occur in an SBOM between certain periods:
<b>Bom Difference Report</b>
The difference report that gets emailed as per the user's request has been extended once again, so that now it would be able to display the patches that have been added to the new BOM selected compared to the old BOM.
<b>Release Date:</b> 04-Apr-2006 |
|
| 13 |
6719 d 9 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 |
|