Azure DevOps Pipeline is a web service that is used to build, test, and run code projects automatically. Azure DevOps Pipeline extension can now be installed in Zoho Sprints. This installation lets you carry out actions in items, sprints and releases from Azure DevOps Pipeline. It also lets you map builds to work items in Zoho Sprints and view pipeline build details.
Note: Troubleshooting Azure DevOps pipeline runs by configuring verbose logs or HTTP trace logs will result in sensitive information recorded in the log files. Please do not share them with anyone.
Configure Azure DevOps Pipeline extension for cloud and server
To configure the extension:
- Click the gear icon at the top-right. The settings window will appear.
- Click Others under Marketplace section. The listing page will appear.
- Click Configure under Azure DevOps Pipeline extension.
- Select the Project and Accessibility controls and click Install Now.
- Enter the Domain/Host URL.
- Provide your Azure DevOps Organization name (Collection Name, if it is Azure DevOps server).
- Click Save & Next.
- Authorize the connections and triggers. While authorizing the Azure DevOps Connection, generate the Personal Access Token from Azure DevOps by using the scopes mentioned below:
- Build.Read
- Code.Read
- Project and Team.Read
- Extensions.Read&Manage (Portal owner only)
- Service connections. Read, query & mange (Portal owner only)
- Choose the projects to be associated from Azure DevOps. In case of server, select one project because Azure has an API restriction in place.
- Click Associate. The selected projects will be mapped.
When you install the Azure DevOps Pipeline Extension, the Zoho Sprints extension in Visual Studio gets installed automatically. The latter should not be installed directly from the Visual Studio marketplace. The Zoho Sprints Task actions can be carried out only for the associated projects.
Azure Authorization behavior
Azure DevOps integration for cloud and server vary due to the API restrictions imposed by Azure. For cloud based account, you can associate up to 5 projects. The behavior is not the same for server based account.
For a server based account, you can only associate one project due to the API restriction. However, during installation, the first project that you selected will get associated despite selecting multiple projects, completing the installation process. But the authorization for the integration would be removed. So, when you try to associate projects following the first instance, Azure would consider the request as unauthorized access and you would be redirected to the authorization page. You need to reauthorize to restore the integration.
Common task parameters in Azure DevOps Pipeline
Once the installation is successful, you can Create and Update work items, sprints and releases from your Azure DevOps pipeline in Zoho Sprints. You can refer to the list below to know about the format in which the data has to be entered. Click here to take a look at the gif to retrieve that data.
Field
|
Type
|
Project Number
|
Number
|
Sprint Number
|
Number
|
Item Number
|
Number
|
Release Number
|
Number
|
Date
|
2022-05-20T00:00:00Z (UTC Format)
|
Tasks
- Add a Feed Status in Zoho Sprints
- Add an Item comment in Zoho Sprints
- Add a Sprint comment in Zoho Sprints
- Complete a Sprint in Zoho Sprints
- Create an Item in Zoho Sprints
- Create a Release in Zoho Sprints
- Create a Sprint in Zoho Sprints
- Start a Sprint in Zoho Sprints
- Update an Item in Zoho Sprints
- Update a Release in Zoho Sprints
- Update a Sprint in Zoho Sprints
For the extension to work, it needs to be enabled from Zoho Sprints. Once the Azure DevOps Pipeline is installed in Zoho Sprints, Zoho Sprints extension gets automatically installed in your Azure organization.
Task Parameters
Work Items in Zoho Sprints
The following are the fields you'll encounter while you create or update work items from your Azure DevOps Pipeline task.
- Project: Provide a Project Number
- Sprint: Specify the Sprint number (0 means Project Backlog)
- Item Number: Provide the Item number of the item in which the fields need to be updated.
- Name: Enter the name of the work item
- Description: Describe your work item
- Status: Specify the status of the work item
- Type: Specify the work item type, e.g.,Task
- Priority: Set the work item priority, e.g., High
- Start Date: Specify work item start date, e.g., 2022-08-13T00:00:00Z
- End Date: Specify the work item end date. It should be greater than the start date, e.g., 2022-09-13T00:00:00Z
- Item Assignee: Provide the email addresses of the item users (separated by commas)
- Estimation points: Mention the index of the estimation points set for the item, e.g.,The index of 2 in a Fibonacci estimation type is 2 and the index of 8 will be 5.
- Comment: Type the comment to be added for that work item
- Duration: Time spent on that work item,e.g., 2hrs 50min
- Custom Fields: Specify the custom field values here. If there are multiple custom fields, they should be mentioned in a new line.
- Example
- UDF1_BOOLEAN=123456
- UDF1_TEXT=text value
Sprints in Zoho Sprints
The following are the fields you'll encounter while you create,update, start or complete sprints from your Azure DevOps Pipeline task.
- Project: Mention the project number.
- Sprint: Mention the sprint number.
- Sprint Name Provide a name to the sprint.
- Description: Describe the sprint
- Scrum Master: Mention the email address of the scrum master
- Sprint Users: Provide the email addresses of the sprint users (separated by commas)
- Start Date: Specify the sprint start date, e.g., 2022-08-13T00:00:00Z
- End Date: Specify the sprint end date, e.g., 2022-08-13T00:00:00Z
- Duration: Mention a tentative duration of the sprint. A sprint duration cannot exceed 8 weeks when strict scrum is enabled. And if strict scrum is disabled, it can last up to 30 weeks, e.g., 2hrs 50min
- Comment: Type the comments to be added to that sprint
- Custom Fields: Specify the custom field values here. If there are multiple custom fields, they should be mentioned in a new line.
- Example:
- UDF1_BOOLEAN=12345
- UDF1_TEXT=text value
Releases in Zoho Sprints
The following are the fields you'll encounter while you create or update releases from your Azure DevOps Pipeline task.
- Project: Enter the project number
- Release Name: Provide a name to the release
- Release Goal: Describe the purpose of release
- Start Date: Enter the starting date of the release, e.g., 2022-08-13T00:00:00Z
- Release Date: Enter the release date, e.g., 2022-10-13T00:00:00Z
- Owners: Mention the email address of the owner separated by commas
- Release Stage: Specify the stage in which the release is currently in, e.g., PLAN
- Custom Fields: Specify the custom field values here. If there are multiple custom fields, they should be mentioned in a new line.
- Example:
- UDF1_BOOLEAN=12345
- UDF1_TEXT=text value
Associate build from Azure DevOps
- Navigate to the details page of a work item in Zoho Sprints.
- Click the Azure DevOps Pipeline icon on the right corner.
- Click Associate Build button.
- Enter the preferred criteria.
- Click Find.
- Choose the build(s) to be associated and click Associate.
View Azure DevOps Pipeline's build status
To check the Azure DevOps pipelines:
- Sign in to Zoho Sprints.
- Select CI/CD view from the left navigation panel.
- Select Azure DevOps Pipeline.
- Hover and click the View Log. You can view the logs of each pipeline by clicking the View Logs button.
- These pipelines can also be viewed based on a particular criteria. Click on the top right corner, set the criteria and click Apply Filter.
Disable extension
To disable the plug-in temporarily:
- Click the gear icon at the top-right. The settings window will appear.
- Click All under Marketplace section. The listing page will appear.
- Find Azure DevOps Pipeline for Zoho Sprints.
- Click Disable. The extension will be disabled.
Uninstall extension
To uninstall:
- Click the gear icon at the top-right. The settings window will appear.
- Click All under Marketplace section. The listing page will appear.
- Find Azure DevOps Pipeline for Zoho Sprints.
- Click Uninstall. The extension will be uninstalled and configuration will be removed.