Geek Answers Handbook

Jenkins work and GIT / maven structure

I'm new to Jenkins and I don't know what works best for working with multiple maven modules. My project consists of 5 different maven projects. One such project is the parent maven project, which creates the rest. Each of these 5 maven projects is located in a separate GIT repository.

Do I have to have one job for each GIT repository or can it be configured in another way?

+4
source share
2 answers

My best practice is that you should put all projects in one GIT repository, which will be released together as you put and share the whole repository in GIT. If the project has a different release cycle, put it in a different repository.

Example:

You have 5 projects A, B, C, D and E. A, B and C for sample projects that represent one level in the zour architecture of your application. D and E are helper libraries that will change sometimes, but not with every version of your application. (e.g. additional GUI elements, ...)

In this case, I would use three repositories:

First repo:

Parentpom for A, B, C
    A as module of ParentPom
    B 
    C

Second repo:

 D

Third repo:

 E

Maven, , "" , , .

Jenkins Job , , . , Jenkins Jobs ( pom )

+2

maven . , .

0

More articles:


All Articles