iCR for Python User Guides
iCR for Python 3.5
iCR for Python 3.5
  • Table of contents
    • Introduction
    • Overview
    • Authorizing Access to Your Source Code
      • Authenticating GitHub Access with a Cloud-Based VCS Repository Service
        • Authenticating GitHub Access with a Private VCS Repository
      • Authenticating GitLab Access with a Cloud-Based VCS Repository
        • Authenticating GitLab Access with a Private VCS Repository
      • Authenticating Bitbucket Access with a Cloud-Based VCS Repository
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your User Password
      • The Navigator top banner
      • The Analysis Engine status
      • Selecting Your Source Code
        • Using a cloud-based VCS
        • Selecting your branch
        • Using a private VCS
        • Using a local project
        • Limiting the files to be analyzed
      • Integrating with your bug tracking system
        • Integrating with Jira - Define Your Project
        • Integrating with Jira - Authorizing Access for iCR
        • Integrating with Jira - Connecting with iCR
    • Using the Analysis Engine
      • Initiating an analysis
      • Monitoring the analysis
      • Interrupting the analysis
    • Reviewing your results
      • Reviewer summary and filters
      • Filter by Directory pane
      • Filter by Category pane
      • Reviewing a fix
      • Accepting a fix
        • Accepting a fix when integrated with your bug system
      • Rejecting a fix
        • Rejecting a fix when integrated with your bug system
      • Undoing a fix
        • Undoing a fix when integrated with your bug system
      • Rejected fix history
      • Providing feedback
      • Applying the fixes
      • Cases needing manual attention
      • Capturing results for printing or sharing
      • Ending a reviewer session
    • When you are complete
    • Appendix – List of supported fixers
    • Appendix – Example Summary Report
    • Appendix - Sample Bug Listing
Powered by GitBook
On this page
  1. Table of contents
  2. Using the Analysis Engine

Initiating an analysis

PreviousUsing the Analysis EngineNextMonitoring the analysis

Last updated 1 year ago

To begin the analysis of a project, you will have logged into your Version-Control System (VCS) such as GitHub, which is being used in our examples. You using your server’s Public IP address and port 3001. Once connected to the Navigator, you selected the project that you wanted to analyze, cloned it and then selected the branch that you wished to analyze (See ).

To begin the analysis of the branch, click on the Analyze button.

Smaller projects (< 100,000 Lines of Code) tend to be less complex in terms of number of files and functions. These may be analyzed within minutes. However, larger projects (> 1M LoC) may take much longer to analyze. That’s OK. You don’t have to sit and watch as it could take many hours for a large, complex project to be thoroughly analyzed.

Clicking the Analyze button gives you the option of requesting an email notification when the analysis completes. If you select the box requesting a notification, an email prompt is displayed. Enter the email to which iCR will address your notification.

To begin the analysis, click Yes. A new tab opens which takes you to the Monitor Analysis screen.

This display will be updated as the analysis progresses. The first step that the analysis undertakes is a check of the license. The license is used to authenticate this instance of iCR and manages the number of OBLoCs that are authorized for this instance. The Checking License Information step requires access to the Internet in order to reach the License Management software. This usually happens quickly and goes unnoticed. However, in some cases, if the Internet connection is a bit slower, you may occasionally see this progress message letting you know that the license checking process is still underway:

Once that step completes, the analysis is running.

connected to the Navigator
Authorizing Access to Your Source Code