IBM Sterling Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Automating CI/CD build/deployment pipeline starting with the development environment

We were working on a build/deployment pipeline for the IBM Sterling Order Management System (OMS) and there seemed to be too many manual steps in this process going from development to QA to PROD. We were hoping to get a more automated build/deployment pipeline process starting from the development environment. Hopefully, the developers who are working on the build/deployment pipeline will be able to distinguish the differences between application codebase and environment settings that are required for each deployment. For example, the application source code will be checked out from the source code repository, built, and packaged into deployment artifacts. These artifacts will be uploaded into a shared artifacts repository. Then, the deployments for the successive higher environments’ deployments will be using this shared artifact. Last, but not least, the environment settings per environment like keys and secrets that are required for each deployment will be externalized or tokenized and replaced only during deployment time. Thus, once this CI/CD pipeline has been automated for the development environment, the process for the higher environments’ deployments will be streamlined, minimized, and less error-prone. The results of this automated process will significantly increase deployment efficiency and the timeline for rolling out new features.

  • Guest
  • May 20 2022
  • Under review
What is your industry? Media & Entertainment
How will this idea be used?

Automation of deployments across all environments to increase the efficiency of deployment timelines.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.