Advice for structuring a maven pipeline with jenkins and git

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Advice for structuring a maven pipeline with jenkins and git

Max-3
Hi, we have several maven projects which are separate but depend on each other from within in several ways. If It helps to get the general picture, the following link lists all our current maven projects with their respective internal dependencies listed in the bullet points.
https://docs.google.com/document/d/1ybD8QIqPtYIurWLi12v-vhCAHhVwBrTH4rfAi8FKJac/edit?usp=sharing

Our goal is to build and deploy each of these to an artifactory server after any changes are pushed to github, and then build all of the projects which depend on it. Could anyone recommend a good way to structure these maven projects in git repositories with keeping jenkins in mind? I understand this is a very unspecific question in regards to jenkins, but I've already tried several different git/jenkins methods and the parent/child build structure we tried to setup when things were changed never ended up working. Thank You.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/aba673ae-58c1-4988-a25b-9d2515e15e28n%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Advice for structuring a maven pipeline with jenkins and git

Yannick Lacaute

Hi, the question is more : how many versions do you want to manage ?
Does it make sense for a final product to take a "common" dependency in version 1.1.2 while another final product take the same dependency in version 1.0.0 because late in dev ?
There is many way of doing, one repo for all, one repo per final product + one repo for all dep, one repo for everything. And when I say that I suppose "on repo = one independant version". But you could also have monorepo which manage different versions...

If your idea is to "update" dependencies versions automatically by Jenkins, I think is is not the job of Jenkins. You would take a look at tools like DependaBot or renovateBot instead.

IMO this is not related to Jenkins at all.


On Mon, Dec 21, 2020 at 9:29 AM Max <[hidden email]> wrote:
Hi, we have several maven projects which are separate but depend on each other from within in several ways. If It helps to get the general picture, the following link lists all our current maven projects with their respective internal dependencies listed in the bullet points.
https://docs.google.com/document/d/1ybD8QIqPtYIurWLi12v-vhCAHhVwBrTH4rfAi8FKJac/edit?usp=sharing

Our goal is to build and deploy each of these to an artifactory server after any changes are pushed to github, and then build all of the projects which depend on it. Could anyone recommend a good way to structure these maven projects in git repositories with keeping jenkins in mind? I understand this is a very unspecific question in regards to jenkins, but I've already tried several different git/jenkins methods and the parent/child build structure we tried to setup when things were changed never ended up working. Thank You.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/aba673ae-58c1-4988-a25b-9d2515e15e28n%40googlegroups.com.


--
Yannick LACAUTE
Consultant indépendant
39 rue de Wattignies, 75012 Paris
Tel : 06 16 85 95 76

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAG1W_Ay6eFWfbFFhBf9FVMAN_MXswNu64p_mO70g-_gNkVdmVg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: Advice for structuring a maven pipeline with jenkins and git

Max-3
Versioning wasn't really my main problem, we were really just going to usually soft depend on the latest version and resolve it in a step. Our main issue was how to build the pipeline in an efficient manner.

On Monday, December 21, 2020 at 1:39:42 AM UTC-8 [hidden email] wrote:

Hi, the question is more : how many versions do you want to manage ?
Does it make sense for a final product to take a "common" dependency in version 1.1.2 while another final product take the same dependency in version 1.0.0 because late in dev ?
There is many way of doing, one repo for all, one repo per final product + one repo for all dep, one repo for everything. And when I say that I suppose "on repo = one independant version". But you could also have monorepo which manage different versions...

If your idea is to "update" dependencies versions automatically by Jenkins, I think is is not the job of Jenkins. You would take a look at tools like DependaBot or renovateBot instead.

IMO this is not related to Jenkins at all.


On Mon, Dec 21, 2020 at 9:29 AM Max <[hidden email]> wrote:
Hi, we have several maven projects which are separate but depend on each other from within in several ways. If It helps to get the general picture, the following link lists all our current maven projects with their respective internal dependencies listed in the bullet points.
https://docs.google.com/document/d/1ybD8QIqPtYIurWLi12v-vhCAHhVwBrTH4rfAi8FKJac/edit?usp=sharing

Our goal is to build and deploy each of these to an artifactory server after any changes are pushed to github, and then build all of the projects which depend on it. Could anyone recommend a good way to structure these maven projects in git repositories with keeping jenkins in mind? I understand this is a very unspecific question in regards to jenkins, but I've already tried several different git/jenkins methods and the parent/child build structure we tried to setup when things were changed never ended up working. Thank You.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/aba673ae-58c1-4988-a25b-9d2515e15e28n%40googlegroups.com.


--
Yannick LACAUTE
Consultant indépendant
39 rue de Wattignies, 75012 Paris
Tel : 06 16 85 95 76

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/24617425-943c-4d8f-b125-9abf1633409an%40googlegroups.com.