We are working on a legacy project and the first task is to setup a DevOps 
for the same. The important thing is we are very new to this area.

We are planning to use Jenkins and sonarqube for the purpose initially. Let 
me start with the requirements.

   - Currently the the project is sub divided into multiple projects (not 
   modules)
   - We had to follow this build structure as there is no plans for 
   re-organizing it as a single multi-module maven project
   - Currently the builds and dependencies are managed manually

Eg: The project is subdivided into 5 individual multi-module maven 
projects, say A,B,C,D and E



        1. A and C are completely independent and can be easly built

        2. B depends on the artifact generated by A (jar) and has multiple 
maven profiles (say tomcat and WebSphere, it is a web-service module)

        3. D depends on the artifact generated by C 

        4. E depends on A, B and D and has multiple maven profiles (say 
tomcat and WebSphere, it is a web project


Based on Jenkins documentation to handle this scenario, we are thinking 
about parameterized builds using “parameterized build plugin" and "extended 
choice parameter plugin" with the help of these plugins we are able to 
parameterize the profile name. But before each build, the builder waits for 
the profile parameter.


So we are still searching to find an optimum answer to the following 
questions:


     1. keep the dependency between projects an built the whole projects if 
there is any change in SCM (SVN). For that we are used "Build whenever a 
SNAPSHOT dependency is built" and "SCM polling option". Unfortunately this 
option seems not working in our case (we have given an interval of 5 min 
for scm polling but no build is happening based on test commits)


     2. Even though we are able to parameterize the profile, this seems as 
a manual step (is there an option to automate this part too, ie. build with 
tomcat profile and WebSphere profile should happen sequentially).


We are struggling to find a solution to cater all these core requirements. 
Any pointer would be greatly appreciated.

Thanks, San

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/70ea26be-f5dc-4197-b11b-bfa228b23f77%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to