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 Navigator
  3. Selecting Your Source Code

Using a private VCS

PreviousSelecting your branchNextUsing a local project

Last updated 1 year ago

As introduced in , you may be using a locally deployed version of your VCS. Continuing to use GitHub as the example, here is how you set up to review repositories managed by GitHub Enterprise. If you are using GitLab Enterprise as your local VCS, refer to for details on how to configure it for use with the Navigator.

This will bring up the window showing all of the private repositories that you may have configured. In our example, this will be the very first GitHub Enterprise server to be configured. So, the list of current servers is empty.

This brings up the configuration window where you set up the entries needed to locate the server and authenticate it with your OAuth credentials.

Set the name to anything you like. In this example we’ll call it “Private GitHub”.

Then, insert your URL to your private GitHub Enterprise Server. For our example, we have created a URL named vcs3.openrefactory.com. Note that you must add the https:// prefix to the URL to reach your server properly.

Once the credentials are set, you may use that private repository by re-selecting GitHub Enterprise from the Select Repository pull-down menu. You will now see the display of all available private repositories. In our example here, you will see the one we just added: Private GitHub.

To see all of the repostiories on that Enterprise server, click on Get Repos to tell the Navigator to fetch all of the repositories associated with the currently logged in user to that private Enterprise server.

For our example, we have already loaded django, our test project, there.

Finally, from the OAuth setup described in , you created a new Client ID and Secret key. Copy those from that window and paste them here.

From here, everything works the same as outlined in .

Authenticating GitHub Access with a Cloud-Based VCS Repository
Selecting your branch
Authenticating GitHub Access with a Private VCS Repository
Authenticating GitLab Access with a Private VCS Repository