Thanks David for your response. I appreciate your comments. So, I would
like to build the project from the parent so could do the following. Doing
this gives me the ability to build all projects from the parent and to
build indivdual projects too! Which is what I want to achieve from
jenkins. Although from the git repository point I dont want the parent to
have the responsibility of all the projects. I want each individual
project to have their own git repo. That makes sense to me. I would like
to know if there are any possible solutions from a git point? It doesnt
seem like this solution is scalable?
Parent
+-pom.xml
+-Project1
+-module1
+-pom.xml
+-module2
+-pom.xml
+-Project2
+-module1
+-pom.xml
+-module2
+-pom.xml
On Friday, 10 March 2017 18:43:06 UTC, David Karr wrote:
>
> On Fri, Mar 10, 2017 at 8:53 AM, paul b <[email protected] <javascript:>>
> wrote:
> > I have several projects that are multi module projects that are like the
> > following
> >
> > Project1
> > +-module1
> > +-pom.xml
> > +-module2
> > +-pom.xml
> >
> > Each project is configuration controlled in git as their own project
> >
> > Now, I have created a parent project with the following flat structure.
> > This is because I would like to keep each project with its own git
> project.
> > That seems sensible for me???
>
> A basic rule for deciding where you should separate things into their
> own git repository is whether the two things need to be built
> together. If they need to be built together, then keep them in the
> same repository. The structure you've defined is not "sensible".
>
> > Parent
> > +-pom.xml
> > Project1
> > +-module1
> > +-pom.xml
> > +-module2
> > +-pom.xml
> >
> > Project2
> > +-module1
> > +-pom.xml
> > +-module2
> > +-pom.xml
> >
> > The parent pom references each project like the following
> >
> > <modules>
> > <module>../project1</module>
> > <module>../project2</module>
> > </modules>
> >
> > This is fine as per maven documentation and all works ok locally but
> when I
> > build this from Jenkins I run into issues. This is because Jenkins cant
> > find the pom file for each project. Basically this is down to the flat
> > directory structure! Is there any way in Jenkins that I can get over
> this
> > issue?
>
> Fix the problem in your repository structure, not in Jenkins.
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/5d99a764-5c68-452b-b7fc-a6f3a43640ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
