CI Job Results
Last updated
Last updated
The CI Job Results screen will display the list of builds triggered for your CI Jobs to date. In addition, you can even trigger a new build or find detailed build info for your existing jobs, such as build status, log reports, author details, etc.
Hover your mouse over the nCino module and click on CI Jobs.
By default, you will be redirected to the Job Results tab; if not, click on the Job Results tab. The list of CI job builds will display in reverse chronological order; the newest will display on the top of the list.
To trigger a new build for your CI Job, follow the below steps:
From the CI Job Results screen, select your job from the All Jobs dropdown field. The dropdown here allows switching between the CI Jobs created.
If no build is created yet, 'No builds exist' gets displayed, or if the build is already triggered for the job and you wish to trigger another build, click on Build Now besides your selected job.
The left side on the next screen will have summary details of your CI job configured, i,e., job label, source/destination org, deployment method chosen, etc.
Under the Build inputs section, enter the title of the build and add comments, if any.
Choose the Deployment Type:
Commit and Deploy: Both commit and deployment will undergo if chosen
Deploy only: Deployment happens to the selected destination org only.
Commit only: Committing the changes to the version control branch only.
Add any additional information in the Notes section. However, this is optional.
Click on Trigger Build. It will validate the user credentials, and the build will get triggered upon successful validation.
You'll be redirected to the Job Results main screen, where you can find your recently triggered build status.
From the CI Job Results screen, click on the CI Job from the list to view the build details or use the All Jobs drop-down to look for your job.
or,
From the list of build lists triggered, look for the build for which you want to see the log and object details. Click on the build once you found it.
For each template deployed, the Data tab will list all the nCino objects committed or deployed, along with the success/fail count.
Click on the object to view its detailed object information displayed on the right side of the screen.
The number of records successfully deployed or failed to deploy can be seen under the Success/ Failed tab.
To view the detailed object records that were successfully deployed or failed to deploy, click on the number link (under Success or Failed).
Post-Deployment Activities: The post-deployment activities information is displayed on this tab. If you have selected more than one Salesforce org as your destination, select the respective org from the Salesforce Org drop-down to view the detailed success/failure objects count.
Point to Note:
A maximum of 5 Salesforce Orgs will be considered for post-deployment activities. For multiple Salesforce Orgs opted, the post-deployment activities will be carried out sequentially, meaning the next post-deployment activities will be carried out only if the current post-deployment activities are done.
The success or failure detailed object records can be seen only if the post-deployment activities are successfully carried out for all of the Salesforce Orgs.
Now it's easy to download the backup snapshot of the CI Jobs as required. You can go to the respective CI job and download the backups of the templates all at once or individually.
Go to any CI Job.
Click on any template available under the build.
On the template page, you will see the download option available for each object.
Open the CI Job, then hover over the three dots at the far right of the banner as shown below.
Click on the “Build Changes” option.
You will be redirected to a “Build Changes” page.
On the “Build Changes” page, click on the “Download” button to download all the templates from that build.
You can see the files downloaded.
Commit Workspace: When various commits are deployed to a branch, the queue commits will be mentioned here. The main concept of introducing the commit workspace is to allow parallel commits to the same version control repository/branch.
Deployment Workspace: View the ongoing deployment process by clicking on the Deployment Workspace icon on the right side of the page.
Filter by Job Name/ Build Number: Filter the builds by CI job label name and the build number.
Triggered By: Filter the builds by the author.
Filter by Created/ Modified Date: If you want to view job lists that get authored between any two dates, use the 'From Date' and 'To Date' to narrow down the list of build lists.
Filter by Build Label Name: Filter the builds by build label name.
Filter by Build Status: Filter the list based on build status, i.e., success or failed.
Filter by Deploy Status: Filter the build via deployment type, i.e., commit and deploy or deploy or commit.
The Log tab contains the detailed report of the commit/deployment performed. Each commit/deployment has several "steps," which contain a subset of logs; such logs can be seen here. You can view complete log information in the user interface or save it to your local machine usingicon. The file usually gets downloaded in ZIP format.
