Handling version of own dependencies in multi-project codebase in Jenkins

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

Handling version of own dependencies in multi-project codebase in Jenkins

Andreas Røsdal

I'm using Jenkins to build and deploy a Java application which consists of multiple Maven projects.
One of the projects is a front-end Java Maven project, and it has the other Maven projects (Java lower-level code I also develop) specifed as dependencies in it's pom.xml file.

When I make changes to the code-base I typically make changes in a feature branch in git, on both the front-end and it's dependencies.
The dependencies are hosted in separate git repositories. There can be many feature branches I work in parallell on at any given time.

How can I use Jenkins to build this Java application, so that when I develop a new feature which includes changes to code in both a feature branch in the front-end
and changes to code in the feature branch of it's dependencies, then the whole Java application gets built by Jenkins correctly?


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/3a3c6ccd-24d0-4340-9e4c-138110f5a427%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.