Azure DevOps Integration issues

Rob96
Tera Contributor

Hi

 

Hoping someone can help. We are hoping to run a proof of concept connecting ServiceNow DevOps Change Velocity and Azure DevOps with the plan to check out management of devOps release via change management.

 

We've connected via the playbook in the workspace to a proof of concept project in our Azure DevOps. Webhooks are testing as successful in Azure DevOps as it the connection made via ServiceNow. 

 

What fails to happen is the discovery of the pipeline and repository etc from ADO. We have used a personal access token and the devops.integration user.

 

We get an inbound event that are errored with the result of "Inbound event cannot be processed because the DevOps subflow for notifications capability cannot be called due to a technical issue." and a further inbound event with an error of "Pipeline details cannot be retrieved or processed due to a technical issue."

 

Does anyone have any suggestions as what isn't working as it should be?

3 REPLIES 3

Rob96
Tera Contributor

More details on the flow and the error in the hope someone can suggest a fix.

 

devopsErrorCode SCRIPT_ACTION_ERROR

internalMsg  com.glide.plan.runners.FlowObjectAPIException: The current operation ended in state: ERROR. Detail: Attempted to add black listed role: [sys_id included here but removed for posting to this forum -can't find a role with the sys_id]

errorSources ["Flow action - DevOps Call Subflow for notifications capability","Flow - DevOps Integration - Orchestration Notification"]

 

properties

 

Subflow with the "technical error" is "Flow action - DevOps Call Subflow for notifications capability","Flow - DevOps Integration - Orchestration Notification"

Rob96
Tera Contributor

I found this post once I searched for "blacklisted role"

 

https://www.servicenow.com/community/devops-forum/flow-designer-error/m-p/2728167

 

Following the OP's solution post we are now also getting data imports 😀

Mathieu Lepoutr
Mega Guru

The main issue is that under the 'Contain Roles' related table, inside the ‘sn_devops.viewer’ and the ‘sn_devops.tool_owner’ roles records, there is a role named '(empty)' .Please remove it and it will solve the issue. You can also use Exalate, which is a decentralized integration solution, where you can granuarly decide which data will be send over and applied