Help Manual

Azure DevOps JDBC Driver

Documentation for Azure DevOps drivers found within JDBC Driver Pack

Azure DevOps

Building the JDBC URL

After installing the license, access the connection management page by executing the command java -jar kingswaysoft.jdbc.jar. Enter the necessary details, and the program will automatically generate the JDBC connection URL. Users can click Test Connection to test the generated URL and Copy to Clipboard to copy the connection string for use within the application where the JDBC driver is being used.

Note: If the license is not installed, you can still use the connection manager to generate a JDBC URL; however, the 'Test Connection' feature will be disabled.

General Page

The General page allows you to specify connection properties and login credentials for the Azure DevOps REST service.

connectionmanage

General Settings
General Settings
Connection Type

The Connection Type refers to the connection methods we support for Azure DevOps. We support both online and on-premise modes.

Service URL

The Service URL is the Azure DevOps URL that we connect to.

Version

The Version is the API version we connect to.

Project

The Project is the name of the Project we need to connect to.

API Throttling Rate

The API Throttling Rate will limit the number of requests that can be sent per second. Set this value to 0 to disable API throttling.

Authentication
Authentication for Online Mode

The Authentication Mode option allows you to choose the method used to authenticate with the Azure DevOps API. Available options are:

  • Personal Access Token
  • Authorization Code
  • Client Credentials
  • Certificate
Authentication for On-premise Mode

The Authentication Mode option allows you to choose the method used to authenticate with the Azure DevOps API. Available options are:

  • Personal Access Token
  • Password

Authentication Methods for Azure DevOps

Personal Access Token

Choose to use personal access token to establish a connection.

Personal Access Token
The personal access token can be used to establish a connection.
Password

Choose to use user name and password to establish a connection.

Domain
Domain allows you to specify the domain that you want to use when connecting to Azure DevOps.
User Name
User Name allows you to specify the user account that you want to use when connecting to Azure DevOps.
Password
Password allows you to specify the password that you want to use when connecting to Azure DevOps.
Authorization Code

A generated access token can be used to establish a connection.

Access Token
The access token can be used to establish a connection.
<dt><strong>Generate Token File</strong></dt>
<dd>
  <p>This button completes the OAuth authentication process in order to generate a new access token.</p>
  <ul>
    <li><strong>Tenant Id:</strong> The Tenant Id option allows you to specify the Tenant Id where the Client App Id is verified to complete the authorization process.</li>
    <li><strong>Client Id:</strong> The Client Id option allows you to specify the unique ID which identifies the application making the request.</li>
    <li><strong>Client Secret:</strong> The Client Secret option allows you to specify the client secret belonging to your app.</li>
    <li><strong>Redirect Url:</strong> The Redirect Url option allows you to specify the Redirect Url to complete the authentication process.</li>
         <li><strong>PKCE (Enhanced Security):</strong> The PKCE (Proof Key for Code Exchange) option may be enabled for PKCE App Type. Ensures that the client that initiates the OAuth flow is the same client that completes the flow.</li>
  </ul>
</dd>
Client Credentials

Enter Tenant Id, Client App Id and Client Secret to establish a connection.

Tenant Id
The Tenant Id option allows you to specify the Tenant Id where the Client App Id is verified to complete the authorization process.
<dt><strong>Client Id</strong></dt>
<dd>The Client Id option allows you to specify the unique ID which identifies the application making the request.</dd>

<dt><strong>Client Secret</strong></dt>
<dd>The Client Secret option allows you to specify the client secret belonging to your app.</dd>
Certificate

Choose to use a saved certificate file and certificate password to establish a connection.

Tenant Id
The Tenant Id option allows you to specify the Tenant Id where the Client App Id is verified to complete the authorization process.
<dt><strong>Client Id</strong></dt>
<dd>The Client Id option allows you to specify the unique ID which identifies the application making the request.</dd>

<dt><strong>Path To Certificate</strong></dt>
<dd>The path to an existing certificate file.</dd>

<dt><strong>Certificate Password</strong></dt>
<dd>The password for the specified certificate file.</dd>
Test Connection

After all the connection information has been provided, click the "Test Connection" button to test if the user credentials entered can successfully connect to the selected service.

Advanced Settings Page

The Advanced Settings page allows you to specify advanced settings for the connection.

connectionmanage

Proxy Server Settings
Proxy Server Settings
Proxy Mode

The Proxy Mode option allows you to specify how you want to configure the proxy server setting. There are three options available.

  • No Proxy
  • Auto-detect (Use system configured proxy)
  • Manual
Proxy Server

Using the Proxy Server option allows you to specify the name of the proxy server for the connection.

Port

The Port option allows you to specify the port number of the proxy server for the connection.

Username (Proxy Server Authentication)

The Username option (under Proxy Server Authentication) allows you to specify the proxy user account.

Password (Proxy Server Authentication)

The Password option (under Proxy Server Authentication) allows you to specify the proxy user's password.

Miscellaneous Settings
Miscellaneous Settings
Timeout (secs)

The Timeout (secs) option allows you to specify a timeout value in seconds for the connection. The default value is 120 seconds. Specify 0 for an infinite timeout.

Retry on Intermittent Errors

The retry on intermittent errors determines if requests will be retried when there is an error. If this option is checked, requests will be retried up to 3 times.

Ignore Certificate Errors

This option can be used to ignore those SSL certificate errors when connecting to the target server.

Warning: Enabling the "Ignore Certificate Errors" option is generally NOT recommended, particularly for production instances. Unless there is a strong reason to believe the connection is secure - such as the network communication is only happening in an internal infrastructure, this option should be unchecked for best security.

Note: When this option is enabled, it applies to all HTTP-based SSL connections in the same job process.

Concurrent Writing Threads

This option can be used to set the number of threads to be used during write operations. This can improve performance during large-volume write operations.

Using the JDBC Driver

Explore detailed examples in this section that demonstrate the application of JDBC classes such as Connection, Statement, and ResultSet to effectively manage interactions with Azure DevOps data. This section covers the use of regular statements and prepared statements for executing complex or frequently executed queries.

Executing Statements

Once you've connected from your code (see Connecting with DriverManager and Connecting with DataSource), you can execute SQL statements using the Statement class. Refer to the Executing Prepared Statements section for information on how to execute parameterized statements.

SELECT

Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data. To retrieve the results of a query, you would then call the getResultSet method of the Statement.

String sql = "SELECT * FROM tags";
try {
    ResultSet resultSet = statement.executeQuery(sql);
    LOGGER.info(resultSet.toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}
Reading using WIQL

Azure DevOps supports the 'Work Item Query Language' which is used for filtering and retrieving work items (such as bugs, user stories, and tasks) based on specific criteria.

String sql = "SELECT System.Id, System.Title, System.State FROM workitems WHERE System.WorkItemType = 'Task' "
           + "AND (System.State <> 'Done' AND System.State <> 'Doing') ORDER BY System.CreatedDate DESC";
try {
    ResultSet resultSet = statement.executeQuery(sql);
    LOGGER.info(resultSet.toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

INSERT

Use either the generic execute method or the executeUpdate method of the Statement class to execute an INSERT operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the inserted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "INSERT INTO workItems/comments (workItemId, text, format) VALUES (185, '<p>test comment</p>', 'html')";

try {
    int result = statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
14250325,null,null,{"text":"<p>test comment</p>"},false

UPDATE

Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the updated data's ID, exceptions raised during execution, and details of the affected data.

String sql = "UPDATE workitems SET System.State = 'Done' WHERE id = 184";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
184,null,null,[{"op":"replace","path":"/fields/System.State","value":"Done"}],false

DELETE

Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "DELETE FROM workitems WHERE id = '15'";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,null,false

Executing Prepared Statements

Using a PreparedStatement can improve performance when you need to execute a SQL statement multiple times with different parameters. Unlike a Statement object, a PreparedStatement object is provided with a SQL statement when it is created, which can then be executed with different values each time. This special type of statement is derived from the more general class, Statement.

Below are the steps outlining how to execute a prepared statement:

Creating and Executing a Prepared Statement
  1. Create a PreparedStatement
  2. Set Parameters
    • Declare parameters by calling the corresponding setter method of the PreparedStatement.
    • NOTE: The parameter indices start at 1.
  3. Execute the PreparedStatement
    • Use the generic execute or executeUpdate method of the PreparedStatement.
  4. Retrieve Results
    • Call the getResultSet method of the PreparedStatement to obtain the query results, which will be returned as a ResultSet.
  5. Iterate Over the Result Set
    • Use the next method of the ResultSet to iterate through the results. To obtain column information, utilize the ResultSetMetaData class. Instantiate a ResultSetMetaData object by calling the getMetaData method of the ResultSet.

SELECT

Use the PreparedStatement class's generic execute method or the executeQuery method to execute SQL statements that return data.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the retrieved data.

String sql = "SELECT * FROM instances/manage/measures WHERE instanceId = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "21994");
    boolean ret = ps.execute(sql);
    if (ret) {
        ResultSet rs = ps.getResultSet();
        LOGGER.info(rs.toString());
    }
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}
Reading using WIQL

Azure DevOps supports the 'Work Item Query Language' which is used for filtering and retrieving work items (such as bugs, user stories, and tasks) based on specific criteria.

String sql = "SELECT System.Id, System.Title, System.State FROM workitems WHERE System.WorkItemType = ? "
           + "AND (System.State <> ? AND System.State <> ?) ORDER BY System.CreatedDate DESC";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "Task");
    ps.setString(2, "Done");
    ps.setString(3, "Doing");
    boolean ret = ps.execute(sql);
    if (ret) {
        ResultSet rs = ps.getResultSet();
        LOGGER.info(rs.toString());
    }
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

INSERT

Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an INSERT operation.

The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of inserted data, exceptions raised during execution, and the data affected by the insertion.

String sql = "INSERT INTO workItems/comments (workItemId, text, format) VALUES (?, ?, ?)";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "185");
    ps.setString(2, "<p>test comment</p>");
    ps.setString(3, "/html");
    ps.executeUpdate();

    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
14250325,null,null,{"text":"<p>test comment</p>"},false

UPDATE

Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute an UPDATE operation.

The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of updated data, exceptions raised during execution, and the data affected by the update.

String sql = "UPDATE workitems SET System.State = ? WHERE id = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "Done");
    ps.setString(2, "184");
    ps.executeUpdate();
    
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
184,null,null,[{"op":"replace","path":"/fields/System.State","value":"Done"}],false

DELETE

Use either the generic execute method or the executeUpdate method of the PreparedStatement class to execute a DELETE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "DELETE FROM workitems WHERE id = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "21994");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    e.printStackTrace();
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,null,false

Metadata Discovery

This section provides examples on how to retrieve table and column metadata using the getTables, getColumns, and getPrimaryKeys methods from the DatabaseMetaData interface. These are essential for discovering database structures.

Tables

The getTables method from the DatabaseMetaData interface can be used to retrieve a list of tables.

This method only retrieves tables that are not write-only.

To get a list of tables which include write-only tables, query the table system.tables.

try {
    ResultSet rs = connection.getMetaData().getTables(null, null, null, null);
    LOGGER.info("\r\n" + rs.toString());
} catch (SQLException e) {
    LOGGER.severe(e.getMessage());
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,TABLE_TYPE,REMARKS
null,null,artifactlinktypes,Table,null
null,null,classificationnodes,Table,null
null,null,fields,Table,null
null,null,queries,Table,null
null,null,recyclebin,Table,null
null,null,reporting/workItemRevisions/discussions,Table,null
null,null,reporting/workitemlinks,Table,null
null,null,reporting/workitemrevisions,Table,null
null,null,system.columns,Table,null
null,null,system.tables,Table,null
null,null,tags,Table,null
null,null,templates,Table,null
null,null,wiql,Table,null
null,null,work/accountmyworkrecentactivity,Table,null
null,null,workItems/comments,Table,null
null,null,workItems/comments/reactions,Table,null
null,null,workItems/comments/reactions/users,Table,null
null,null,workItems/comments/versions,Table,null
null,null,workItems/revisions,Table,null
null,null,workItems/updates,Table,null
null,null,workitemicons,Table,null

The getTables method returns the following metadata columns:

Column Name Data Type Description
TABLE_CAT String The catalog that contains the table.
TABLE_SCHEM String The schema of the table.
TABLE_NAME String The name of the table.
TABLE_TYPE String The type of the table (e.g., TABLE or VIEW).
REMARKS String An optional description of the table.

Columns

Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about database columns. To narrow the results to a specific table, specify the table name using the parameter table_name.

This method returns columns only for tables that are not write-only.

To get columns for tables which are write-only, query the table system.columns.

try {
    ResultSet rs = connection.getMetaData().getColumns(null, null, "workitems", null);
    LOGGER.info(rs.toString());
} catch (SQLException e) {
    e.printStackTrace();
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,DATA_TYPE,TYPE_NAME,COLUMN_SIZE,BUFFER_LENGTH,DECIMAL_DIGITS,NUM_PREC_RADIX,NULLABLE,REMARKS,COLUMN_DEF,SQL_DATA_TYPE,SQL_DATETIME_SUB,CHAR_OCTET_LENGTH,ORDINAL_POSITION,IS_NULLABLE,SCOPE_CATALOG,SCOPE_SCHEMA,SCOPE_TABLE,SOURCE_DATA_TYPE,IS_AUTOINCREMENT,IS_GENERATEDCOLUMN,DTS_TYPE
null,null,workitems,System.AreaId,-5,BIGINT,null,null,0,0,null,null,null,-5,null,null,null,null,null,null,null,null,null,null,DT_I8
null,null,workitems,System.AreaPath,12,VARCHAR,null,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,workitems,System.AssignedTo,12,VARCHAR,null,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,workitems,System.AttachedFileCount,-5,BIGINT,null,null,0,0,null,null,null,-5,null,null,null,null,null,null,null,null,null,null,DT_I8
null,null,workitems,System.AuthorizedAs,12,VARCHAR,null,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,workitems,System.AuthorizedDate,93,TIMESTAMP,null,null,0,0,null,null,null,93,null,null,null,null,null,null,null,null,null,null,DT_DBTIMESTAMP
null,null,workitems,System.BoardColumn,12,VARCHAR,null,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,workitems,System.BoardColumnDone,16,BOOLEAN,null,null,0,0,null,null,null,16,null,null,null,null,null,null,null,null,null,null,DT_BOOL
null,null,workitems,System.BoardLane,12,VARCHAR,null,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,workitems,System.ChangedBy,12,VARCHAR,null,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,workitems,System.ChangedDate,93,TIMESTAMP,null,null,0,0,null,null,null,93,null,null,null,null,null,null,null,null,null,null,DT_DBTIMESTAMP
null,null,workitems,System.CommentCount,-5,BIGINT,null,null,0,0,null,null,null,-5,null,null,null,null,null,null,null,null,null,null,DT_I8
...

The getColumns method returns the following columns:

Column Name Data Type Description
TABLE_CAT String The database name.
TABLE_SCHEM String The table schema.
TABLE_NAME String The table name.
COLUMN_NAME String The column name.
DATA_TYPE Integer The data type represented by a constant value from java.sql.Types.
TYPE_NAME String The data type name used by the driver.
COLUMN_SIZE Integer The length in characters of the column or the numeric precision.
BUFFER_LENGTH Integer The buffer length.
DECIMAL_DIGITS Integer The column scale or number of digits to the right of the decimal point.
NUM_PREC_RADIX Integer The radix, or base.
NULLABLE Integer Whether the column can contain null as defined by the following JDBC DatabaseMetaData constants: columnNoNulls (0) or columnNullable (1).
REMARKS String The comment or note associated with the object.
COLUMN_DEF String The default value for the column.
SQL_DATA_TYPE Integer Reserved by the specification.
SQL_DATETIME_SUB Integer Reserved by the specification.
CHAR_OCTET_LENGTH Integer The maximum length of binary and character-based columns.
ORDINAL_POSITION Integer The position of the column in the table, starting at 1.
IS_NULLABLE String Whether a null value is allowed: YES or NO.
SCOPE_CATALOG String The catalog of the table referenced by a reference attribute (null if DATA_TYPE is not REF).
SCOPE_SCHEMA String The schema of the table referenced by a reference attribute (null if DATA_TYPE is not REF).
SCOPE_TABLE String The name of the table referenced by a reference attribute (null if DATA_TYPE is not REF).
SOURCE_DATA_TYPE Short The source type of a distinct type or user-defined REF type (null if DATA_TYPE is neither DISTINCT nor a user-defined REF).
IS_AUTOINCREMENT String Whether the column value is assigned by Azure DevOps in fixed increments.
IS_GENERATEDCOLUMN String Whether the column is generated: YES or NO.
DTS_TYPE String Object DTS attribute type.

Primary Keys

The getPrimaryKeys method in the DatabaseMetaData interface is used to retrieve metadata about primary keys for a given table in Azure DevOps.

try {
    ResultSet resultSet = connection.getMetaData().getPrimaryKeys(null, null, "workitems");
    LOGGER.info("\r\n" + resultSet.toString());
    Assertions.assertNotNull(resultSet);
} catch (SQLException e) {
    LOGGER.severe(e.getMessage());
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,KEY_SEQ,PK_NAME
null,null,workitems,id,1,null

The getPrimaryKeys method returns the following columns:

Column Name Data Type Description
TABLE_CAT String The catalog name.
TABLE_SCHEM String The schema name.
TABLE_NAME String The name of the table that contains the primary key.
COLUMN_NAME String The name of the column that serves as the primary key for the table.
KEY_SEQ Short The sequence number within the primary key.
PK_NAME String The primary key name.

Connection Settings

Connection Setting Type Default Value Description
ApiThrottleRate Integer 10 The maximum number of API requests a client can make to the server within a specific time period, defined in requests per second.
AuthenticationMode String "Authorization Code" AuthenticationMode specifies the method used to authenticate when connecting to Azure DevOps API.
CacheExpirationTime Integer 30 Defines the expiration time for cache. A value of 0 disables caching.
CertificatePassword String "" The password used to access the key store file.
ClientId String "" The client ID you have selected or created in Azure DevOps.
ClientSecret String "" The client secret you have selected or created in Azure DevOps.
ConcurrentWritingThreads Integer 1 The number of threads for executing operations in parallel. A value of 0 will disable multi threading.
ConnectionTimeout Integer 30 ConnectionTimeout is the maximum amount of time the program will wait to set up a connection to the Azure DevOps API.
ConnectionType String "" Connection Type refers to the connection methods we support for Azure DevOps. We support both online and on-premise modes.
Domain String "" Domain is the domain address we use to connect to the on-premise Azure DevOps.
IgnoreCertificateErrors Boolean false Specifies whether to verify the certificate when connecting to Azure DevOps. If certificate verification is not required, you can set this value to 'true'.
IgnoreError Boolean false Determines if the program continues executing SQL statements after encountering an error.
InstanceId String "" The InstanceId is required and allows you to specify the instance that should be targeted in requests made to the API.
LogFileSize String "10485760" A string specifying the maximum size in bytes for a log file.
LogLevel String "INFO" The logging level for the JDBC driver.
LogPath String "./jdbcLogs" The directory where log files are stored.
OemKey String "" The OEM license key.
Password String "" The password used to authenticate the user.
PathToCertificate String "" The file path where the keystore file for connecting to the Azure DevOps.
PathToTokenFile String "" PathToTokenFile allows you to specify the path to the token file on the file system.
Project String "" Project is the name of the Project we need to connect to.
ProxyMode String NoProxy This setting configures the proxy. Allowed values are "NoProxy", "AutoDetect" and "Manual".
ProxyPassword String "" The password to be used to authenticate to the proxy.
ProxyServer String "" The host of the proxy server.
ProxyServerPort Integer 0 The port of the proxy server.
ProxyUsername String "" The username to be used to authenticate to the proxy.
ReadBatchSize Integer 100 ReadBatchSize is used to set how many records can be read from Azure DevOps in a single call.
ResultPath String "" The path where the execution result files are saved.
RetryOnIntermittentErrors Boolean true The RetryOnIntermittentErrors parameter indicates whether to retry the connection when it might occasionally fail due to temporary issues.
SaveResult Boolean false The SaveResult parameter indicates whether to save the execution results to a file.
ServiceName String "" The ServiceName refers to the name of the service API selected by the user.
ServiceTimeout Integer 120 The ServiceTimeout is the timeout to receive the full response from Azure DevOps API.
ServiceUrl String "" Service URL is the Azure DevOps address that we connect to.
Suppress404NotFoundError Boolean true When set to true, if a query results in an HTTP 404 error, a result set will still be created. When set to false, an error is logged instead and no result set is created.
SubscriptionKey String "" The Subscription Key is required to authenticate and authorize API requests to Azure DevOps.
TenantId String "" The Azure Tenant ID used to access Azure DevOps.
TokenPassword String "" The password used to read the token file.
UserName String "" The user account used to connect to the server.
Version String "" Version is the API version we connect to.
WriteBatchSize Integer 1 WriteBatchSize is used to set how many records can be written to Azure DevOps in a single call.