Legacy Bamboo CI Setup for AIQ Execution

Last reviewed: September 29, 2026

This page is retained for teams that still run AIQ execution plans from Atlassian Bamboo.

What changed in this article

• Marked Bamboo CI setup as legacy/environment-specific because many current CI workflows use Jenkins, GitHub, Azure DevOps, or another maintained runner.
• Replaced the long Bamboo installation walkthrough with targeted AIQ execution-plan guidance: agents, Ant tasks, repositories, credentials, and result handling.
• Called out stale dependencies from the old article, including Ubuntu 16.04, Oracle JDK 8, old Bamboo agent versions, and credential files such as creds.json.

Validation workflow

1. Confirm Bamboo is still the customer’s active CI system before using this page.
2. Validate agent OS, JDK, Ant, browser, repository, and AIQ connectivity before creating the execution plan.
3. Run one controlled Bamboo build and confirm AIQ execution results are created before scheduling recurring jobs.

Review note: Kept as legacy CI guidance and removed the impression that old Bamboo/JDK/Ubuntu setup is current default practice.

Last updated: September 29, 2026

If you have feedback on this topic, contact documentation@appvance.ai.