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

Multiple Workflows

It is commonplace for a development team to create multiple workflows for various projects. Each workflow may include an iCR build step. The iCR server named in these multiple workflows may refer to distinct iCR servers. Or some may refer to the same one.

The Navigator will receive these multiple events requesting the initiation of an analysis. When multiple events are triggered, either from a Jenkins or a GitHub workflow, the Navigator will queue them up and initiate them in the order that they were triggered. If the delays waiting for analyses to complete are too long, it may indicate the need to add additional iCR server instances in the Development Operations plan.

PreviousExecuting the WorkflowNextAppendix A - Getting a BitBucket App Password for JENKINS

Last updated 1 year ago

Was this helpful?