Hi,

I like to implement the following build queue in one of our projects:

1. A developer commits a change for a module.
2. The module is build by Jenkins and module tests are executed.
3. Jenkins builds a Karaf custom distribution containing the new module.
4. Jenkins executes integration tests on the built Karaf custom distribution
using PaxExam.

Our Karaf custom distribution uses a custom features.xml. Unfortunately
Jenkins cannot parse the dependencies from the features.xml file and hence
cannot trigger der custom distribution build, when one of the modules is
build.

I see several solutions for this problem:

1. Build the features.xml file using the karaf-maven-plugin and Maven
dependencies. The custom distribution job depends on the features.xml job. A
built module triggers building the features.xml triggers building the custom
distribution. Cons: The features.xml file created by the karaf-maven-plugin
does not does not meet our needs.

2. Maintain the dependencies in features.xml and as Maven dependencies.
Cons: Duplication.

3. Create a Jenkins plugin which parses the features.xml file and acts as
build trigger for the Karaf custom distribution build job. Probably the best
solution, but quite expensive.

Does anyone know other solutions to trigger a Jenkins build when a
dependency defined by features.xml file is build?

Regards
Jochen



--
View this message in context: 
http://karaf.922171.n3.nabble.com/Triggering-a-Jenkins-build-when-dependency-defined-in-feature-xml-is-updated-tp4034123.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Reply via email to