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,458,620
Community Members
 
Community Events
176
Community Groups

Scan for Bitbucket yaml repository fails with unknown error

I am running bitbucket server, and bamboo server.

We have deposited a yaml build spec on the bitbucket server, and linked bitbucket with bamboo.

We had minor issues with this link, because bamboo is behind an IIS as a reverse proxy (this was necessary to enable https).

In any case: the link is working. I can generate a linked repository, and I can select a branch within any repository.

However, when I scan for build specs, I get the following:

Couldn't start Bamboo Specs scanning

An unknown error has occurred. See the logs for more details.

 

However, I do not see any log messages that seem directly related. Only one log-message is created, and it supposedly a warning:

2020-07-10 21:56:34,331 WARN [http-nio-8085-exec-15] [XsrfResourceFilter] Additional XSRF checks failed for request: http://localhost:8085/rest/api/latest/repository/1638401/scanNow , origin: https://bamboo.XXXX.com , referrer: https://bamboo.XXXX.com/admin/configureLinkedRepositories!doDefault.action , credentials in request: true , allowed via CORS: false

Any hints or tips? Thanks!

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events