Actions
Bug #3027
closed
(Techniques) "Enforce a file content" version 3.1 doesn't appear in Rudder 2.4
Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas PERRON
Category:
Techniques
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
On Rudder 2.4, the newest version of Enforce a file content (v3.1) hasn't be correctly merged and contains wrong tag in metadata.xml. Consequently, Rudder can't import this version of the Technique and #2945 #2819 bug corrections will not be able.
The fix is to change "POLICY" by "TECHNIQUE".
Check:
grep -ER "(<POLICY name=.*>|</POLICY>)"
Updated by Nicolas PERRON about 12 years ago
- Status changed from New to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:bcbd19f52eaa4580fd56c42a81cbaba4eebf61f7.
Updated by Nicolas PERRON about 12 years ago
- Target version changed from 2.4.0~rc2 to 2.4.0~rc1
Updated by Jonathan CLARKE about 12 years ago
- Subject changed from (Techniques) Enforce a file content v3.1: Merge between branch 2.3 and 2.4 has failed and the version doesn't appear in Rudder 2.4 to (Techniques) "Enforce a file content" version 3.1 doesn't appear in Rudder 2.4
Updated by Jonathan CLARKE about 12 years ago
- Status changed from Pending technical review to Released
- Target version changed from 2.4.0~rc1 to 2.4.0~rc2
Technical review OK, but can't be targeted on RC1 as that has been released.
Updated by Jonathan CLARKE about 12 years ago
- Status changed from Released to Pending release
Updated by Jonathan CLARKE about 12 years ago
- Status changed from Pending release to Released
Actions