DevOps / Bamboo: Continuous Integration & Deployment Interview Questions
How does Bamboo share artifacts between stages?
A job defines an artifact by pointing to files it produces (e.g. target/*.jar), and marking that definition as shared makes it available to every later stage in the plan automatically. Bamboo copies the file(s) to its artifact storage after the producing job finishes, and any job in a subsequent stage that needs them has them downloaded onto its agent before its own tasks start.
This matters because different stages often run on different agents — without shared artifacts, a "Package" stage's output wouldn't exist on the agent running the later "Deploy" stage. It also avoids rebuilding the same code twice: the test and package stages consume the exact binary the build stage produced, rather than each stage recompiling independently.
More Related questions...
