Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Did you know you can subscribe to updates to the release notes? Right-click and copy this link and paste it into your feed reader of choice.

Known issues

  • None

Launch Webinar Recordings

FlexDeploy 9.0.0.0 (11-02-2024)

Version Details

Application Updates

Platform Update

FlexDeploy 9.0 application supports Java 17 and 21. Plugins will continue to support various Java versions similar to FlexDeploy 8.0.

Automated Rollback

  • Support for rolling back deployments has been added for Standard and and Package-based project level deployments.

  • Standard project rollback will deploy a previous build version to a given environment. User can override version to be deployed if necessary.

  • Package-based project rollback will build rollback package and deploy each file from the chosen Rollback Source Type:

    • Project Version - Source from a previous project version artifact.

    • SCM Revision - Retrieve from the project's configured source control system.

    • Rollback Project File - Select a different project file to build and deploy to roll back. Rollback file is retrieved from project’s source control system. This is project file attribute and can be defaulted as necessary by providing groovy scripts. For example, if file is Fil1.sql then Rollback file can be R_File1.sql. Customers can implement as necessary.

    • Backup Repository - Restore from a previous backup version. Backup repository must be enabled for this option. See plugin guides to see which plugins support taking backups automatically.

    • Rollback Source Type is a project file attribute which can be defaulted from a Groovy script entered on the Project Types screen.

  • Rollback execution history, including linked executions and files, can be easily viewed from the Project Execution page, as well as globally from reports.

GIT Integrations

  • Advanced Git Integration via OAuth applications.

    • Mass create integration instances by inspecting available git repositories for the user.

      • Automatically create repository webhooks and FlexDeploy webhook configuration for building projects and syncing branches

    • Automatically create and delete remote branches when performing actions in FlexDeploy.

    • Inspect repository contents when providing Sparse Folder Checkout script.

  • New Projects Commits page

    • View a list of commits on the project and see the highest environment they have been deployed to.

    • A commit details page to show

      • Pull requests for a commit

      • Commit changes (including code changes)

      • Commit timeline

  • FLEXDEPLOY-12153 - GIT Source Control Integration Instances can now use SSH Type credentials to connect via SSH protocol.

Credentials

Credentials are now updated to support different types. These new types are Secret Text, SSH Key, and Certificate.

  • Secret Text

    • Has an input for text that will be encrypted. These are commonly associated with passwords and is the standard credential type we have supported in the past.

  • SSH Key

    • Supports a private key file upload and an optional input for a passphrase.

    • These type of Credentials are generally associated with connecting to endpoints and authenticating with GIT.

    • Endpoints configured with Private Key and optional Passphrase prior to FlexDeploy 9.0 will be migrated to store Private Key with optional Passphrase in Local Credential Store.

    • SSH Key credentials are now also supported with Git source control instances.

  • Certificate credentials will support a certificate file upload and an optional password.

Configuration Export Import

  • FlexDeploy Configuration Export/Import allows Projects and Workflows to be seamlessly migrated between 2 separate FlexDeploy servers.

  • Individual projects and / or workflows can be exported from the source FlexDeploy server as a zip file. This zip file can then be uploaded in the target FlexDeploy server to migrate these projects and workflows over.

  • This feature works when creating or updating projects and workflows on target server.

WebSocket

Several FlexDeploy screens now leverage WebSocket, as opposed to traditional poll mechanism using REST APIs, to both improve UI responsiveness and reduce network traffic. This change has been made on the following screens:

  • Project Execution List

  • Execution Workflow Steps

  • Execution Plugin Logs

  • Release Dashboard

Release and Pipeline Management

  • FLEXDEPLOY-13075 - Snapshot inputs are now displayed in the order they were created when shown in the UI.

Integrations

  • FLEXDEPLOY-12475 - Integration provider properties now use the Field Data Type (Text Field, Date Time etc.) that is used on other custom property definitions.

Security

  • FLEXDEPLOY-8873 - Pipeline security permissions can now be overridden at individual pipeline level to allow for finer-grained access to pipeline management when necessary. Additionally, Bulk Update Permissions is available to simplify the update of permissions on more than one pipeline.

  • Active Directory / LDAP Realm and Email passwords are now migrated to Local Credential Store.

  • FLEXDEPLOY_12040 - Updated Joda Time to resolve vulnerability CVE-2024-23080.

  • FLEXDEPLOY-12138 - Updated Spring-Core library to resolve vulnerability CVE-2024-22233.

System Settings

  • Email OAuth Settings have been migrated to System Settings -> Integrations where individual OAuth applications are defined.

Groovy Libraries

  • Users can now create their own Groovy Libraries that can be shared across all Groovy scripts. A new Groovy Libraries page has been added under the Administration heading for users to create, edit and maintain their custom libraries. Each library is then made available in each Groovy script via a Library Key, for example LIB_MATH_HELPERS, just like our FLEXDEPLOY, EMAIL and other helper libraries.

  • The Groovy Library editor also includes a Try It window to test your library in real time as you are developing it!

Purge

  • FLEXDEPLOY-12790 - Introduced new Purge Setting Keep Production Count, which must be 1 or higher. Additionally, Keep Count setting can be lowered to 0. Keep Success Count and Keep Failed Count are removed. Customer should use other available Keep Count settings.

Plugin Updates

Resolved Issues

  • Projects

    • FLEXDEPLOY-13036 - Resolved an issue where project properties page shows underlying groovy script instead of showing List of Values.

    • FLEXDEPLOY-13087 - Resolved an issue where Success Rate and Duration metrics did not update when filtering by execution status for deployment executions on the Project Insights tab.

    • FLEXDEPLOY-13171 - SCM Defaults will now correctly set the default instance should one be present in the defaults.

    • FLEXDEPLOY-13209 - The Package select dropdown will now properly render the package description as markdown. If the description contains multiple lines, only the first line will be shown in the drop down.

    • FLEXDEPLOY-13188 - Resolved an issue where build/deploy/utility request form fails to submit if required Boolean input is not checked.

    • FLEXDEPLOY-13366 - Resolved an issue that would sometimes display a permission error if hovering execution links on the project execution page.

  • Release and Pipeline Management

    • FLEXDEPLOY-12406 - Allow removing projects and packages from completed releases.

    • FLEXDEPLOY-13072 - Encrypted snapshot inputs will now display a mask value ****** instead of the encrypted value.

    • FLEXDEPLOY-13288 - The Force Execute option on the Pre-deploy Pipeline step has been renamed to just "Force"

  • GIT

    • FLEXDEPLOY-3377 - Resolved an issue where update of GIT URL on source control integration instance may cause issues with build activity. URL update may include just protocol change from https to ssh or vice versa.

    • FLEXDEPLOY-7839 - Resolved an issue where multiple line commit message may get interpreted as changed file for commit.

  • Workflow Execution

    • FLEXDEPLOY-12662 - Resolved an issue to show files in the Execution Reports folder when a file name exists in multiple sub folders.

  • Work Items

    • FLEXDEPLOY-13196 - Corrected the documentation links for all Work Item Administration screens to point to the Administration documentation

  • Security

    • FLEXDEPLOY-13262 - Resolved an issue where User can unlock their own account.

  • Credentials

    • FLEXDEPLOY-13274 - Resolved an issue that caused testing credentials for custom providers to fail every time when using the encrypted value stored in the database.

  • User Profile

    • FLEXDEPLOY-13353 - Added missing documentation links to the user profile pages

  • Purge

    • FLEXDEPLOY-12989 - Resolved an issue where project versions of Package-based projects were not purged correctly if the workflow execution couldn't be started due to errors such as no endpoint available.

    • FLEXDEPLOY-12955 - Resolved an issue where project versions of Package-based projects were not purged if they were never deployed.

    • FLEXDEPLOY-12954 - Resolved an issue where the purge status display would not show the "RUNNING" status in certain cases.

Incompatible Changes

FlexDeploy 9.0 application now requires Java 17 and 21 and FlexDeploy Installer 1.0.21 or later should be used with FlexDeploy 9 upgrades.

URL Changes

  • The FlexDeploy Patches screen URL has been moved from /flexdeploy/next/#/administration/patches to /flexdeploy/next/#/administration/admin-operations/view-patches

Git Accounts

Git Accounts has been removed and Connected Apps has taken its place. Git connected applications will offer the same feature list as Git Accounts and more! However, because Git Accounts were stored only on the users device and not the FlexDeploy server we are not able to port over existing Git Accounts into Connected Applications. We apologize for this inconvenience.

Topology

  • FLEXDEPLOY-13170 - Removed the ability to set the PrivateKey default value for new Endpoints. This is due to Private Keys now being stored as SSH Key credentials.

  • No labels