Bug #12171
closed
Normalize plugin build structure
Description
As the number of plugins increase, we want to normalize their structure and the quantity of information that is duplicated in each of them.
The main points are:
- use a "master" build.conf for rudder-branch and perhaps other properties common to all plugin on a given branch,
- perhaps use a master pom to centralize common behaviour (at least, the maximun number of them)
- perhaps find a simpler to check for license build. We would like to have that provided as a service to all plugin without any code on their side for the status checking (it's extremelly error prone and verbose right now)
Some change will need to be made in 4.1, other in 4.3 (because they will also need changes in Rudder plugin API). This ticket takes care of 4.1 branch.
Updated by François ARMAND about 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/20
Updated by Rudder Quality Assistant about 6 years ago
- Assignee changed from Vincent MEMBRÉ to François ARMAND
Updated by François ARMAND about 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset commit:rudder-plugins|01e8094073f9d0275d92d840327761bb0785d2ce.
Updated by Alexis Mousset about 6 years ago
- Status changed from Pending release to Released
Updated by Vincent MEMBRÉ over 5 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
Updated by Vincent MEMBRÉ over 5 years ago
- Related to Bug #12199: Parent pom update needed for plugins added