Maven , Jenkins and pom.xml

[Rehan Baig]

Guys I am newbie here trying to learn CICD using jenkins

I went through pom.xml where we control the build order and provide dependencies , the training I saw is an old video, I am curious to know do we still use pom.xml to structure our CI and integerate it with jenkisn ? Or jenkisn do all the dependencies and build order (down stream or up stream)

Any guidence will be highly appreciated

[Jan Monterrubio]

Maven is a  build automation tool. The pom.xml describes the build and how to perform it. It’s mostly used for java projects. 

Jenkins simply invokes the maven process and adds other nice features on top. 

 

Jenkins doesn’t decide dependencies, those are all configured by the pom. So think of Jenkins as a machine that runs builds and describes how to run a build, as opposed to maven which describes how to build a project. 

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAC5m0rM8iMRCeaTW8yECKhG%3DFuc%2BhvK82-6zM5UfXs855tGK2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Arnaud Héritier]

Hi,

  It is often considered dangerous or difficult to manage dependencies between projects.

  It is sometimes useful, at least temporarily to have  project depending to another project using a SNAPSHOT dependency and in such a case for sure you would love to have your CI tool discovering / updating your builds dependencies.

  In Jenkins there is a plugin dedicated to Maven ( https://plugins.jenkins.io/maven-plugin ) which is providing such feature but the community highly discourages to use it (it has a lot of problems / limitations).

  The best approach nowadays is to use the dedicated Maven integration for pipeline projects : https://plugins.jenkins.io/pipeline-maven

  This plugin will be able to discover in a given instance which projects are publishing/consuming your maven artifacts and when a project will be built all others which are consuming it will be triggered after it to all you to validate that an upstream change doesn't break your downstream projects

  

Best regards

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9J1MgjX%3DPoRBp9BAdZfLoG0JCxtUKXvebSB%3Dbph50Conw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

-----

Arnaud Héritier

http://aheritier.net

Mail/GTalk: aheritier AT gmail DOT com

Twitter/Skype : aheritier