Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Functionality already exists
Workspace Self Service Tool
Created by Guest
Created on May 20, 2022

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.

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.

  • Admin
    Sampson Wong
    Jul 5, 2023

    For a complete CICD flow, please explore the SST command line tool which allows the user to upload and deploy the application. For the source code specific tracking between development/preprod/production, I would encourage the use of a Version control tool between each level of the development.

    Here is the link to the command line tool