iCR for Python User Guides
iCR for Python 3.0.2
iCR for Python 3.0.2
  • Table of contents
    • Introduction
    • Overview
    • Getting Started
      • Installing iCR for Python
      • Managing your service
        • Opening Ports
      • 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
          • Authenticating Bitbucket Access with a Private VCS Repository
          • Setting Bitbucket Server Credentials in the Navigator
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your private passphrase
      • 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
        • Setting the scope of your analysis
      • 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 Navigator
  3. Selecting Your Source Code

Using a local project

PreviousUsing a private VCSNextSetting the scope of your analysis

Last updated 1 year ago

You may choose to not access source code from a cloud-based repository. iCR for Python also supports accessing projects that are accessible directly on your server. Any of your developers may be given login access to your server. From a shell console, you can upload projects to it or, you may mount a network attached file system. In this case, it would need to be mounted as a subdirectory of your configured anchor point in the file system.

Selecting this option brings up the Select Project window on the left side of the screen. By default, it is anchored at /home.

However, you can reposition this anchor point using the icrforpython -d as noted earlier in . 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 Remove button allows you to drop this project from the list of available projects.

You can add as many projects as you wish.

The project has now been added to the list of locally accessible projects available for analysis. 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 . And the Version button allows you to specify the required Python library version needed for this local project.

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
Managing your service