Subversion Repositories DevTools

Rev

Go to most recent revision | Show changed files | Details | Compare with Previous | Blame | RSS feed

Filtering Options

Rev Age Author Path Log message Diff
4178 4303 d 5 h dpurdie /ManagerSuite/Deployment_Manager/trunk/WikiAsp/db/  
4177 4303 d 5 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Changed the Jira SQL to handle the schema change in Jira 1.6  
4054 4483 d 3 h dpurdie /ManagerSuite/Deployment_Manager/trunk/WikiAsp/ Updated Wiki Engine. All Manager Suite now use the same engine  
4050 4483 d 7 h dpurdie /ManagerSuite/Deployment_Manager/trunk/WikiAsp/ Updated Wiki Engine. All Manager Suite now use the same engine  
4027 4492 d 10 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Integrate branch development back to trunk.
Only one developer so use of a branch is a make-work.		  
4026 4492 d 10 h dpurdie /ManagerSuite/Deployment_Manager/trunk/WikiAsp/db/  
3947 4533 d 10 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.		  
3911 4545 d 7 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Changes to generation of NodeSpec files
1) Email and Web NodeSpec files are now generated via the same code
2) Packages with VIX are treated in the same way as packages with erg_logo.gif
3) All Keys in the NodeSpec file are quoted		  
1333 4899 d 9 h dpurdie /ManagerSuite/Deployment_Manager/trunk/ Jira Database and webserver migrated to the cloud  
43 5027 d 20 h brianf /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
DEVI-070968		  
41 5028 d 23 h brianf /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
DEVI-070966
DEVI-070968		  
39 5163 d 1 h brianf /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
DEVI-069415		  
37 5197 d 18 h brianf /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
DEVI-068922		  
35 5972 d 20 h ghuddy /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
Add an "Update All" button to the Update Products form (wSyncProducts.asp)		  
33 6270 d 22 h ghuddy /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
Remove dependence upon daf_action_buttons table
Remove dependency upon PACKAGE_BUILD_ENV and BUILD_ENVIRONMENTS tables
Make About page auto-maintained		  
31 6319 d 3 h ghuddy /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
DEVI-049920 - JIRA issue reporting on BOM difference report page.		  
29 6415 d 20 h jtweddle /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
* Fixed a bug in BOM comparison that caused products that had been updated to also be shown as having been removed.
* Fixed a bug that caused server error pages when removing an OS from a node, or a product from an OS.		  
27 6738 d 0 h rsolanki /ManagerSuite/Deployment_Manager/trunk/ DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
Added Production Manager Configuration


<b>Release Date:</b> 5-January-2007		  
25 6738 d 0 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 6738 d 0 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		  

←Prev12Next→

Show All