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. GitHub Actions Workflow

Executing the Workflow

With the iCR container registered in the User’s registry and linked with the intended repositories, the .github/workflows/main.yml script copied into those repositories, and the relevant user supplied secrets defined for each repository, the workflow is ready to be used. The DevOps engineer can edit the main.yml script to add triggering events such as responding to a new commit, or as the result of a routine timer.

Once the analysis is initiated by the iCR container, the workflow does not wait for the analysis to complete. Analysis for larger projects may take many hours so it does not make sense to monitor the workflow to wait for it to complete.

Rather, once initiated, the workflow moves on and the analysis runs until it completes. When done, the email address specified in the MAIL_ADDRESS secret is sent a summary of the analysis as described in the Private Platform User Guide.

Upon receiving notification of completion, any User who knows the access passphrase to the specified iCR server may connect to the Navigator there and process results. Of course, if a User connects while an analysis is in progress, the User will see that the engine is busy so a new analysis may not be started manually.

PreviousSetting the User Defined Secrets ValuesNextGitLab Workflow

Last updated 1 year ago

Was this helpful?