Forums

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

Bitbucket server plugin failing authorization in jenkins (since some time)

manojkdi
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!
May 22, 2020

I have been using bitbucket server integration from last 20 days. It was working fine till last week end. Now i see authorization falilre at the SCM step of the jenkins pipeline. When I look at the jekins server log I see these messages

INFO hudson.model.AsyncPeriodicWork lambda$doRun$0
Started Periodic background build discarder
INFO hudson.model.AsyncPeriodicWork lambda$doRun$0
Finished Periodic background build discarder. 18 ms
INFO com.atlassian.bitbucket.jenkins.internal.http.HttpRequestExecutorImpl handleError
Bitbucket - Path not found
INFO com.atlassian.bitbucket.jenkins.internal.trigger.register.BitbucketWebhookHandler lambda$findSame$5
Found an existing webhook - {"id":1361,"name":"7eb4031e11b7cc93425f3c4d5cb5bdf615f2fe88","url":"https://jenkins-c2000sw.dal.design.ti.com/bitbucket-server-webhook/trigger","events":[repo:refs_changed],"active":true}
INFO com.atlassian.bitbucket.jenkins.internal.http.HttpRequestExecutorImpl handleError
Bitbucket - Path not found
INFO com.atlassian.bitbucket.jenkins.internal.http.HttpRequestExecutorImpl handleError
Bitbucket - Path not found
INFO com.atlassian.bitbucket.jenkins.internal.http.HttpRequestExecutorImpl handleError
Bitbucket - responded with not authorized
INFO com.atlassian.bitbucket.jenkins.internal.http.HttpRequestExecutorImpl handleError
Bitbucket - Path not found
INFO com.atlassian.bitbucket.jenkins.internal.http.HttpRequestExecutorImpl handleError
Bitbucket - Path not found
INFO com.atlassian.bitbucket.jenkins.internal.http.HttpRequestExecutorImpl handleError
Bitbucket - Path not found
INFO jenkins.branch.MultiBranchProject$BranchIndexing run
TopoGrandeBootROM/build-topogrande-bootrom #20200522.030723 branch indexing action completed: SUCCESS in 8.1 sec
WARNING jenkins.branch.WorkspaceLocatorImpl getWorkspaceRoot
JENKINS-2111 path sanitization ineffective when using legacy Workspace Root Directory ‘${ITEM_ROOTDIR}/workspace’; switch to ‘${JENKINS_HOME}/workspace/${ITEM_FULL_NAME}’ as in JENKINS-8446 / JENKINS-21942
WARNING jenkins.branch.WorkspaceLocatorImpl getWorkspaceRoot
JENKINS-2111 path sanitization ineffective when using legacy Workspace Root Directory ‘${ITEM_ROOTDIR}/workspace’; switch to ‘${JENKINS_HOME}/workspace/${ITEM_FULL_NAME}’ as in JENKINS-8446 / JENKINS-21942
WARNING org.jenkinsci.plugins.workflow.job.WorkflowRun getLogFile
Avoid calling getLogFile on TopoGrandeBootROM/build-topogrande-bootrom/develop #126

 

 

1 answer

0 votes
Abdulkarim Itani October 15, 2020

Were you able to fix this ?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events