Bug #12171

Normalize plugin build structure

Added by François ARMAND 17 days ago. Updated 1 day ago.

Pending release
Target version:
Target version (plugin):
User visibility:
Effort required:


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.


Bug #12197: More clean-up on blank template projectPending releaseVincent MEMBRÉ

Bug #12199: Parent pom updete needed for pluginsReleasedFrançois ARMAND

Bug #12200: Dependencies update consequencesReleasedFrançois ARMAND

Bug #12201: Missing part of POM for node external reportPending releaseVincent MEMBRÉ

Associated revisions

Revision 01e80940
Added by François ARMAND 11 days ago

Fixes #12171: Normalize plugin build structure


#1 Updated by François ARMAND 11 days ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to

#2 Updated by Normation Quality Assistant 9 days ago

  • Assignee changed from Vincent MEMBRÉ to François ARMAND

#3 Updated by François ARMAND 9 days ago

  • Status changed from Pending technical review to Pending release

Also available in: Atom PDF