Cloud Platform

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

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 a notification 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.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Under review
Workspace UrbanCode
Categories Velocity
Created by Guest
Created on Aug 31, 2021

Gate Condition with Test/Security Results for Deployment Trigger

Gate approvals for deployment through UCV is manual approvals with the defined approvers list. For CI/CD implementation, it is a practice to rely on Testing (JUnit/JMeter/Selenium) and Security (SAST,DAST) results for deployment in DEV and QA environments. Considering current feature of manual approval is not feasible even for lower environments and can be considered only for PROD environments.


Based on results from Testing/Security, if there are any critical blockers, then we stop the deployment in lower environment and the user trying to deploy the failure build will acknowledge which can be recorded for future audits.

Why is it useful?
  • Provides more flexibility with CI/CD implementation

  • Less manual effort in approving the request to verify all test/security results manually

  • Developers are aware of the results so that it can be fixed at the earliest instead of tracking it separately

Who would benefit from this IDEA? Developers, Admins, PM
Idea Priority High