Projects with many subprojects

I am working on a project which has many sub projects (about 1000). Every sub-project is basically a java package in the main project. Every sub-project should create a separate jar because they must be versioned differently. Here is the structure












Creating one job/task for every project cannot be created manually (at least I am not doing it). How should I setup a job plan to setup continuous integration on all the sub projects? What ya guys think?

1 answer

Assuming you're using Maven or Gradle to script the build and deal with dependencies - the project struture could be accomodated although you might want to refactor the code to conform to the standard structure to save some configuraiton.

There are a number of advantages to a single build with modules/subprojects:

  1. A single biuld plan versus 1k plans
  2. Space savings (only one workspace versus 1k workspaces)
  3. Better handling of inter subproject dependencies

The single con is the time it might take to run through all of the modules/subprojects.  In addition to the build avoidance baked in to Maven and Gradle, you might want to looking to parallelizing the build - a feature available in both tools.


Hope this Helps!






Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

925 views 3 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you