Project

General

Profile

Actions
Copy link

Bug #12417

closed

build.conf properties are not filtered (replaced) in plugin

Added by François ARMAND over 6 years ago. Updated over 6 years ago.

Status:
Released
Priority:
N/A
Assignee:
Vincent MEMBRÉ
Category:
Packaging
Target version:
4.1
Pull Request:
https://github.com/Normation/rudder-p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

The properties are not replaced in the build.conf package with the jar, what remove a little bit of interest for the file. Actually, the only real problem is ${rudder-branch} as other properties are defined in the file.

Actions
Copy link
 #1

Updated by François ARMAND over 6 years ago

  • Status changed from New to In progress
Actions
Copy link
 #2

Updated by François ARMAND over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder-plugins/pull/30
Actions
Copy link
 #3

Updated by François ARMAND over 6 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:rudder-plugins|0d12b24a2c83d3582d87e9bc96aaabacc84c626f.

Actions
Copy link
 #4

Updated by Alexis Mousset over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.11, 4.2.5 and 4.3.0~rc3 which were released today.

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 6 years ago

  • Project changed from Rudder to Rudder plugins
  • Category changed from Plugins integration to Packaging
  • Target version changed from 4.1.11 to 4.1
Actions
Copy link

Also available in: Atom PDF