Unified Language User Guides
iCR User Guide 5.0
iCR User Guide 5.0
  • Table of contents
    • Introduction
    • Overview
    • Authorizing Access to Your Source Code
      • Authenticating GitHub Cloud Access Using OAuth
      • Authenticating GitHub Cloud Access Using PAT
      • Authenticating GitHub Enterprise Access Using OAuth
      • Authenticating GitHub Enterprise Access Using PAT
      • Authenticating GitLab Cloud Access Using OAuth
      • Authenticating GitLab Cloud Access Using PAT
      • Authenticating GitLab Enterprise Access Using OAuth
      • Authenticating GitLab Enterprise Access Using PAT
      • Authenticating Bitbucket Cloud Access using OAuth
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your User Password
      • Updating your User Information
      • 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 Severity
        • Filter by Category
        • Filter by CWE
        • Filter by OWASP
        • Filter by Directory
      • 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
      • Comparing Analyses
      • Capturing results for printing or sharing
      • Ending a reviewer session
    • When you are complete
    • Integrating iCR Into Your CI/CD Workflows
      • Jenkins Workflow
        • Installing the plugin
        • Configuring the plugin
          • Creating a Personal Access Token
          • Copying Your Repository's URL
        • Viewing the Results
      • GitHub Actions Workflow
        • GitHub Actions Overview
        • Preparing the GitHub Workflow
          • Environment Variables
          • User Supplied Secrets
          • Setting the User Defined Secrets Values
        • Executing the Workflow
      • GitLab CI/CD Workflow
        • GitLab CI/CD OverView
        • Configuring the GitLab Script variables
          • Environment Variables
          • User Supplied Variables
          • Creating a Personal Access Token
          • Setting the User Defined Variable Values
        • Executing the Workflow
      • Multiple Workflows
    • Appendix – Language Specific Fixer Lists
    • Appendix - Sample Bug Listing
    • Appendix - Getting a BitBucket App Password for JENKINS
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 3 months 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.

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 icons are now available as they were for the non-local VCS case. The Review icon is grayed out until an analysis is complete and results are available for review.

The Integration icon supports working with the .

The Engine Log icon is there in the rare case that some error has occured during the analysis of your project. This icon allows you to capture the log from The Analysis Engine and send it to OpenRefactory in the event that further resolution of the failure is required.

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

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

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