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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Not under consideration
Workspace Heritage
Categories Build Forge
Created by Guest
Created on May 6, 2026

RELATED IDEAS

Need ability to set license timeout

We use FlexLM Floating Licenses for Build Forge. However, Build Forge holds on to a floating license for >24 hours, even when there's no activity from the user. It should be possible to release licenses in a reasonable timeframe, like 2 hours, the way it works for ClearCase and ClearQuest, using a ibmratl.opt file to set timeouts. Unfortunately, adding an entry for Build Forge to this file has no effect.

Refer to the following Cases for more details:

TS013877678

TS022120624

TS022430058

I attached a screenshot of the licenses currently in use. The person that has been using a license for more than 25 hours IS OFF TODAY! (she ran a deployment yesterday).

Thanks,

Jozef

BFUsage.jpg
BFUsage.jpg
Open full size
  • Guest
    Jul 28, 2026

    Hi,

    This is totally unacceptable. Build Forge holds on to licenses for more than 24 hours. No build runs for 24 hours. I urge you to reconsider. You are just accelerating the State's migration to Atlassian Bamboo. I would prefer for our projects to remain on Build Forge.

    Thank you.

    Jozef 

     

    Reply
  • Guest
    Jul 21, 2026

    Products utilize different licensing mechanisms based on their usage and business models. For ClearCase (CC) and ClearQuest (CQ), releasing the license after 2 hours is logical because typical operations—such as code check-ins/check-outs or updating tickets—are completed within that time frame.

    For Build Forge, however, build jobs often run for 2 hours or longer depending on their complexity. Releasing the license prematurely risks disrupting a running build, which is why this parameter is fixed and not configurable. If the number of users exceeds the current license count, we recommend acquiring additional licenses.

    Reply

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.