Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. 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 Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Dec 13, 2022

Deployment warnings should be exposed as a consumable property

We are currently making use of the warnings feature in UCD where we are marking the deployment with an ucdWarning in certain cases.

When looking at a deployment through UCD, it's clear that there is a warning and that the person needs to take a closer look. However, there are quite a lot of end users that don't look inside UCD and are mainly concerned with Jenkins.

As long as the deployment doesn't 'fail', they are not going to take a closer look at UCD. Hence, it's important to be able to return this 'warning' back to Jenkins, so that we can mark the build as unstable.

Currently, when we do a requestApplicationProcess, we put the 'post-deploy-message' = '${p:finalStatus}', so that on callback, Jenkins knows whether the deploy was successful or not. We would like to be able to extend this with a notion of there being a warning.

However, when looking at the properties that are part of the deployment, I don't see any valuable parameter that I could add to the above 'post-deploy-message'.

Idea priority Medium