The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

unable to scan repository ( couldn't resolved the team details) -- Critical

Adesh Kumar Singh
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 26, 2021

Hi Team,

This is regarding the issue we have been facing since yesterday 4 P.M , Suddenly our jenkins start throwing error during scan with a message "Could not resolve team details" , initially we were things that this might be due to any maintenance jobs but still we are on same stage.

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 31, 2021

Hi @Adesh Kumar Singh,

I see that you have opened a support ticket for this issue as well, but I wanted to provide the response here for any other users who may come across the same issue.

If you're using the Bitbucket Branch Source plugin in Jenkins, the reason for this error is that the plugin was not updated before the deprecation of certain Bitbucket API endpoints:

The plugin is not owned or maintained by Atlassian. Its owner has been notified here:

and I can see in that issue's comments that version 2.9.11 has been released for the plugin, which should solve the issue.

Kind regards,
Theodora

TAGS
AUG Leaders

Atlassian Community Events