| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 5374 |
3675 d 12 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/common/ |
Move Jira Credentials out of source code and into global.asa |
|
| 5371 |
3675 d 20 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/ |
|
|
| 5355 |
3680 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 |
3687 d 14 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/ |
Detect empty array of states when determining available states for display / warning |
|
| 4807 |
3982 d 12 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 |
|
| 4554 |
4093 d 15 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/ |
The DEVI sections of the ClearQuest Database have been copied into the Release Manager Database and the Manager Suite codebase has been modified to use the local tables. |
|
| 4256 |
4233 d 20 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/ |
Moved to the JIRA Rest API as this is expected to be stable. |
|
| 3947 |
4515 d 20 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 |
4527 d 17 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 |
4881 d 19 h |
dpurdie |
/ManagerSuite/Deployment_Manager/trunk/ |
Jira Database and webserver migrated to the cloud |
|
| 43 |
5010 d 6 h |
brianf |
/ManagerSuite/Deployment_Manager/trunk/ |
DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
DEVI-070968 |
|
| 37 |
5180 d 4 h |
brianf |
/ManagerSuite/Deployment_Manager/trunk/ |
DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
DEVI-068922 |
|
| 35 |
5955 d 6 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) |
|
| 31 |
6301 d 13 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 |
6398 d 6 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. |
|
| 23 |
6720 d 10 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 |
|
| 21 |
6720 d 10 h |
rsolanki |
/ManagerSuite/Deployment_Manager/trunk/ |
DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
There are changes in Release Manager and Deployment Manager so that the generation of node spec files is automated and the business
processes involved made efficient and less time-consuming. This involves the introduction of a mechanism that would enable users to add/import
processes to package versions in Release Manager and to the platforms in a given node in a BOM (Bills Of Materials) in Deployment Manager.
In general, the mechanism can be described in the following steps:
1. Insert processes/instances of processes in a given package version in Release Manager.
2. Import the processes/instances of processes to the platforms in a given node in Deployment Manager.
3. Generate the NodeSpecFiles from Deployment Manager to be used.
<b>Release Date:</b> 19-May-2006 |
|
| 17 |
6720 d 10 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 |
|
| 15 |
6720 d 10 h |
rsolanki |
/ManagerSuite/Deployment_Manager/trunk/ |
DevTools/ManagerSuite/Deployment_Manager: Checkin by Svn Import
<b>New Functionality Under Additional Tools</b>
The functionality to merge and diff two given SBOMs have now been split into two so that the user can get more detailed information regarding the differences between the SBOMs.
The SBOM Merge Manager would display the changes as per node, operating systems applied to the node and the product versions existing.
The SBOM Version Difference Report would display the changes as per the product versions existing in the SBOMs.
<b>History Tab</b>
History tabs have been added to most of the sections in Deployment Manager so as to track and record the action logs of Deployment Manager users.
<b>NOT_XML functionality</b>
Each operating system would now have an option whether to display or not to display in the XMLs generated for CFengines.
<b>Is_Interface Edit Option</b>
There is now support to edit the "is_interface" value for given processes.
<b>Support for Windows E-name</b>
Package names would now support both SunOS and WIN electronic names for CFengines.
<b>Products In the Node Spec File</b>
Deployment Manager can now support the ability to add several products in the node spec file.
<b>Bom Difference Report</b>
The difference report that gets emailed as per the user's request has been modified so that now it would be able to display the product/package versions that exist between the two versions employed in the BOMs.
<b>XML files for CFEngines</b>
The XML files being generated for CFengines would now be zipped and emailed to the user instead of having Deployment Manager displaying the path to access the files previously.
<b>Release Date:</b> 13-Mar-2006 |
|
| 13 |
6720 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 |
|