Versions Compared

Old Version 1

changes.mady.by.user Karl Henselin

Saved on

compared with

New Version 2

changes.mady.by.user Victor Krieg

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

There are many types of Integrations:

  1. Source Control

...

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

  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

...

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

...

  1. Scan tools

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

  3. Other - Other account providers can be setup here.

Viewing Integrations

To view the list of Integrations defined within FlexDeploy, select the Topology select Integrations tab from the menu and choose the Integrations tabunder Configuration.

...

By default, all only active Integration instances are displayed in the search resultseach table in order of last updated on. To refine the search results, type all or part of the Integration instance name into the Search box, and the list will automatically filter. Select the Active checkbox to show the inactive Integration instances as wellyou can sort by each column in the tables as well as query the values in each column.

Creating or Editing Integrations

 Each Integration type has slightly different configuration requirements. The following links will assist in setting up Integrations.

Inactivating/Activating Integrations

To inactivate an Integration instance at any time, click the Active link Checkmark on the desired Integration instance in the table, and it will toggle to Inactive. This will hide that Integration instance after leaving the screen, until the Active checkbox is unchecked. To reactivate an Integration instance, click the Inactive link Icon and it will toggle back to Active.