Unified Language User Guides
iCR User Guide 4.0
iCR User Guide 4.0
  • 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
    • When you are complete
    • Appendix – Language Specific Fixer Lists
    • Appendix – Example Summary Report
    • Appendix - Sample Bug Listing
Powered by GitBook
On this page
  1. Table of contents
  2. Using the Navigator
  3. Selecting Your Source Code

Using a local project

PreviousUsing a private VCSNextLimiting the files to be analyzed

Last updated 1 year ago

In some development environments you may not be able to access source code from a cloud-based repository. iCR also supports accessing projects that are accessible directly on your server. With the help of an administrative user, projects may be uploaded to the local file system of the server.

Selecting this option brings up the Select Project window on the left side of the screen. iCR uses a default anchor point of /home for local projects. If projects need to be reached from a different acess point, please contact your administrator to have them help you locate the local projects.

From the Select Project frame, you can scroll down through directories and subdirectories looking for the desired project for analysis.

In this example, we will select a project called django which is located within the directory python-projects (which is displayed as the Base Directory Path).

The project has now been added to the list of locally accessible projects available for analysis.

The Remove button allows you to drop this project from the list of available projects.

You can add as many projects as you wish.

Notice that once the project is added, the icon: appears next to the project name. This option works exactly the same as the mono-repo icon described in . It allows you to select a subdirectory of the source code to narrow the scope of your analysis of this local project. See the description in for more details.

Note that the Analyze, Review and Remove buttons are now available. The Review button is grayed out until an analysis is complete and results are available for review. The Integration button supports working with the . If you happen to be working in Python, the Version button allows you to specify the required Python library version needed for this local project as shown in the example below:

Note: If you choose to remove a project, ALL OF ITS RESULTS will also be deleted. This includes ALL of the .

Jira bug tracking system
history of Rejected bugs
Selecting your branch
Selecting your branch