Bamboo Child Plan Needs Artifact from Triggering Build (Including FAILED Builds) Instead of Latest S

[DIETZ Alexander]

Hi,

I'm trying to build a reusable AI failure-analysis workflow in Bamboo and I'm stuck on artifact handling.

Goal

=====

I want a generic Bamboo plan that can be reused by multiple other plans.

Example:

SAF-QCLV

↓

COM-QTFAA (AI Analysis)

The source plan runs tests and produces artifacts such as:

- test_result.html

- junit.xml

- ai_analysis_report.txt

The analysis plan should then automatically run and analyze the artifacts produced by the build that triggered it. The key requirement is that this must work for FAILED builds because the entire purpose is failure analysis.

Current Setup

=============

Source Plan:

- SAF-QCLV

Child Plan:

- COM-QTFAA

The child plan is configured as a downstream/child plan and is triggered automatically after SAF-QCLV completes.

The source plan creates a shared artifact "ai_analysis_report.txt".

The file is successfully created and appears in the build artifacts.

Problem

=======

I added an Artifact Downloader task to COM-QTFAA.

The downloader successfully retrieves artifacts, but it always appears to retrieve artifacts from the latest SUCCESSFUL build of SAF-QCLV.

Example:

Build #12 = SUCCESS

Build #13 = FAILED

COM-QTFAA is triggered by Build #12.

However, the Artifact Downloader downloads artifacts from Build #12 instead of Build #13.

This makes the analysis useless because it is analyzing the wrong run.

Things I Have Already Verified

==============================

✅ Child plan triggering works

✅ Artifact creation works

✅ Artifact is marked Shared

✅ Artifact Downloader works

✅ The artifact exists in the triggering build

✅ The source plan may fail after the artifact has already been generated

❌ Child plan cannot access the artifact from the FAILED triggering build

Additional Notes

================

I initially tried sharing files through local disk paths, but discovered Bamboo schedules jobs on different agents.

Questions

=========

1. Is it possible for a child plan to access artifacts from the exact build that triggered it, even if the parent build FAILED?

2. Is there a Bamboo variable available in the child plan that identifies the triggering build result key?

3. Can the Artifact Downloader be configured to use:

- triggering build

instead of:

- latest successful build

4. Is there a recommended Bamboo design pattern for implementing a reusable "failure analysis" plan that can be attached to many different build plans?

5. Has anyone implemented a workflow where:

Build Plan

      ↓

Reusable Analysis Plan

      ↓

AI / Log Analysis

and the analysis must work on failed builds?

The end goal is to have a single reusable Bamboo plan that can be connected to different test plans to automatically analyze the logs to investigate the failures. 

Any advice would be greatly appreciated.