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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

noDependencies() method is deprecated


I ran into an issue w/ removing the existing dependencies from a plan. The blow is the error message that I got from the publish attempt:

2018-05-29 16:43:19,817 INFO [BambooServer] An error occurred while publishing plan UIWEB-WEBMASTERTESTSCYLLA: Plan import is blocked to prevent deleting your plan dependencies silently. If you are confident that you want to delete all plan dependencies, use method explicitly.

So I tried to use noDependencies() method but didn't work because it's deprecated. Is there any workaround solution for removing a dependency from an existing plan other than noDependencies()?

2 answers

0 votes

Hi, using of noDependencies() is the only correct way of removing plan dependencies. It's deprecated from the beginning as it was architecture decision. We don't want to keep in API for a long time, but first version of Bamboo Specs didn't have solution for dependencies management so you had to configure it from UI. Next version had dependencies management, but Bamboo Specs should not silently remove it from you configuration if you was not aware of this API change.

Thanks for the answer @Alexey Chystoprudov. As I commented above, it went through with the workaround solution which I'm happy about. :)

I found a workaround solution for publishing the plan with removing dependencies. You can remove the dependencies via UI before publish then the check won’t interrupt. FYI, I referred the workaround solution for a similar issue here:

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events