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,461,688
Community Members
 
Community Events
176
Community Groups

Unable to enable Bamboo specs

I'm trying to enable Bamboo Specs on a server that is running Bamboo 6.5.0.
I've followed this tutorial: https://confluence.atlassian.com/bamboo/tutorial-bamboo-java-specs-stored-in-bitbucket-server-938641946.html

The Bamboo Specs repository is created like this:

1. Open Navbar -> "Create" -> "Create Bamboo Specs"
2. In the wizard dialog, select the Project and link a new repository from a "Bitbucket Server / Stash" and click "Create".
3. Create the file "bamboo-specs/bamboo.yaml" in the repository at Bitbucket Server. The content of the YAML is the Dragon Slayer spec from the example.

Everything looks good, but when I push a change in Bitbucket Server, Bamboo does not create a plan. I do not see any log output in the tab "Specs status" of the "Linked repository" and I also do not see anything in the logs of the Bamboo server that would indicate that Bamboo is doing anything.

I've checked https://confluence.atlassian.com/bamboo/enabling-repository-stored-bamboo-specs-938641941.html and also read through all the points in the troubleshooting docs (https://confluence.atlassian.com/bamboo/bamboo-specs-troubleshooting-938844477.html) and ensured that everything is set up as described there.

As I do not find any error messages, I do not know what else to do. Any hints?

1 answer

1 accepted

1 vote
Answer accepted
Foong Atlassian Team May 18, 2018

The Application Link might not be functioning correctly.

When the commit is pushed to Bitbucket Server, is there any following log message in Bamboo log?

2018-05-18 23:00:54,783 INFO [http-nio-8085-exec-24] [AuthenticatorImpl] Authenticated app 'Bitbucket:6798726783' as user 'null' successfully
2018-05-18 23:00:54,783 INFO [http-nio-8085-exec-24] [AccessLogFilter] 127.0.0.1 POST http://localhost:8085/rest/remote-event-consumer/latest/events/stash-branch-changed-remote-event 334926kb

This log message means that Bitbucket Server send a remote event trigger to Bamboo server.

You can check Bamboo Administration > System > System information > Linked Bitbucket Server instances to check the status of the remote event too.

Try recreating the Application Link.

I did not see any logs as described and status of the "Linked Bitbucket Server instance" was "Not Working".

I recreated the Application Link and now Bamboo Specs are working.

Thanks!

Warning on this course of action.
W have same issue with bamboo not finding the yaml file,

resetting the bitbucket bamboo links destroyed the existing links for all linkedrepos, bamboo would no longer build off of commits.
I think root cause is some sort of rest of the ssh keys, any way had to delete all linkedrepos and then re add the mall again to get them to work., simply re saving them did not work.
Additional oddity, bamboo would actually pick up the commits after a restart, but only once...who knows?

For us this was also after a major version increase in Bamboo from a 5 version to 6.7, with bitbucket at 4.14.

Foong Atlassian Team Jan 18, 2019

Recreating Application Link should not cause problem to SSH keys.

SSH keys are stored in different location that is not related to Application Link. Editing existing repositories will show that the link is gone and need to re-save but it will not affect the checkout process cause the SSH keys are stored in different location.

Since this question have been answered, can you raise another question with error log?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events