Versions Compared

Key

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

...

Insert excerpt
FD65:FlexDeploy 6.5 Release Notes
FD65:FlexDeploy 6.5 Release Notes
namesubscribe
nopaneltrue

...

  • The version 0 REST API was removed.

  • The version 1 REST APIs for Applications, Test Instances, and Test Types are removed.

  • The version 1 REST API call to create or modify a release with a partial-deploy project has changed. See Release API

  • The version 1 REST API call to create a new snapshot for a release with a package-based project that takes all files should specify package name "(All Files)". See Release Snapshot API

  • The version 1 REST API call to build a project has changes to the input when building package-based projects, and returns a completely new response body. See Project API Build

  • The project Classification PartialDeployments was renamed to PackageBased which affects the version 1 Project REST API.

  • REST API /v1/project/{projectId}/stream/{streamId}/populate no longer supports sortAllAfterPopulate. Files are always sorted if necessary after discover (previously known as populate).

Projects and Deployment

  • Deployment to Test Instances (integration instance) is no longer supported. Customers can create additional Target Groups if deployment or Utility Execution on a Test Instance is necessary.

  • External Approvals with ITS are no longer supported. External Approvals with CMS continue to be supported.

  • Package-based projects previously supported building with files being selected, and without the need to create a named package. Now a named package is required.

    • Builds made previously without a package name will have a package name assigned to them when they are deployed.

    • Existing projects will have a package name “(All Files)” added to them on server startup to be consistent with how it looked when building all files without a package in previous versions of FlexDeploy. This package will be dynamic and includes all files (e.g. include path of “.*”).

  • Deployment Strategies are removed for container projects. New capability is planned in the future based on feedback received on the previous iteration.

  • Application-level deployment is removed.

    • Projects can still be deployed one at a time.

    • Release and Pipeline is the supported method of deploying an assortment of projects as a group.

...