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 Planned for future release
Workspace Rational Other
Categories Build Forge
Created by Guest
Created on Jul 15, 2016

Fix required : Not able to restart RBF job from GUI, when the job is triggered as 'API-Only' user

Issue : When the RBF job which gets triggered from API as "API-Only" user fails, we are not able to restart the job from GUI as "normal" user.
Note: GUI is logged in as 'normal' user

Work around TSR provided : Use SQL to update the build ownership to a normal console user in the database and restart the build via console UI

Challenges with the workaround :
1. We need to get RBF server backend access and RBF DB schema access for all the GUI users (deployers) which is not recommended
2. It is very difficult to execute the query for every failed job

What we expect : A solution to restart the failed jobs without running DB query
Other Concerns : Currently we are running on RBF version 7.1.3.3. We have approximately 300+ RBF agents. If the Fix for the issue is provided in next release(probably version 8.0.0.x), we will have difficulty in upgrading RBF to 8.0.0.x version since upgrading all 300+ agents to 8.0.0.x version is a huge effort. Hence the fix is expected to be a patch in the exiting RBF version.

Idea Priority Medium
Use Case
We trigger a RBF deployment project from Jenkins using API. When the job fails, we will fix the issue and try to restart the job from RBF. Which is not possible if the job is trigger as "API-Only" user.
RFE ID 91558
RFE URL
RFE Product Rational Build Forge
  • Guest
    Dec 10, 2020

    The feature that is described in this request is a candidate for a future release.