Bamboo Stages and Maven Life Cycle

Question

Let's say I have a pretty standard maven-based Java project that uses almost the entire maven life cycle. Compile test cases in test in compile , JUnit for test , integration testing using the automatically started and stopped berth on integration-test / verify deployed in our internal maven repository on deploy . The main things.

It also works as a build plan on our Bamboo server. At the moment, there is only one stage with one task with one task performing mvn clean deploy . This ensures that SNAPSHOT on our repo is always the latest version from the original control, which compiles without test failures.

Now, I feel that Bamboo could do more ... What are all the steps, tasks, and more, if everything is handled in one lonely task? So I thought, maybe it could be a “test” stage, an “integration-test” stage and a “deployment” stage, which perform mvn test , mvn verify and mvn deploy ... But: each stage has its own checkout and, as such, the final step is to complete the entire maven life cycle before deploying again, including validation and validation ...

What would be a good way to match maven with bamboo? I have not found examples of such configurations. Has anyone done this before in a consistent way? Or do I need to transfer test materials from pom.xml to custom Bamboo jobs?

Answer 1

From the fact that I used Bamboo for stages, there are separate objects from the point of view of assembly, each of them having a different folder on the server. However, you can share assembly artifacts between the various steps.

Configure artifact sharing between jobs

So you can use the deployment phase to get the jar from the package stage in Bamboo.