Actions
Bug #5710
closed
User story #5293: Add a 'changes only' compliance mode, only reporting changes on systems
User story #5296: Create the logic to get execution reports for "error only" mode
Rudder 3.0 is missing migration elements (SQL script and property)
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
We need to add:
- rudder.jdbc.maxPoolSize (=25) property
- dbMigration-2.11-2.12-add-nodeconfigids-columns.sql
to the migration script !
Updated by Matthieu CERDA about 10 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-packages/pull/513
Updated by Matthieu CERDA about 10 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:05f20d649f9513f87198d160bb5e73db1bf3e01f.
Updated by Jonathan CLARKE about 10 years ago
Applied in changeset commit:d377c1bd3529716d5c57e5fa7814474e6df012a1.
Updated by Nicolas CHARLES almost 10 years ago
- Project changed from 34 to Rudder
- Parent task set to #5293
Updated by Jonathan CLARKE almost 10 years ago
- Parent task changed from #5293 to #5296
Updated by Vincent MEMBRÉ almost 10 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.0.0~beta1 which was release on 01/12/2014.
- Announcement
- Changelog
- "Download information": https://www.rudder-project.org/site/get-rudder/downloads/
Actions