Skip to main content

Azure DevOps Reader

Note

This adapter is in preview and is available on Striim Developer only. See Striim Developer for more information.

Azure DevOps is a comprehensive suite of development tools and services that enables teams to plan, develop, test, and deliver software efficiently. It supports the entire application lifecycle with features for project management, source control, continuous integration, and deployment.

Striim's Azure DevOps Reader converts these application entities into relational tables, facilitating the real-time, seamless migration of data from Azure DevOps to any relational database or data warehouse. This integration enhances reporting capabilities and provides deeper insights into development workflows and project performance.

Feature summary

Feature

Supported?

Notes

Objects

Standard objects

✓

Custom objects

✓

Authentication

Basic authentication

Username and password

OAuth authentication

Manual configuration based

Custom authentication methods

✓

Not all methods may be supported

Operations

Automated mode

✓

Initial load

✓

Pull-based incremental load

✓

Push-based incremental load

Automated pipeline

Governance

Connection profile

Sherlock AI

Sentinel AI

Schema handling

Initial schema creation

✓

Works with supported targets

Schema evolution

Setup

Wizard template

Flow Designer

✓

Striim TQL

✓

Runtime

Resilience/recovery

✓

Parallel execution

Metrics

✓

Standard metrics

Supported authentication method

The Azure DevOps Reader supports bearer token authentication using a personal access token.

Supported objects

The following are the supported objects for reading from Azure DevOps:

CatalogName

SchemaName

Object

Information

  • AgentPools

  • AuditLogEntries

  • BuildDefinitions

  • ProjectProperties

  • Projects

  • Users

  • WorkItemIds

  • WorkItemsHistory

  • WorkItemUpdatesHistory

Project_<ProjectId>

or

Project_<ProjectName>

Project

  • BacklogColumnFields

  • BacklogPanelFields

  • Backlogs

  • BacklogWorkItems

  • BoardColumns

  • BoardRows

  • Boards

  • BuildChanges

  • BuildDefinitionDrafts

  • BuildDefinitionMetrics

  • BuildDefinitions

  • BuildDemands

  • BuildLogs

  • BuildPlans

  • Builds

  • BuildValidationResults

  • BuildWorkItems

  • CommitChanges

  • CommitGitStatus

  • Commits

  • CommitWorkItems

  • Dashboards

  • DeploymentGroupMachines

  • DeploymentGroups

  • Environments

  • FeedPermissions

  • Feeds

  • FeedUpstreamSources

  • FeedViews

  • GitBranches

  • GitStats

  • IterationWorkItems

  • Pipelines

  • ProjectProperties

  • PullRequestAttachments

  • PullRequestReviewers

  • PullRequests

  • PullRequestWorkItems

  • Pushes

  • PushRefUpdates

  • Queries

  • QueryClauses

  • QueryColumns

  • ReleaseApprovals

  • ReleaseArtifacts

  • ReleaseChanges

  • ReleaseDefinitionArtifacts

  • ReleaseDefinitions

  • ReleaseDeployments

  • ReleaseEnvironments

  • Releases

  • Repositories

  • TaskGroupInputs

  • TaskGroups

  • TaskGroupSourceDefinitions

  • Tasks

  • TeamIterations

  • TeamMembers

  • Teams

  • TeamSettings

  • TestAttachments

  • TestCasePointAssignments

  • TestCases

  • TestConfigurations

  • TestPlans

  • TestPoints

  • TestResultIterationDetails

  • TestResults

  • TestRuns

  • TestRunStatistics

  • TestSessions

  • TestSubResults

  • TestSuites

  • TestVariables

  • TfvcBranches

  • TfvcChangesets

  • VariableGroups

  • Widgets

  • WikiPages

  • Wikis

  • WikiVersions

  • WorkItemIds

  • WorkItemRelations

  • WorkItemRevisionFields

  • WorkItemRevisions

  • WorkItems

  • WorkItemsFields

  • WorkItemUpdatesHistory

Repository_<RepositoryId>

  • CommitChanges

  • CommitGitStatus

  • Commits

  • CommitWorkItems

  • GitBranches

  • GitStats

  • PullRequestAttachments

  • PullRequestReviewers

  • PullRequests

  • PullRequestWorkItems

  • Pushes

  • PushRefUpdates

Analytics

  • Areas

  • BoardLocations

  • Dates

  • Iterations

  • Projects

  • Tags

  • Teams

  • Users

  • WorkItemBoardSnapshot

  • WorkItemIds

  • WorkItemLinks

  • WorkItemRevisions

  • WorkItems

  • WorkItemSnapshot

  • WorkItemTypeFields

Azure DevOps Reader properties

Property

Type

Default value

Notes

Organization

String

The name of the Organization. Navigate to Profile > Organizations to obtain the name of your organization in the account.

Personal access token

Password

The personal access token used for accessing the data in your organization. The personal access token can be found in your Organization > Profile > Personal Access Tokens.

Catalog name

String

Specify this property to connect with a particular catalog.

Specify this property to access Custom Projects. The Project catalogs contain data relating to the project specified in the catalog name. You can use either the ProjectId or Project Name in the catalog name, such as 'Project_837ccd31-8159-4db3-b8ce-de0c36d2a0bf' or 'Project_drivers'.

Schema name

String

Specify this property to connect with a particular schema.

The following are the possible schema names:

For an empty Catalog:

  • Information

For a specific Project Catalog:

  • Project

  • Analytics

  • Repository (Repository_<RepositoryId>)

You can set this property to Information to access general Azure DevOps information not related to a specific project.

Within any of the Project catalogs, you can set this property to Project, Analytics, or any of the Repository schemas.

The Project schema contains data relating to the project specified in the catalog name.

The Repository schemas contain data relating to the repository specified in the schema name. The schema name includes the RepositoryId, such as 'Repository_51b94efc-fe12-4179-825c-5ab3d0fee245'.

The Analytics schema connects to the OData Analytics service, while all other schemas connect to REST endpoints.

Connection pool size

Integer

20

Specifies the maximum number of active connections.

Exclude tables

String

A list of tables excluded from read operations. Typically used to create a list of exceptions when the Tables property includes wildcards. Misconfiguration of the Tables and Exclude Tables properties can cause "Invalid table names" errors.

Incremental load marker

String

The incremental load marker is a unique incremental column in each object used for incremental load. When no marker is specified, tables are resynced at each polling interval.

Specify the name of the column that contains the start position value. This column must meet the following criteria:

  • It should have an integer or timestamp data type (for example, a creation timestamp or an employee ID).

  • The values must be unique and continuously increasing to ensure proper incremental reading.

Migrate schema

Boolean

False

Only available in Initial Load or Automated mode. Set to True to enable initial schema migration, which propagates the object schema from the source to the target.

Mode

Select list:

  • Automated mode

  • Initial load

  • Incremental load

Automated

Automated mode applies incremental updates to objects that support incremental load and performs full resyncs for objects that do not support incremental load.

Polling interval

Integer

5m

Specifies an interval as an integer followed by a unit. Supported units are days (d), hours (h), minutes (m), or seconds (s). The reader polls the source at the specified interval.

Refresh token

Password

An OAuth 2.0 refresh token.Use the value generated while creating the token.

Start Position

String

%=-1

Value of the incremental load marker that defines the initial reading position.

Tables

String

A semicolon-delimited (;) list of objects to read from the source. Supports the % wildcard. Misconfiguration of the Tables and Exclude Tables properties can cause "Invalid table names" errors. Do not modify this property when recovery is enabled for the application.

Thread pool count

Integer

10

The number of parallel running threads. The default value of zero specifies single-threaded operation.

When the value of the thread pool counter is higher than the connection pool size, large data ingestion operations can cause the app to halt. Since best performance is achieved when using one thread for each table being synced, increasing the size of the connection pool to match the number of threads in use is a performance best practice.