| Excerpt |
|---|
Planned release: 18.08 2013Released: 2013-08-21. |
Highlights
Updating from 0.27
Databases
Audit trail DB
The information elements have have been changed from varchar(255) to unlimited strings (
| Jira Legacy |
|---|
| server | SBForgeSystem JIRA |
|---|
| serverId | 81c76265-cab2-3ba5-b74d-ee7cd9a2765e |
|---|
| key | BITMAG-646 |
|---|
|
). To update the database do the following:
- Derby: Either just run the audit trail service, which will automatically update the DB, or run the sql/derby/auditTrailServiceDBUpdate2to3.sql script on the DB.
- PostgreSQL: Run the sql/postgres/auditTrailServiceDBUpdate2to3.sql script on the DB.
Audit trail contributor DB
The information elements have have been changed from varchar(255) to unlimited strings (
| Jira Legacy |
|---|
| server | SBForgeSystem JIRA |
|---|
| serverId | 81c76265-cab2-3ba5-b74d-ee7cd9a2765e |
|---|
| key | BITMAG-646 |
|---|
|
). Both the reference pillar and integrity service databases needs to be updated
.To update the database do the following:
- Derby: Either just run the reference pillar and integrity service, which will automatically update the DB, or run the sql/derby/auditContributorDBUpdate2to3.sql script on the DBs.
- PostgreSQL: Run the sql/postgres/auditContributorDBUpdate2to3.sql script on the reference pillar and integrity service DBs.
ReferenceSettings
AuditTrailPreservation
The different settings for AuditTrailPreservation has been moved into a dedicated element, <AuditTrailPreservation>. This element is now optional, eg. if undefined no audit trail preservation will be done (
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 81c76265-cab2-3ba5-b74d-ee7cd9a2765e |
|---|
| key | BITMAG-960 |
|---|
|
).
Old settings:
| Code Block |
|---|
....
<AuditTrailServiceSettings>
....
<AuditTrailPreservationInterval>604800000</AuditTrailPreservationInterval>
<AuditTrailPreservationCollection>TwoPillarCollection</AuditTrailPreservationCollection>
<AuditTrailPreservationTemporaryDirectory>${build.dir}/test/audittrailservice//tmpDir</AuditTrailPreservationTemporaryDirectory>
....
</AuditTrailServiceSettings>
.... |
New settings (optional AuditTrailPreservation section):
| Code Block |
|---|
....
<AuditTrailServiceSettings>
....
<AuditTrailPreservation>
<AuditTrailPreservationInterval>604800000</AuditTrailPreservationInterval>
<AuditTrailPreservationCollection>TwoPillarCollection</AuditTrailPreservationCollection>
<AuditTrailPreservationTemporaryDirectory>${build.dir}/test/audittrailservice//tmpDir</AuditTrailPreservationTemporaryDirectory>
</AuditTrailPreservation>
....
</AuditTrailServiceSettings>
.... |
Integrity reports
As part of the solution to
| Jira Legacy |
|---|
| server | SBForgeSystem JIRA |
|---|
| serverId | 81c76265-cab2-3ba5-b74d-ee7cd9a2765e |
|---|
| key | BITMAG-862 |
|---|
|
a setting defining the integrity report directory has been added to the
IntegrityServiceSettings section. This means the integrity service settings needs to be updated with the new setting:
| Code Block |
|---|
...
<IntegrityServiceSettings>
...
<ObsoleteChecksumSettings/>
<IntegrityReportsDir>${IntegrityReportsDir}</IntegrityReportsDir>
</IntegrityServiceSettings> |