Endevor Bridge for Git Version 3.2.1 Generally Available

[Lukas Zima]

We are excited to announce the general availability of Endevor Bridge for Git version 3.2.1

 

Bridge for Git 3.2.1 is available on the Broadcom Support Portal. The new version can also be deployed as a Docker Image and with a Helm Chart. 

For specific download procedures, see Acquire the Product.

 

The release includes the following new features and enhancements:

• Improved Branch Merging

A new application.yml parameter defines how Bridge For Git handles manual updates to sensitive configuration files within a synchronized Git branch. This parameter provides Increased flexibility for manual updates and makes merging branches easier.

• Limit Hook Notifications

A new application.yml parameter lets administrators set notification limits for large mappings to reduce the performance impact on the server that runs Bridge for Git.

• Security Enhancements

This release implements additional security-hardening measures.

 

For more information about the features included in this release, see New Features.

 

💡 Quick Tips: Migrating from v2.x to v3.x

 

While Bridge for Git is designed for automatic migration, we highly recommend attention to the specifics of the migration process.

 

Before You Begin

Before you begin a Bridge for Git upgrade, review the following considerations:

 

• Learn about the New Features in version 3.
  
  

• Review the list of Breaking Changes that come with this new release. If you are impacted, please plan your upgrade accordingly. A significant change, for example, is the Java 17 requirement.
  
  

• To improve the user experience, we recommend increased hardware resources for Bridge for Git 3.0 deployments. Also, ensure that you provide sufficient hardware resources to your Bridge for Git server. For more information, see Address Hardware Requirements.
  
  

• Familiarize yourself with the Upgrade Checklist.

 

Upgrade Process

 

Each deployment of Bridge for Git is specific. To ensure a seamless upgrade of your production environment, we recommend first testing the upgrade procedure in a test environment.

 

Before upgrading, ensure that you have a current backup, especially of the Bridge for Git database. Having a current backup will ensure an easy rollback in case of issues during an upgrade.

 

An integral part of the upgrade is updating client software, such as the Zowe CLI plugin and VS Code extension, to versions that are compatible with Bridge for Git v3. For more information, see the Available Zowe CLI Plug-ins topic in the Enterprise Support for Zowe documentation, and Bridge for Git Explorer documentation in the Visual Studio Marketplace.

 

We Are Here for You

 

Do not hesitate to contact us for assistance. Whether you need clarification with upgrade planning or you are experiencing issues with the upgrade, feel free to reach out.

 

We welcome your feedback and suggestions about your experience with the upgrade procedure, the new product version, and the product documentation. 

 

Best regards,

Product Owner: Lukas Zima, [e-mail]

Product Manager: Vaughn Marshall, [e-mail]

-------------------------------------------