Software businesses across the globe is mostly automated. As the customer requirements pile up, the development and operations need to deliver outcomes in rapid phases. If you are an agile team, no wonder that your deliverables are quite frequent and you definitely need a Devops tool for an organized and timely deliverable.
Available Plan: Starter, Elite, Premier and Zoho One
Why Jenkins integration for Zoho Sprints?
When it comes to CI/CD (continuous integration/continuous deployment), Jenkins is the top-notch automation tool that befriends developers and makes the build updates clutter-free. Implementing your agile team's work through a steady integration with
Jenkins helps your to perform the following operations right while you work with different cases in your pipeline.
- Directly add work items to your projects via Jenkins.
- Automatically update your work item's progress across the destined status and priority.
- View the build logs for each work item on its details page.
- Add comments to your work items or sprints directly from Jenkins.
- Upload the build log file to the work items from Jenkins.
- Add feed status for every build update from Jenkins.
Your development related work items can be run directly from Jenkins and you can track them in Zoho Sprints.
Enable integration from Zoho Sprints
- Navigate to Setup in the upper-right corner.
- Navigate to Marketplace > Others.
- Hover over Jenkins app and click Configure.
- Accept the Terms & Conditions and then click Enable Now.
- Navigate to your Jenkins account.
- Select Manage Settings in the left panel.
- Click Configure System.
- Navigate to Sprints Connection.
- Enter the Connection Name, Sprints Team URL, Sprints Team Admin Mail ID, and select Sprints API Token (Sprints Client to connect).
- Click Add and select Jenkins.
- Select the Kind as Sprints API Token.
- Click Generate Authentication Token in Zoho Sprints to generate the refresh token.
- Copy and paste the Client ID, Client Secret, and Redirection URL from Zoho Sprints.
- Click Authenticate and Migrate.
Note: Click Authenticate and Migrate to configure and to migrate the existing builds from Jenkins to Zoho Sprints.
Build actions in Jenkins
Update item status from Jenkins
- Sign In to your Jenkins account.
- Navigate to the Build.
- Click Configure from the left menu.
- Select Add build step under the Build section.
- Click [Zoho Sprints] Update Item Status.
- Prefix: Enter the relevant project and item ID here. Example: P1#I10 (P1 - Project number, I10 - Item number). If there are multiple items to be updated, you can specify them like: P1#I10, P#I11, P#I12, P2#I136.
- Move to Status: You can enter the relevant status name.
- Save and Apply your changes.
- Click Build Now to trigger the API.
Note: You can change the status of the work items only in the active sprint.
Update item priority
- Sign In to your Jenkins account.
- Navigate to the Build.
- Click Configure from the left menu.
- Select Add build step under the Build section.
- Click [Zoho Sprints] Update Item Priority.
- Prefix: Enter the relevant project and item ID here. Example: P1#I10 (P1 - Project number, I10 - Item number). If there are multiple items to be updated, you can specify them like: P1#I10, P#I11, P#I12, P2#I13.
- Move Priority To: Enter the priority name as defined in Zoho Sprints.
- Save and Apply your changes.
- Click Build Now to trigger the API.
Add feed status
You can directly add a status on your project feed right from Jenkins.
- Sign In to your Jenkins account.
- Navigate to the Build.
- Click Configure from the left menu.
- Select Add build step under the Build section.
- Click [Zoho Sprints] Add feed status.
- Prefix: Enter the project ID here. Example: P7. The status will be posted in the project's feed.
- Status: Enter the content for your status in this section. Note: All the script related information will be automatically removed.
- Save and Apply your changes.
- Click Build Now to trigger the API.
You can add a comment to your sprint or work item from Jenkins.
- Sign In to your Jenkins account.
- Navigate to the Build.
- Click Configure from the left menu.
- Select Add build step under the Build section.
- Click [Zoho Sprints] Add comments to item.
- Prefix: Enter the relevant project ID along with the Item ID. Example: P7#I10 .
- Add comment: Enter your comment for the item here.
- Add attachment: If you would like to attach the log files of your build, you can choose Yes, add. The build log file will be attached to the relevant item's comment.
- Save and Apply your changes.
- Click Build Now to trigger the API.
Update Release Stage
- Sign In to your Jenkins account.
- Navigate to the Build.
- Click Configure from the left menu.
- Select Add build step under the Build section.
- Click [Zoho Sprints] Update Release Stage.
- Prefix: Enter the relevant project and release ID here. Example: P1#R10 (P1 - Project number, R10 - Release number).
- Enter the stage to which you'd like to update the release.
- Save and Apply your changes.
- Click Build Now to trigger the API.
Associate Items to Release
- Sign In to your Jenkins account.
- Navigate to the Build.
- Click Configure from the left menu.
- Select Add build step under the Build section.
- Click [Zoho Sprints] Associate Item(s) to Release.
- Prefix: Enter the relevant project and release ID here. Example: P1#R10 (P1 - Project number, R10 - Release number). Multiple Items can be mapped to a single release.
- Item to Map: Enter the prefix of your Item ID to map.
- Save and Apply your changes.
- Click Build Now to trigger the API.
Note: A maximum of 15 items can be mapped.
Add New Release
- Sign In to your Jenkins account.
- Navigate to the Build.
- Click Configure from the left menu.
- Select Add build step under the Build section.
- Click [Zoho Sprints] Add New Release.
- Project Prefix: Enter the relevant project number here. Example: P1(P1 - Project number).
- Item Prefix: Enter the prefix of the items that will be associated to the release.
- Description: Add a description to your release.
- Stage: Choose the stage of the release.
- Release Owner: Enter the email address of the release owner.
- Release Time (In Days): Enter the number of days required for the release.
- Save and Apply your changes.
- Click Build Now to trigger the API.
Note:
- The stage should not be 'completed'.
- Release Time should be a minimum of three days.
Release Details
This page displays the name of the job and the build along with the name of the person who initiated it and the time, the name of the branch, the status of the build, and the total duration. You can also view the build details. It also displays the total number of work items involved. You can even add new work items here.
Post build actions in Jenkins
Create new item
You can create a new work item to your backlog or sprint in your Post Build from Jenkins.
- Sign In to your Jenkins account.
- Navigate to the Build.
- Click Configure from the left menu.
- Select Add post-build action under the Post-build Actions.
- Choose [Zoho Sprints] Create New Item.
- Prefix: Enter the prefix. Example: P8#S4 (P1 - Project ID, S2 - Sprint Number) or P8#S0 (P8 - Project ID, S0 - Backlog ID) .
- Item Name: Input your work item name.
- Item Description: Enter description for your work item.
- Assign Item To: Enter the email address of the portal user here. Note: The user should be in an active status. If the user hasn't confirmed his email address or is inactive, then the user will not be added as an assignee.
- Item Type: Choose Task or Bug. Note: You can only add the item types: Task or bug.
- Add Attachment: Choose Add Log File to add the build log file as an attachment to your item.
- Save and Apply your changes.
- Click Build Now to trigger the API.
You can perform the other actions like status and priority update, adding feed status and comment to work item in your post build actions.
Create item on build failure
On build failure, you can automate and create a new work item.
- Sign In to your Jenkins account.
- Navigate to the Build.
- Click Configure from the left menu.
- Select Build Environment.
- Choose [Zoho Sprints] Create Item on Failure.
- Prefix: Enter the prefix. Example: P8#S4 (P1 - Project ID, S2 - Sprint Number) or P8#S0 (P8 - Project ID, S0 - Backlog ID) .
- Item Name: Input your work item name.
- Item Description: Enter description for your work item.
- Assign Item To: Enter the email address of the portal user here. Note: The user should be in an active status. If the user has not confirmed his email address or is inactive, then the user will not be added as an assignee.
- Item Type: Choose Task or Bug. Note: You can only add the item types: Task or bug.
- Add Attachment: Choose Add Log File to add the build log file as an attachment to your item.
- Save and Apply your changes.
- Click Build Now to trigger the API.
If you choose to upload the build log file, it gets reflected in the 'Attachments' section in your work item.
Build Details in Zoho Sprints
View build updates
You can track all the build updates made in Jenkins from your Zoho Sprints team.
- Click the Jenkins Icon from the top panel.
- View all the Build updates against each jobs.
- Click the search icon next to Job Name to search for a relevant job.
- Click Customize Column and set visibility for the required fields.
- Click the logs next to the Last Success and Last Failure columns to view the Logs, Actions, and Activity of the build.
Did you know?
Log: All the build logs that are triggered in your Jenkins build.
Action: Action tab contains the new work items created by the build.
Activity: Activity contains the list of streams that are triggered in the build.
View build details
You can track your build details for individual jobs.
- Click View Details next to the relevant Job Name.
- Search for the Build Name.
- Click View Build Details to view the Logs, Actions, and Activity of your build.
- Click Customize Column and set visibility for the required fields.
Filter build details
You can filter the build details anytime.
- Click the Filter icon at the top right corner.
- Select the different criteria - Build Duration, Waiting Time, Build On, Build Status, and Triggered By.
- You can also search for the particular user who triggered the build by searching for the user name.
- Click Apply Filter.
Export build details
You can also export your build details to XLS or CSV files.
- Click the Jenkins Icon from the top panel.
- Click View Details against the relevant Job Name.
- Click the Filter icon and select Export in the top right corner.
- Choose the Format of your export file and select the other criteria for your export.
- Click Export.
Note: Click Export History to view all the past exports.
Jenkins and Build Reports
You can view a detailed report on your build in Zoho Sprints.
Types of reports:
- Jenkins Reports: Tracks the user and job based report.
- Build Reports: Tracks the build by status and job.
Jenkins - User based report
Jenkins user based report will track the number of builds triggered by each user in a particular job.
- Navigate to Jenkins in the top panel.
- Click View Reports in the right corner.
- Select User Based Reports in Jenkins Report.
- Hover over a particular user to view the relevant Job Name, Count (No. of build triggered by the user) .
- Select View By in the right corner and choose your report from: This Week, Last Week, Today, 1 Hour, 6 Hours, and 12 Hours.
- Click Export next to View By to export your report.
Benefits:
- Track the users who have triggered a maximum build in a particular job.
- Track the job that has taken a maximum build updates.
- Track the performance of all the users in your job.
Jenkins - Job based report
Jenkins job based report will track the number of builds triggered for each job based on the default build status:
Building, Success, Failure, Aborted.
- Navigate to Jenkins in the top panel.
- Click View Reports in the right corner.
- Select Job Based Reports in Jenkins Report.
- Hover over a particular job to view the count of builds and their status.
- Select View By in the right corner and choose your report from: This Week, Last Week, Today, 1 Hour, 6 Hours, and 12 Hours.
- Click Export next to View By to export your report.
Benefits:
- Track the job that takes a maximum number of builds.
- Track the number of failed builds and schedule a scrum meeting to discuss the setbacks.
- Track the build success on an average of 1 week and plan for future build updates.
Build reports
Build reports help you track the count of builds in each status and the build count in each job. You can view the build reports by status and job.
- Build report by status: Track the number of builds in each status.
- Build report by job: Track the number of builds triggered for each job in Jenkins.