iCR Workflow Integration Guide
WebTry iCR
CI/CD Workflow 3.0
CI/CD Workflow 3.0
  • Table of contents
    • Introduction
    • Jenkins Workflow
      • Installing the plugin
      • Configuring the plugin
        • Creating a Personal Access Token
        • Copying Your Repository's URL
      • Viewing the Results
    • GitHub Actions Workflow
      • Workflow Overview
      • Preparing and Registering the Docker Image
        • Adding a Workflow to a Repository
      • Preparing the GitHub Workflow
        • Environment Variables
        • User Supplied Secrets
        • Setting the User Defined Secrets Values
      • Executing the Workflow
    • GitLab Workflow
      • Workflow Overview
      • Preparing the Docker Image
      • 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 A - Getting a BitBucket App Password for JENKINS
Powered by GitBook
On this page

Was this helpful?

  1. Table of contents
  2. GitLab Workflow
  3. Configuring the GitLab Script variables

User Supplied Variables

PreviousEnvironment VariablesNextCreating a Personal Access Token

Last updated 1 year ago

Was this helpful?

These variables are provided by the DevOps engineer who is developing the workflow. They are needed in order to identify the iCR server to be used for analysis and its accompanying configuration parameters. They are:

  1. OR_ICR_URL Provide the URL to the location of the iCR server to be used for the analysis and review. Using examples from the Private Platform User Guide, the `url` would look like:\   `https://3.237.77.219:3001`\ where 3.237.77.219 is the IP address of the iCR server and 3001 is the TCP port that the Navigator uses.

  2. OR_PASSPHRASE ``Entry into the Navigator is protected using a passphrase. This is the same passphrase that is used to enter the Navigator as described in Section 4.1 of the Private Platform User Guide.

  3. OR_LANGUAGE_VERSION ``With some languages that are analyzed by iCR, such as Python, the specific version of the language or related libraries needs to be specified in order for iCR to work correctly for the target source. For example, if you are using Python 3.7, then the string 3.7 is assigned.

  4. OR_SECRET_TOKEN ``To authorize the workflow to operate upon the project on behalf of a specific user, that workflow needs to supply a (PAT) that authorizes access to their repositories.

  5. OR_MAIL_ADDRESS ``When the analysis triggered by this workflow completes, the User, upon whose behalf this analysis was performed, will receive an email notification letting them know it is complete. That User’s email will be entered here. An email address MUST be provided to allow a way for iCR to notify the User in the event of either success of some kind of failure. If no address is provided the workflow will not proceed.

Personal Access Token