Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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?

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

251 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you