Page Comparison

...

• 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 versionThis . 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.

...

• 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

  As part of this work Email OAuth Settings have been migrated to System Settings -> Integrations where individual OAuth applications are defined.

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

Credentials

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

• Secret Text credentials have

  • 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 credentials will support

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

  These will be

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

  . There will also be an option to generate an SSH key pair within FlexDeploy

  • .

  • 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. These can be used for authenticating SMTP/IMAP accounts for Email Settings.

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 will be select able in the source instance. Then can be exported from the source FlexDeploy server as a zip file will be downloaded. This zip file can then be uploaded in the target instance 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:

...

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

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!

...

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

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.

...