Bamboo separate repositories for server / client interfaces

[Emeric LEBON]

We're currently developing a server/client application. The server is a maven Java EE project. The client interfaces are in HTML5. We use Stateless REST interfaces to communicate with each other. As there are two subteams in our project team, we decided it was a good thing to separate the server and client interfaces in two git repositories (web dev team doesn't need the server for developing/testing interfaces, and vice versa).

However, when it comes to packaging, we need to integrate the web interfaces into the server package. To do this, we use git subtrees to install the web interfaces in the server projet before launching mvn package. This is not a good thing since the code is duplicated in the server git repository, and we have to check manually for newer versions of the web interfaces.

We recently have felt the need for a CI server, and we went for Bamboo, as we already use Stash, Jira and Confluence in our company.

Is there a way to make Bamboo actually do the web interfaces integration before packaging so we don't have to use git subtree?

[Radek Antoniuk]

I would define two repositories to check out from in Bamboo and then use packaging to bundle them together.

You can use any packaging tool you want, e.g. maven or gradle to do that.

[Aakash Basnet]

Bamboo is a CI server that is used to build and deploy with its resulted artifact. So for the packaging we need to configure a bamboo build plan, and for that we need a source repository to linked with the code and version control like  git,svn or any other is necessary to collaborate with the stash. since stash is a git repository management system so it is better to use git as vcs.