Bundles DB Structure

All tables belonging to this app starts with “AO_102D86_” prefix.

 

AO_102D86_BUNDLE: This table stores all bundle definitions and is linked to PROJECT table with PROJECT_ID column. PROJECT_KEY on this table is always empty and not used anymore.

AO_102D86_BUNDLE_CONTENT: This table stores component version pairs of a bundle. Connected to the AO_102D86_BUNDLE table with BUNDLE_ID column. It is also connected to COMPONENT table with COMPONENT_ID column and PROJECTVERSION table with VERSION_ID column.

 

Each bundle has multiple bundle_content entities. The following query returns all component and version pairs inside a bundle with a given name:

1 2 3 4 select distinct AO_102D86_BUNDLE_CONTENT.COMPONENT_ID, AO_102D86_BUNDLE_CONTENT.VERSION_ID from AO_102D86_BUNDLE_CONTENT join AO_102D86_BUNDLE on AO_102D86_BUNDLE_CONTENT.BUNDLE_ID = AO_102D86_BUNDLE.ID where BUNDLE_NAME = 'SSM Release 1'

 

To find issues affected by a bundle or fixed in a bundle you also need to use JIRAISSUE and NODEASSOCIATION tables of Jira together with AO_102D86_BUNDLE_CONTENT table. This article perfectly explains the relationship between versions and the Jira issue and between components and the Jira issue.