# WikiData

PageData:
==Table of Contents
[[TOC]]
== Introduction
This wiki is designed to document the Release Manager internal operation.
== Development Notes
>*[[Wiki Operation Notes]]
>*[[Lessons Learnt]]
>*[Development Notes=DevelopmentNotes]
>>*[[Database Field Values]] and Fields
== Code snippets
>* [[Package Version Sort in SQL]]

PrevPageData:
@@@@@@@@@@@@@@@@8/12/2016 3:30:30 PM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Introduction
This wiki is designed to document the Release Manager internal operation.
== Development Notes
>*[[Wiki Operation Notes]]
>*[[Lessons Learnt]]
>*[Development Notes=DevelopmentNotes]
>>*[[Database Field Values]] and Fields

@@@@@@@@@@@@@@@@21/09/2012 5:44:06 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Introduction
This wiki is designed to document the Release Manager internal operation.
== Development Notes
>*[[Wiki Operation Notes]]
>*[Development Notes=DevelopmentNotes]
>>*[[Database Field Values]] and Fields

@@@@@@@@@@@@@@@@9/21/2012 4:09:48 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Introduction
This wiki is designed to document the Release Manager internal operation.
== Development Notes
 * [[Wiki Operation Notes]]
 * [Development Notes=DevelopmentNotes]
== Pages
Values for various (important) [[Database Field Values]] and Fields

@@@@@@@@@@@@@@@@9/21/2012 4:08:59 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Introduction
This wiki is designed to document the Release Manager internal operation.
== Development Notes
[[Development Notes=DevelopmentNotes]]
== Pages
Values for various (important) [[Database Field Values]] and Fields

@@@@@@@@@@@@@@@@9/21/2012 3:54:37 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Introduction
This wiki is designed to document the Release Manager internal operation.
== Development Notes
Development Notes
== Pages
Values for various (important) [[Database Field Values]] and Fields

@@@@@@@@@@@@@@@@9/21/2012 3:53:44 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Introduction
This wiki is designed to document the Release Manager internal operation.
== [[DevelopmentNotes]]
== Pages
Values for various (important) [[Database Field Values]] and Fields


@@@@@@@@@@@@@@@@9/21/2012 3:40:13 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Introduction
This wiki is designed to document the Release Manager internal operation.
== Pages
Values for various (important) [[Database Field Values]] and Fields


@@@@@@@@@@@@@@@@9/21/2012 3:11:31 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Introduction
This wiki is designed to document the Release Manager internal operation.
== Pages
[[Database Field Values]]


@@@@@@@@@@@@@@@@9/21/2012 3:10:09 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Introduction
== Pages


PageData:
==Table of Contents
[[TOC]]
== RTAGS RELEASE_TAGS.OFFICIAL
||DataBase||Mode Code||Name||Description
||N||1||Open Mode||Developers can perform most operations
||R||2||Restricted Mode||Some operations restricted
||C||4||CCB Mode||Package Release only by selected users 
||Y||3||Closed Mode|| Content retained in Package Archive
||O||-||Old Closed Mode|| Closed for more than 60 days - not stored in database. Calculated and used internally.
||P||5||Preserved Mode|| Content retained in Package Archive
||A||6||Archive Mode|| Content can be removed from Package Archive{br}Release not considered a part of Blat Project wildcard
||S||7||SnapShot|| The release is a snapshot of a release. It should never be modified.
== DLOCKED
||N||Unlocked
||Y||Released and Locked
||P||Pending Approval
||A||Aproved. Ready for Autobuild
||R||Rejected
== PKG_STATE
Not sure that this is actually stored in the Release_Content table

||0|| OK
||1||Major
||2||Minor
||3||Major Ready
||4||Minor Ready
||5||New Patch
||6||Deprecated *
||7||Deprecated Dependent *
||8||Advisory Ripple
||9||Ripple Dependent
||10||Pegged Version
||11||Imported Via SDK *
||12||Not Found, but a dependency of an SDK *
||13||UnBuildable Package *
||14||Scheduled to build *
||15||Actively Building *
||16||Excluded from Build (root package) *
||17||Excluded from Build (indirectly) *
||-1||Not Found *
(*) indicates that the value is not stored in the database. It may be jammed into the field in-memory
== Build_Type
||M||Manual
||A||Auto
||Y||Ripple
||U||UnBuildable - Spontaneously generated package
== Ripple_Field
||M||Major
||m||Minor
||p||Patch
||b||Build Number
||z||Do Not Ripple
== Change_type
||M||Major
||N||Minor
||P||Patch
||F||Fixed. Version number manually allocated
== Release Mode
Used in Official column of the Release Tags label
||N||Open
||R||Restricted
||C||CCB
||Y||Closed
||A||Archived
== Operation (Planned/Pending) PLANNED.OPERATION
||A||Add Existing Version
||S||Subtract existing version
||R||Add New Version
== Test Type Id. UNIT_TESTS.TEST_TYPES_FK
||1||Note Done
||2||Coverage
||3||Performance
||4||Memory
||5||Auto Unit Test
||6||Interactive Unit Test
||7||Autobuild UTF
== CQ Issues Database
||1||MASSI||Unknown
||2||DPGIM||Unknown
||3||TDSE|| Sydney Development
||4||DEVI||Main ClearQuest Issues database
||5||VT5DM||VTK Issues
||6||JIRA||Not actually used in the code
||7||VTSUP||More VTK Issues
The interface to ClearQuest is slowly being removed from the Manager Suite. Part of the problem is that the queries are structured such that if any of the databases are not available then the entire query will fail.
== CQ Issues State iss_state
||enumISSUES_STATE_IMPORTED||0||
||enumISSUES_STATE_FIXED|| 1||
== Release Note Info
||NULL|| || Triggers Release Note Generation
||MSG:1||Generating||Set when Release Notes Generation starts
||MSG:2||Not Found||Triggers Release Note Generation
||MSG:3||Failed||Set when Release Note Generation fails
||MSG:4||No Previous Version||Used in the creation of Release Notes
||MSG:5||Place Holder Package||Release Notes not generated. Manually built package, no Build Env and Not in dpkg_archive
== Build RUN_LEVEL.CURRENT_RUN_LEVEL
Set the by the Build Tool
||1||CANNOT_CONTINUE||Set if insufficient disk space or read-only file system
||2||PAUSED||Directed to pause by user, or scheduled downtime
||3||ACTIVE||Master:Notify all daemons that there is a build Job.
||4||IDLE||Master: Will poll database within 60 seconds. Slave: Transitional State before WAITING
||5||WAITING||Master: Waiting for slaves. Slave: Waiting for a job.
||6||PUBLISHING||Master Only: All daemons have built the software. Master is working: Check dpkg_archive,  Save Build files, Teardown Workspace, Update RM Database with VCS Tag and Dependencies, Release Package, Insert Package Metrics, send build-complete Email

== Env Area
Used in the ENVIRONMENT_VIEW, and else where
|| 0 || Is a WIP
|| 1 || Is Planned
|| 2 || Is a part of the Release

PrevPageData:
@@@@@@@@@@@@@@@@29/04/2019 10:19:52 AM : 10.240.1.125@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== RTAGS RELEASE_TAGS.OFFICIAL
||DataBase||Mode Code||Name||Description
||N||1||Open Mode||Developers can perform most operations
||R||2||Restricted Mode||Some operations restricted
||C||4||CCB Mode||Package Release only by selected users 
||Y||3||Closed Mode|| Content retained in Package Archive
||O||-||Old Closed Mode|| Closed for more than 60 days - not stored in database. Calculated and used internally.
||P||5||Preserved Mode|| Content retained in Package Archive
||A||6||Archive Mode|| Content can be removed from Package Archive{br}Release not considered a part of Blat Project wildcard
== DLOCKED
||N||Unlocked
||Y||Released and Locked
||P||Pending Approval
||A||Aproved. Ready for Autobuild
||R||Rejected
== PKG_STATE
Not sure that this is actually stored in the Release_Content table

||0|| OK
||1||Major
||2||Minor
||3||Major Ready
||4||Minor Ready
||5||New Patch
||6||Deprecated *
||7||Deprecated Dependent *
||8||Advisory Ripple
||9||Ripple Dependent
||10||Pegged Version
||11||Imported Via SDK *
||12||Not Found, but a dependency of an SDK *
||13||UnBuildable Package *
||14||Scheduled to build *
||15||Actively Building *
||16||Excluded from Build (root package) *
||17||Excluded from Build (indirectly) *
||-1||Not Found *
(*) indicates that the value is not stored in the database. It may be jammed into the field in-memory
== Build_Type
||M||Manual
||A||Auto
||Y||Ripple
||U||UnBuildable - Spontaneously generated package
== Ripple_Field
||M||Major
||m||Minor
||p||Patch
||b||Build Number
||z||Do Not Ripple
== Change_type
||M||Major
||N||Minor
||P||Patch
||F||Fixed. Version number manually allocated
== Release Mode
Used in Official column of the Release Tags label
||N||Open
||R||Restricted
||C||CCB
||Y||Closed
||A||Archived
== Operation (Planned/Pending) PLANNED.OPERATION
||A||Add Existing Version
||S||Subtract existing version
||R||Add New Version
== Test Type Id. UNIT_TESTS.TEST_TYPES_FK
||1||Note Done
||2||Coverage
||3||Performance
||4||Memory
||5||Auto Unit Test
||6||Interactive Unit Test
||7||Autobuild UTF
== CQ Issues Database
||1||MASSI||Unknown
||2||DPGIM||Unknown
||3||TDSE|| Sydney Development
||4||DEVI||Main ClearQuest Issues database
||5||VT5DM||VTK Issues
||6||JIRA||Not actually used in the code
||7||VTSUP||More VTK Issues
The interface to ClearQuest is slowly being removed from the Manager Suite. Part of the problem is that the queries are structured such that if any of the databases are not available then the entire query will fail.
== CQ Issues State iss_state
||enumISSUES_STATE_IMPORTED||0||
||enumISSUES_STATE_FIXED|| 1||
== Release Note Info
||NULL|| || Triggers Release Note Generation
||MSG:1||Generating||Set when Release Notes Generation starts
||MSG:2||Not Found||Triggers Release Note Generation
||MSG:3||Failed||Set when Release Note Generation fails
||MSG:4||No Previous Version||Used in the creation of Release Notes
||MSG:5||Place Holder Package||Release Notes not generated. Manually built package, no Build Env and Not in dpkg_archive
== Build RUN_LEVEL.CURRENT_RUN_LEVEL
Set the by the Build Tool
||1||CANNOT_CONTINUE||Set if insufficient disk space or read-only file system
||2||PAUSED||Directed to pause by user, or scheduled downtime
||3||ACTIVE||Master:Notify all daemons that there is a build Job.
||4||IDLE||Master: Will poll database within 60 seconds. Slave: Transitional State before WAITING
||5||WAITING||Master: Waiting for slaves. Slave: Waiting for a job.
||6||PUBLISHING||Master Only: All daemons have built the software. Master is working: Check dpkg_archive,  Save Build files, Teardown Workspace, Update RM Database with VCS Tag and Dependencies, Release Package, Insert Package Metrics, send build-complete Email

== Env Area
Used in the ENVIRONMENT_VIEW, and else where
|| 0 || Is a WIP
|| 1 || Is Planned
|| 2 || Is a part of the Release


@@@@@@@@@@@@@@@@28/04/2019 5:41:03 PM : 10.240.1.125@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== RTAGS RELEASE_TAGS.OFFICIAL
||DataBase||Mode Code||Name||Description
||N||1||Open Mode||Developers can perform most operations
||R||2||Restricted Mode||Some operations restricted
||C||4||CCB Mode||Package Release only by selected users 
||Y||3||Closed Mode|| Content retained in Package Archive
||O||-||Old Closed Mode|| Closed for more than 60 days - not stored in database. Calculated and used internally.
||P||5||Preserved Mode|| Content retained in Package Archive
||A||6||Archive Mode|| Content can be removed from Package Archive{br}Release not considered a part of Blat Project wildcard
== DLOCKED
||N||Unlocked
||Y||Released and Locked
||P||Pending Approval
||A||Aproved. Ready for Autobuild
||R||Rejected
== PKG_STATE
Not sure that this is actually stored in the Release_Content table

||0|| OK
||1||Major
||2||Minor
||3||Major Ready
||4||Minor Ready
||5||New Patch
||6||Deprecated *
||7||Deprecated Dependent *
||8||Advisory Ripple
||9||Ripple Dependent
||10||Pegged Version
||11||Imported Via SDK *
||12||Not Found, but a dependency of an SDK *
||13||UnBuildable Package *
||14||Scheduled to build *
||15||Excluded from Build (root package) *
||16||Actively Building *
||-1||Not Found *
(*) indicates that the value is not stored in the database. It may be jammed into the field in-memory
== Build_Type
||M||Manual
||A||Auto
||Y||Ripple
||U||UnBuildable - Spontaneously generated package
== Ripple_Field
||M||Major
||m||Minor
||p||Patch
||b||Build Number
||z||Do Not Ripple
== Change_type
||M||Major
||N||Minor
||P||Patch
||F||Fixed. Version number manually allocated
== Release Mode
Used in Official column of the Release Tags label
||N||Open
||R||Restricted
||C||CCB
||Y||Closed
||A||Archived
== Operation (Planned/Pending) PLANNED.OPERATION
||A||Add Existing Version
||S||Subtract existing version
||R||Add New Version
== Test Type Id. UNIT_TESTS.TEST_TYPES_FK
||1||Note Done
||2||Coverage
||3||Performance
||4||Memory
||5||Auto Unit Test
||6||Interactive Unit Test
||7||Autobuild UTF
== CQ Issues Database
||1||MASSI||Unknown
||2||DPGIM||Unknown
||3||TDSE|| Sydney Development
||4||DEVI||Main ClearQuest Issues database
||5||VT5DM||VTK Issues
||6||JIRA||Not actually used in the code
||7||VTSUP||More VTK Issues
The interface to ClearQuest is slowly being removed from the Manager Suite. Part of the problem is that the queries are structured such that if any of the databases are not available then the entire query will fail.
== CQ Issues State iss_state
||enumISSUES_STATE_IMPORTED||0||
||enumISSUES_STATE_FIXED|| 1||
== Release Note Info
||NULL|| || Triggers Release Note Generation
||MSG:1||Generating||Set when Release Notes Generation starts
||MSG:2||Not Found||Triggers Release Note Generation
||MSG:3||Failed||Set when Release Note Generation fails
||MSG:4||No Previous Version||Used in the creation of Release Notes
||MSG:5||Place Holder Package||Release Notes not generated. Manually built package, no Build Env and Not in dpkg_archive
== Build RUN_LEVEL.CURRENT_RUN_LEVEL
Set the by the Build Tool
||1||CANNOT_CONTINUE||Set if insufficient disk space or read-only file system
||2||PAUSED||Directed to pause by user, or scheduled downtime
||3||ACTIVE||Master:Notify all daemons that there is a build Job.
||4||IDLE||Master: Will poll database within 60 seconds. Slave: Transitional State before WAITING
||5||WAITING||Master: Waiting for slaves. Slave: Waiting for a job.
||6||PUBLISHING||Master Only: All daemons have built the software. Master is working: Check dpkg_archive,  Save Build files, Teardown Workspace, Update RM Database with VCS Tag and Dependencies, Release Package, Insert Package Metrics, send build-complete Email

== Env Area
Used in the ENVIRONMENT_VIEW, and else where
|| 0 || Is a WIP
|| 1 || Is Planned
|| 2 || Is a part of the Release


@@@@@@@@@@@@@@@@15/08/2016 10:14:33 AM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== RTAGS RELEASE_TAGS.OFFICIAL
||DataBase||Mode Code||Name||Description
||N||1||Open Mode||Developers can perform most operations
||R||2||Restricted Mode||Some operations restricted
||C||4||CCB Mode||Package Release only by selected users 
||Y||3||Closed Mode|| Content retained in Package Archive
||O||-||Old Closed Mode|| Closed for more than 60 days - not stored in database. Calculated and used internally.
||P||5||Preserved Mode|| Content retained in Package Archive
||A||6||Archive Mode|| Content can be removed from Package Archive{br}Release not considered a part of Blat Project wildcard
== DLOCKED
||N||Unlocked
||Y||Released and Locked
||P||Pending Approval
||A||Aproved. Ready for Autobuild
||R||Rejected
== PKG_STATE
Not sure that this is actually stored in the Release_Content table

||0|| OK
||1||Major
||2||Minor
||3||Major Ready
||4||Minor Ready
||5||New Patch
||6||Deprecated *
||7||Deprecated Dependent *
||8||Advisory Ripple
||9||Ripple Dependent
||10||Pegged Version
||11||Imported Via SDK *
||12||Not Found, but a dependency of an SDK *
||13||UnBuildable Package *
||-1||Not Found *
(*) indicates that the value is not stored in the database. It may be jammed into the field in-memory
== Build_Type
||M||Manual
||A||Auto
||Y||Ripple
||U||UnBuildable - Spontaneously generated package
== Ripple_Field
||M||Major
||m||Minor
||p||Patch
||b||Build Number
||z||Do Not Ripple
== Change_type
||M||Major
||N||Minor
||P||Patch
||F||Fixed. Version number manually allocated
== Release Mode
Used in Official column of the Release Tags label
||N||Open
||R||Restricted
||C||CCB
||Y||Closed
||A||Archived
== Operation (Planned/Pending) PLANNED.OPERATION
||A||Add Existing Version
||S||Subtract existing version
||R||Add New Version
== Test Type Id. UNIT_TESTS.TEST_TYPES_FK
||1||Note Done
||2||Coverage
||3||Performance
||4||Memory
||5||Auto Unit Test
||6||Interactive Unit Test
||7||Autobuild UTF
== CQ Issues Database
||1||MASSI||Unknown
||2||DPGIM||Unknown
||3||TDSE|| Sydney Development
||4||DEVI||Main ClearQuest Issues database
||5||VT5DM||VTK Issues
||6||JIRA||Not actually used in the code
||7||VTSUP||More VTK Issues
The interface to ClearQuest is slowly being removed from the Manager Suite. Part of the problem is that the queries are structured such that if any of the databases are not available then the entire query will fail.
== CQ Issues State iss_state
||enumISSUES_STATE_IMPORTED||0||
||enumISSUES_STATE_FIXED|| 1||
== Release Note Info
||NULL|| || Triggers Release Note Generation
||MSG:1||Generating||Set when Release Notes Generation starts
||MSG:2||Not Found||Triggers Release Note Generation
||MSG:3||Failed||Set when Release Note Generation fails
||MSG:4||No Previous Version||Used in the creation of Release Notes
||MSG:5||Place Holder Package||Release Notes not generated. Manually built package, no Build Env and Not in dpkg_archive
== Build RUN_LEVEL.CURRENT_RUN_LEVEL
Set the by the Build Tool
||1||CANNOT_CONTINUE||Set if insufficient disk space or read-only file system
||2||PAUSED||Directed to pause by user, or scheduled downtime
||3||ACTIVE||Master:Notify all daemons that there is a build Job.
||4||IDLE||Master: Will poll database within 60 seconds. Slave: Transitional State before WAITING
||5||WAITING||Master: Waiting for slaves. Slave: Waiting for a job.
||6||PUBLISHING||Master Only: All daemons have built the software. Master is working: Check dpkg_archive,  Save Build files, Teardown Workspace, Update RM Database with VCS Tag and Dependencies, Release Package, Insert Package Metrics, send build-complete Email

== Env Area
Used in the ENVIRONMENT_VIEW, and else where
|| 0 || Is a WIP
|| 1 || Is Planned
|| 2 || Is a part of the Release


@@@@@@@@@@@@@@@@21/07/2016 11:35:22 AM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== RTAGS RELEASE_TAGS.OFFICIAL
||DataBase||Mode Code||Name||Description
||N||1||Open Mode||Developers can perform most operations
||R||2||Restricted Mode||Some operations restricted
||C||4||CCB Mode||Package Release only by selected users 
||Y||3||Closed Mode|| Content retained in Package Archive
||O||-||Old Closed Mode|| Closed for more than 60 days - not stored in database. Calculated and used internally.
||P||5||Preserved Mode|| Content retained in Package Archive
||A||6||Archive Mode|| Content can be removed from Package Archive{br}Release not considered a part of Blat Project wildcard
== DLOCKED
||N||Unlocked
||Y||Released and Locked
||P||Pending Approval
||A||Aproved. Ready for Autobuild
||R||Rejected
== PKG_STATE
Not sure that this is actually stored in the Release_Content table

||0|| OK
||1||Major
||2||Minor
||3||Major Ready
||4||Minor Ready
||5||New Patch
||6||Deprecated *
||7||Deprecated Dependent *
||8||Advisory Ripple
||9||Ripple Dependent
||10||Pegged Version
||11||Imported Via SDK *
||12||Not Found, but a dependency of an SDK *
||13||UnBuildable Package *
||-1||Not Found *
(*) indicates that the value is not stored in the database. It may be jammed into the field in-memory
== Build_Type
||M||Manual
||A||Auto
||Y||Ripple
||U||UnBuildable - Spontaneously generated package
== Ripple_Field
||M||Major
||m||Minor
||p||Patch
||b||Build Number
||z||Do Not Ripple
== Change_type
||M||Major
||N||Minor
||P||Patch
||F||Fixed. Version number manually allocated
== Release Mode
Used in Official column of the Release Tags label
||N||Open
||R||Restricted
||C||CCB
||Y||Closed
||A||Archived
== Operation (Planned/Pending) PLANNED.OPERATION
||A||Add Existing Version
||S||Subtract existing version
||R||Add New Version
== Test Type Id. UNIT_TESTS.TEST_TYPES_FK
||1||Note Done
||2||Coverage
||3||Performance
||4||Memory
||5||Auto Unit Test
||6||Interactive Unit Test
||7||Autobuild UTF
== CQ Issues Database
||1||MASSI||Unknown
||2||DPGIM||Unknown
||3||TDSE|| Sydney Development
||4||DEVI||Main ClearQuest Issues database
||5||VT5DM||VTK Issues
||6||JIRA||Not actually used in the code
||7||VTSUP||More VTK Issues
The interface to ClearQuest is slowly being removed from the Manager Suite. Part of the problem is that the queries are structured such that if any of the databases are not available then the entire query will fail.
== CQ Issues State iss_state
||enumISSUES_STATE_IMPORTED||0||
||enumISSUES_STATE_FIXED|| 1||
== Release Note Info
||NULL|| || Triggers Release Note Generation
||MSG:1||Generating||Set when Release Notes Generation starts
||MSG:2||Not Found||Triggers Release Note Generation
||MSG:3||Failed||Se


PageData:
==Table of Contents
[[TOC]]
== Introduction
This page contains notes on the creation and maintenance of the Release Note Wiki used within Release Manager. 

== Background
This Wiki is based on [WikiAsp|http://lambda.vze.com/].
It has been heavily modified.
=== Why
For a long while the Release Manager release notes where held in an ERG Wiki. This was in the process of being deprecated. Many pages where being transferred to  the newer VIX Wiki running on GoogleSites. The format was not compatible and it seems wrong to have Release Manager requiring two servers. The solution was to have the Release Manager server also serve out the Release Notes. WikiAsp was a simple solution.
=== Future
There is hope that the Wiki can also be used to provide training and documentation on the Release Manager itself.

== Editing
Pages can only be edited on the Test/Development System. They cannot be edited on the Live Release Manager instance. This is intentional:
 * The Wiki Database is then version controlled with Release Manager
 * Prevents users from editing the Release Notes
When the Wiki is run on a Test/Development system the user will get extra menu items at the top of the page and a panel at the bottom of the page. These are not normally seen.

== Text Formatting Rules
See [ReleaseNotes::TextFormattingRules] for details on the Wiki Format.


PageData:
==Table of Contents
[[TOC]]
== Creating a new Database
Method 1
 * Create a reference to the new database via an 'InterWiki Link'
 * This will fail and you will be prompted to create a new database.
Method 2
 * Fudge the URL with the name of the required database
 * This will fail and you will be prompted to create a new database.
Method 3
 * Enable Editing
 * Select the 'Config' item. It contains a facility to create a new Wiki Database
== Bulk Page Delete
This can only be enabled via the 'Config' Menu. It will remain active for the remainder of the editing session.

When enabled any of the page table displays will have an additional column to allow the deletion of the page. The deletion will not be questioned.

PrevPageData:
@@@@@@@@@@@@@@@@9/26/2013 10:28:59 AM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Creating a new Database
Method 1
 * Create a reference to the new database via an 'InterWiki Link'
 * This will fail and you will be prompted to create a new database.
Method 2
 * Fudge the URL with the name of the required database
 * This will fail and you will be prompted to create a new database.
== Bulk Page Delete
This can only be enabled within the Wiki Code. Look for gBulkDelete.

When enabled any of the page table displays will have an additional column to allow the deletion of the page. The deletion will not be questioned.

@@@@@@@@@@@@@@@@9/26/2013 10:26:07 AM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Creating a new Database
Method 1
 * Create a reference to the new database via an 'InterWiki Link'
 * This will fail and you will be prompted to create a new database.
Method 2
 * Fudge the URL with the name of the required database
 * This will fail and you will be prompted to create a new database.

@@@@@@@@@@@@@@@@9/26/2013 9:54:13 AM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Creating a new Database
 * Create a referenece to the new database via an 'InterWiki Link'
 * This will fail. Then add "&pw=pass" - to the URL

@@@@@@@@@@@@@@@@9/21/2012 4:16:38 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Deleting a page
 * Select the page
 * Append the following to the URL : &a=del&pw=passworddel 
== Creating a new Database
 * Create a referenece to the new database via an 'InterWiki Link'
 * This will fail. Then add "&pw=pass" - to the URL

@@@@@@@@@@@@@@@@9/21/2012 4:12:11 PM : 10.240.2.79@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]
== Deleting a page
 * Select the page
 * Append the following to the URL : &a=del&pw=passworddel 
== Creating a new Database
 * Create a ferenece to the new database via an 'InterWiki Link'
 * This will fail. Then add pw=pass - to the URL


PageData:
==Table of Contents
[[TOC]]

Some notes on what to do and not to do.

== Oracle Session Leakage
Oracle will leak sessions unless ALL bound variables are unbound at the end of the page rendering.
Sounds simple enough - except for error handling.

All pages that include globals.asp MUST also:
 * Include destructor.asp
 * OR Include _footer.asp
 * OR Call Destroy_All_Objects

Any call that terminates page rendering MUST Call Destroy_All_Objects first. This includes:
 * Response.End
 * Response.Redirect
 * Err.Raise

== Oracle, and other, Error Handling. Try, Catch, Finally
Someone wrote some nice code called objEH.TryORA and objEH.CatchORA and objEH.Finally.
There is also a objEH.Try and objEH.Catch and objEH.Finally, for use when not expecting oracle errors.

Catches:
 * The biggest catch is that 'On Error Resume Next' MUST be in play before an Oracle operation that may generate an error is processed. If 'On Error Resume Next' is not in play then ASP will stop and throw the error to the callee. There will be no further processing in the routine.
 * objEH.Finally appears to return TRUE if the Catch has not been invoked (almost)
 * objEH.ErrorRedirect = TRUE, will not work as expected IFF any html output has been generated. ASP will hide the message 'The HTTP headers are already written to the client browser. Any HTTP header modifications must be made before writing page content.'

Also

== On Error Resume Next
There are a few notes:
 * It is scoped. If invoked in a Subroutine or Function, then it will not affect the callee. ie: its only in play in the Function.
 * If not invoked in a function/subroutine and an error occurs then the error is passed up to the parent. At the top of the call tree is ASP and ASP will simply print a message and STOP.

PrevPageData:
@@@@@@@@@@@@@@@@8/12/2016 3:53:46 PM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]

Some notes on what to do and not to do.

== Oracle Session Leakage
Oracle will leak sessions unless ALL bound variables are unbound at the end of the page rendering.
Sounds simple enough - except for error handling.

All pages that include globals.asp MUST also:
 * Include destructor.asp
 * OR Include _footer.asp
 * OR Call Destroy_All_Objects

Any call that terminates page rendering MUST Call Destroy_All_Objects first. This includes:
 * Response.End
 * Response.Redirect
 * Err.Raise

== Oracle, and other, Error Handling. Try, Catch, Finally
Someone wrote some nice code called objEH.TryORA and objEH.CatchORA and objEH.Finally.
There is also a objEH.Try and objEH.Catch and objEH.Finally, for use when not expecting oracle errors.

Catches:
 * The biggest catch is that 'On Error Resume Next' MUST be in play before an Oracle operation that may generate an error is processed. If 'On Error Resume Next' is not in play then ASP will stop and throw the error to the callee. There will be no further processing in the routine.
 * objEH.Finally appears to return TRUE if the Catch has not been invoked (almost)

Also

== On Error Resume Next
There are a few notes:
 * It is scoped. If invoked in a Subroutine or Function, then it will not affect the callee. ie: its only in play in the Function.
 * If not invoked in a function/subroutine and an error occurs then the error is passed up to the parent. At the top of the call tree is ASP and ASP will simply print a message and STOP.



@@@@@@@@@@@@@@@@8/12/2016 3:51:25 PM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]

Some notes on what to do and not to do.

== Oracle Session Leakage
Oracle will leak sessions unless ALL bound variables are unbound at the end of the page rendering.
Sounds simple enough - except for error handling.

All pages that include globals.asp MUST also:
 * Include destructor.asp
 * OR Include _footer.asp
 * OR Call Destroy_All_Objects

Any call that terminates page rendering MUST Call Destroy_All_Objects first. This includes:
 * Response.End
 * Response.Redirect
 * Err.Raise

== Oracle, and other, Error Handling. Try, Catch, Finally
Someone wrote some nice code called objEH.TryORA and objEH.CatchORA and objEH.Finally.
There is also a objEH.Try and objEH.Catch and objEH.Finally, for use when not expecting oracle errors.

The biggest catch is that 'On Error Resume Next' MUST be in play before an Oracle operation that may generate an error is processed. If 'On Error Resume Next' is not in play then ASP will stop and there will be no further processing.

== On Error Resume Next
There are a few notes:
 * It is scoped. If invoked in a Subroutine or Function, then it will not affect the callee. ie: its only in play in the Function.
 * If not invoked in a function/subroutine and an error occurs then the error is passed up to the parent. At the top of the call tree is ASP and ASP will simply print a message and STOP.



@@@@@@@@@@@@@@@@8/12/2016 3:42:12 PM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Table of Contents
[[TOC]]

Some notes on what to do and not to do.

== Oracle Session Leakage
Oracle will leak sessions unless ALL bound variables are unbound at the end of the page rendering.
Sounds simple enough - except for error handling.

All pages that include globals.asp MUST also:
 * Include destructor.asp
 * OR Include _footer.asp
 * OR Call Destroy_All_Objects

Any call that terminates page rendering MUST Call Destroy_All_Objects first. This includes:
 * Response.End
 * Response.Redirect
 * Err.Raise

== Oracle Error Handling
Someone wrote some nice code called objEH.TryORA and objEH.CatchORA and objEH.FinallyORA.

The biggest catch is that 'On Error Resume Next' MUST be in play before an Oracle operation that may generate an error is processed. If 'On Error Resume Next' is not in play then ASP will stop and there will be no further processing.

== On Error Resume Next
There are a few notes:
 * It is scoped. If invoked in a Subroutine or Function, then it will not affect the callee. ie: its only in play in the Function.
 * If not invoked in a function/subroutine and an error occurs then the error is passed up to the parent. At the top of the call tree is ASP and ASP will simply print a message and STOP.



@@@@@@@@@@@@@@@@8/12/2016 3:30:44 PM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@


PageData:
An SQL sequence to return all package versions in descending order.
Could be used to replace the use of 'SortHelper'
The SortHelper is written in VBScript. It may be quicker to sort the list on the oracle server

The script needs to handle COTS and TOOL packages
Basically it will extract the major, minor patch and build number(ish) fields
The fun stuff is done in the 'ORDER BY' where we sort by number and text


 SELECT pkg_version,V_NMM,
  REGEXP_SUBSTR(V_NMM, '^[^.]+')      AS major,
  REGEXP_REPLACE(V_NMM, '.*\.(.*)\.\..*','\1') AS minor,
  get_patch_version(V_MM)             AS patch,
  get_build_number(V_MM)              AS build,
  V_EXT
 FROM package_versions
 WHERE pkg_id = :PKG_ID
 ORDER BY 
 TO_NUMBER(REGEXP_SUBSTR(major, '[0-9]+')) desc NULLS LAST, REGEXP_REPLACE(major, '[0-9]', '') desc, 
 TO_NUMBER(REGEXP_SUBSTR(minor, '[0-9]+')) desc NULLS LAST, REGEXP_REPLACE(minor, '[0-9]', '') desc, 
 TO_NUMBER(REGEXP_SUBSTR(patch, '[0-9]+')) desc NULLS LAST, REGEXP_REPLACE(patch, '[0-9]', '') desc, 
 TO_NUMBER(REGEXP_SUBSTR(build, '[0-9]+')) desc NULLS LAST, REGEXP_REPLACE(build, '[0-9]', '') desc, 
 v_ext desc

PrevPageData:
@@@@@@@@@@@@@@@@8/06/2018 1:20:32 PM : 10.240.1.125@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

{{{
SELECT pkg_version,V_NMM,
  REGEXP_SUBSTR(V_NMM, '^[^.]+')      AS major,
  REGEXP_REPLACE(V_NMM, '.*\.(.*)\.\..*','\1') AS minor,
  get_patch_version(V_MM)             AS patch,
  get_build_number(V_MM)              AS build,
  V_EXT
FROM package_versions
WHERE pkg_id = :PKG_ID
ORDER BY 
TO_NUMBER(REGEXP_SUBSTR(major, '[0-9]+')) desc NULLS LAST, REGEXP_REPLACE(major, '[0-9]', '') desc, 
TO_NUMBER(REGEXP_SUBSTR(minor, '[0-9]+')) desc NULLS LAST, REGEXP_REPLACE(minor, '[0-9]', '') desc, 
TO_NUMBER(REGEXP_SUBSTR(patch, '[0-9]+')) desc NULLS LAST, REGEXP_REPLACE(patch, '[0-9]', '') desc, 
TO_NUMBER(REGEXP_SUBSTR(build, '[0-9]+')) desc NULLS LAST, REGEXP_REPLACE(build, '[0-9]', '') desc, 
v_ext desc
}}}


