An Integration represents an external technology instance integrated into FlexDeploy that is running in one or more Environments.
...
Source Control (Source Code Management) Instances - represent a source code management system such as Subversion, Git, TFS, CVS, etc. Holds properties necessary to authenticate. The paths to specific projects in the SCM are contained in the project instead so that the Instance can be used across many projects.
Testing Instances - represent a software test tool. Holds properties necessary to run tests, and allows the properties to be used wherever the test is run.
Issue Tracking System Instances - represent an Issue Tracking System. Currently JIRA, Redmine, Azure Boards, GitLab, and GitHub are supported out-of-box, and custom systems can be created. The settings on this Instance allow FlexDeploy to authenticate and manage tickets in the issue tracking system.
Change Management System Instances - represent a Change Management System. ServiceNow, Freshservice, BMC Helix Remedyforce, and Jira ITSM are supported out-of-box, and custom systems can be created. The configuration of this instance allows FlexDeploy to maintain change tickets in the change management system.
Cloud - represents various cloud accounts and providers. Currently AWS, Azure, OCI, and OIC providers are supported. The settings on this instance will allow FlexDeploy to access various cloud accounts setup for the providers from workflow plugin operations.
Containers - Accounts for container services like Docker and Kubernetes
Artifact Repository - Accounts for Nexus, Artifactory, or other Artifact Repositories
CI Server - Accounts for Jenkins or other CI tools
Analysis Tool - Accounts for Acunetix, Checkmarx, SonarQube, or other Analysis tools
Messaging - Accounts for Microsoft Teams, Slack, or other messaging tools
Other - Other account providers can be setup here.
Viewing Integrations
To view the list of Integrations defined within FlexDeploy, select the Topology from the menu and choose the Integrations tab.
...