Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,584
Community Members
 
Community Events
176
Community Groups

Child plan never executes after successful run of parent plan

Edited

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.

2 answers

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.

Foong Atlassian Team Jun 20, 2018

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.

 

mark a.

Foong Atlassian Team Jun 21, 2018

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?

The child build is running now--I can't give you an explanation as to why, but I can initiate the parent plan either manually or by scheduling it, and both plans do run. Thanks for your help on that.

Having a separate issue now with "Host key verification failed" when attempting to scp files from the Bamboo server to the remote agent machine. The remote agent is running under the same linux account for which the keys were generated and shared with the Bamboo server. From a terminal on the remote agent machine and logged in as that user, I can execute the same command line as the remote agent task and it succeeds. Do I (somehow) have to associate that username with the remote agent task?

I'll open this up under a separate thread--thanks for your help.

0 votes
Foong Atlassian Team Jun 20, 2018

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?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events