How to set up a Bamboo deployment pipeline for a Java web application?

Confirmed facts

You have a Bamboo server with at least one remote agent, default JDK and Maven capabilities, and the Java web app source is in a Git repository.

Likely explanation

Assuming the build produces a WAR (or JAR) file in the target/ directory and you want to promote successful builds through Test → Staging → Production environments, the pipeline can be built from a single plan that publishes the artifact and a deployment project that consumes it.

Steps

1. Create the build plan
   • Link the plan to the Git repository (Repository tab).
   • Keep the default Source Code Checkout task.
   • Add a Maven 3.x task with goals clean install (or package) to compile and produce the artifact.
   • On the Artifacts tab, define an artifact (e.g., webapp-war) pointing to target/*.war (or target/*.jar) and enable “Share this artifact so other plans can download it”.
2. Verify the build
   • Run the plan manually; confirm the artifact appears in the Artifacts tab and can be downloaded.
3. Create a deployment project
   • Set the build plan as the source.
   • Add three environments: Test, Staging, Production.
   • For each environment, add a Deploy task:
     • If the target server is reachable via SSH from the Bamboo agent, use an SCP task (or Script task with scp) to copy the shared artifact to the deployment directory.
     • If the agent has direct filesystem access, use a simple Script task to copy the artifact (cp ${bamboo.shared.artifact.webapp-war} /path/to/deploy/).
   • Optionally add post‑deployment tasks (smoke‑test script, DB migration, notification).
4. Configure promotion
   • Set the Test environment to auto‑deploy on successful build (Trigger tab → “Deploy after successful build”).
   • Leave Staging and Production as manual promotions (use the “Promote” button) or add branch‑based triggers if desired.

Missing diagnostic detail

Please confirm whether your target deployment environment is accessible via SSH from the Bamboo agent, as this determines whether to use an SCP task or a local file copy for the Deploy step.