BMC AMI DevX vs. GitHub

I love these tools! However, my company has not yet transitioned from SCLM to a modern repository, and this is causing most of our developers to remain within TSO for all their development. It's been a slow adoption up to this point, but we are moving toward more modernization this year and next, so with any luck, we'll see usage pick up. Success depends on the speed at which your management is willing to move.

Incentivized

I’ve worked with Github my entire career and view it as an essential part. As a Product manager it allows me to keep track of my features, epics, issues and QA. It is easy to set up and integrate with tools such as intercom or notion.

Incentivized

• Code Pipeline: integration of MF and non-MF type of object (COBOL, Java, zosconnect...). Deployment of objects coming from inside and outside the mainframe in the same way.
• Workbench for Eclipse: a must-have for working with Code Pipeline and the mainframe in the development context.
• Workbench for VS Code: They started developing VSCode, and the plugin works very well. There are a lot of things to add, but it's still very good. Young developers like it!

Incentivized

• Version control: GitHub provides a powerful and flexible Git-based version control system that allows teams to track changes to their code over time, collaborate on code with others, and maintain a history of their work.
• Code review: GitHub's pull request system enables teams to review code changes, discuss suggestions and merge changes in a central location. This makes it easier to catch bugs and ensure that code quality remains high.
• Collaboration: GitHub provides a variety of collaboration tools to help teams work together effectively, including issue tracking, project management, and wikis.

• Download source code plug-in on Azure DevOps to allow downloading prod version even if it's not in the assignment.
• Publishing Test Results on Azure DevOps from Total Test plugin
• Integration with DevEnterprise in Workbench and GenAI capabilities for enhance code analysis (Accross multiple programs/applications)

Incentivized

• Not an easy tool for beginners. Prior command-line experience is expected to get started with GitHub efficiently.
• Unlike other source control platforms GitHub is a little confusing. With no proper GUI tool its hard to understand the source code version/history.
• Working with larger files can be tricky. For file sizes above 100MB, GitHub expects the developer to use different commands (lfs).
• While using the web version of GitHub, it has some restrictions on the number of files that can be uploaded at once. Recommended action is to use the command-line utility to add and push files into the repository.

GitHub's ease of use and continued investment into the Developer Experience have made it the de facto tool for our engineers to manage software changes. With new features that continue to come out, we have been able to consolidate several other SaaS solutions and reduce the number of tools required for each engineer to perform their job responsibilities.

GitHub is a clean and modern interface. The underlying integrations make it smooth to couple tasks, projects, pull requests and other business functions together. The insights and reporting is really strong and is getting better with every release. GitHub's PR tooling is strong for being web based, i do believe a better code editor would rival having to pull merge conflicts into local IDE.

Incentivized

Support has been amazing compared to Optim. Further, new features are very regular with File-AID - I can't remember the last time Optim had a significant update. File-AID support is very receptive to feature requests and reported bugs, including sending out hotfixes quickly.

Incentivized

It's a testament to how easy it is to use GitHub and how many others use it that you can pretty much find the answer to any problem you have by searching online. Consequently, I've never needed to use their support. It's an incredibly easy tool to set up initially, so it won't require much onboarding expertise to get started.

Incentivized

The names may have changed over the years, but anyone who has been around for a while will recognize them. For Software Configuration Management, I have used TSO/ISPF/SCLM, Panvalet, ChangeMan, Librarian, Endevor, and now Code Pipeline. All of them met the basic requirements. All of them had their advantages and disadvantages. Code Pipeline, however, stands head and shoulders above the rest in simplicity, completeness, effectiveness, efficiency, and elegance.

Incentivized

GitHub comes handy in terms of usage and capabilities, it is easy to use and quite a user friendly tools when it comes to user experience, with limited UI/UX and it has vast exposure when it comes to third party integration and being quite mature and yet evolving and popular tool many other platform provide easy integration with the platform and make first choice for many tools architects.

Incentivized

• I can debug (expeditor) much faster and more efficiently. In fact, I was asked yesterday to run their job through Workbench Expeditor. I can also view data movement much better.
• Code analysis lets me give a quicker explanation of what a program may do, as it provides a graphical interface showing processing and data movement.

Incentivized

• GitHub has made branching much easier for our dev team. Easy branching makes it easier for us to gain all the benefits of source control while giving us the flexibility to decide what features/branches we want to go in any particular release.
• Integration with third-party tools like Azure DevOps has allowed us to streamline workflows and gain the benefits of automated testing whenever a commit is made.
• GitHub has also raised visibility with its integration with our Sprint boards. We can easily jump to a commit from a work item.

Incentivized