Endevor Bridge for Git version 2.12.0 now available!

[Zachariah Mullen]

Our team is excited to announce the general availability of Bridge for Git version 2.12.0. This release of Bridge for Git consists of the following new features:

• Gitea support - Administrators can configure Bridge for Git with the open source enterprise Git server Gitea.  
• Repository transfer between Git servers - Administrators can configure Bridge for Git to work with multiple git servers, and mapping administrators can transfer their mappings to an alternate git server.
• Mirror mapping mode - Mapping administrators can initialize mappings that map only the elements of the target Endevor location and maintain at all times only an exact image of what is in the Endevor location.
• Support for public GitHub - Administrators can configure Bridge for Git to work with public instances of GitHub.
• Change Endevor connection for a mapping - Mapping administrators can use a new Advanced Mapping Administration checkbox on the Administration page to change the Endevor connection for a particular mapping

This release also consists of the following technical debt and customer fixes/requests:

• Keyring support for secured Bridge for Git server on the mainframe
• Ability to create hooks that call native programs
• Specification of commit message values for Bridge for Git operations for a particular mapping
• Secure local hook with a personal access token generated under the user profile
• Improvements to the processing of operations and management of the queue

The release is available for download from Broadcom Support. In Downloads, search for Endevor and then select the "Solution Downloads." Find "Endevor Integrations for Enterprise DevOps" version 18.1 and you will find a list of the components available.

We look forward to supporting you as you upgrade to this new version and continue to work with us on the continued development of Bridge for Git.

------------------------------
Zach Mullen
Product Owner, Integrations for Enterprise DevOps
[e-mail]
------------------------------

[Bruno Lago]

Zach Mullen,

As a Broadcom customer, we started using EBG.
We noticed that mapping managed by only one person sometimes causes problems, for example:

When the employee changes the password and forgets to change it in the EBG.
When the Employee goes on vacation.

So, it's causing some discomfort.

I don't know if you guys are already working on it, but hopefully having more people managing it would be cool, or any other idea.

Bruno Judson
IT Consultant

 

[Vaughn Marshall]

Hi Bruno,

Our recommendation for this would be to set up the API/ML from Zowe which enables certificate based authentication (thereby removing the need to continually update passwords).  It can be for the original user / mapping owner or for a generic service account if so desired.  You can also transfer ownership (e.g. if someone is planning to be out for a period of time).  Or if the person has forgot, the admin can transfer ownership to someone else.

Let me know your thoughts and whether this would address the problem.