An Integration represents an external technology instance integrated into FlexDeploy that is running in one or more Environments. Credential Stores and Providers can now be found under integrations as well.

...

1. Source Control Repositories - 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.

2. 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.

3. 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.

4. 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.

5. Credential Stores - represent an instance of specific type of credential store provider. You can have many such credential stores in FlexDeploy of same or different type. There is one credential store created by default, which is named Local. If you are migrating from previous version of FlexDeploy, you will also notice migrated credentials under Local credential store.

6. Cloud - represents various cloud accounts and for various providers. Currently AWS, Azure, OCI, and OIC A number of providers are supported . The settings on this instance will out of the box. Custom cloud providers can also be created. Cloud Accounts allow FlexDeploy to access various cloud accounts setup for the providers from workflow plugin operationsclouds, platforms, and tools during workflow executions.

7. Containers - Accounts for container services like Docker and Kubernetes

8. Artifact Repository - Accounts for Nexus, Artifactory, or other Artifact Repositories

9. CI Server - Accounts for Jenkins or other CI tools

10. Scan Tool - Accounts for Acunetix, Checkmarx, SonarQube, or other Scan tools

11. Messaging - Accounts for Microsoft Teams, Slack, or other messaging tools

12. Other - Other account providers can be setup here if they don’t fit well in another category.

Viewing Integrations

There are 2 permissions associated with the integrations page. It is recommended that if a a group has permission to Integration Providers, the group should also be given permission to Integration Instances.

...

To view the list of Integrations defined within FlexDeploy, select Integrations tab from the menu under Configuration.

...

By default, only active Integration instances are displayed in each table in order of last updated on, and the data is ordered by updated on with the most recent on top. To refine the results, you can sort by each column in the tables as well as query the values in each column.

...

• SCM Integration

• Test Integration

• Issue Tracking Integration

• Change Management Integration

• Credential Store and Provider

• Cloud Account and Provider

• Container Account and Provider

• Artifact Repository Account and Provider

• CI Server Account and Provider

• Scan Tool Account and Provider

• Messaging Account and Provider

Refer to to the Creating/Editing an Account and Provider page for more details for managing accounts and providers.

Inactivating/Activating Integrations

...