A dependency was set up with Plan B (the child plan) in Plan A. If I run Plan A manually, Plan B never executes. If I run Plan A manually and then manually run Plan B (which requires output from Plan A), however, both successfully complete.
What is the Bamboo version?
What is the trigger configured in Plan A and B?
What is the Dependency blocking strategy configured in Plan A and B?
Bamboo version: 6.5.0
Trigger config:
Plan A: none (plan started manually) Plan B: none
Dependency blocking settings:
Plan A: none (under Dependencies on the same page, Plan B is listed as the child)
Plan B: none (under Parent Plans on the same page, Plan A is listed as the parent)
Thanks.
mark a.
What repository type used in both Plan?
Access to a repository is needed only in Plan A--the tasks are run under a local agent. The plan pulls from a Bitbucket repo and compiles the code.
Plan B runs under a dedicated remote agent, using a script that pulls the compiled code down from the machine that ran Plan A (via scp).
I can run Plan A manually, and the source is pulled and compiled. I can then run Plan B and the remote agent successfully fetches the binaries down to it's location.
If the debug logging "com.atlassian.bamboo.event" is enabled at Administration > System > Log settings , does it show the following debug message in atlassian-bamboo.log
2018-06-21 17:25:10,690 DEBUG [10-BAM::PlanExec:pool-16-thread-2] [EventLoggingThreadPoolExecutor] About to run Future for com.atlassian.bamboo.v2.trigger.DependentBuildDetectionAction for CHAIN:<projectKey>-<planB>
Is there any error in the log after Plan A finish running?
It looks like you're new here. Sign in or register to get started.
