Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.

Status Future consideration
Categories Build
Created by Guest
Created on Apr 2, 2020

HudsonSyncLoopRunnable should run multithreaded

We use Jenkins to run builds triggered from EWM/RTC. We currently have about 700 project areas, each of which has multiple components and there are several build definitions for each component. Our build farm has a couple of dozen executors but we ended up creating several build engines in RTC for each component to allow for parallel processing. This led to us having over 11000 build engines currently. Since the Sync loop appears to loop through all of the build engines to query their status, sometimes a build that run a minute or two in Jenkins may take over half an hour to update in RTC which leads the dev teams to open support tickets wondering what's wrong with the servers. We opened a support ticket with IBM but the response was that we'd need an RFE to allow the sync loop to run multi-threaded so that the sync loop can finish faster.

Idea priority Low
  • Guest
    Reply
    |
    Jan 8, 2024

    We ended up reducing the number of build engines we have by centralizing them in a single project area on the instance and reusing from the existing pool of engines rather than defining separate engines within each project area. This solved our issue

  • Guest
    Reply
    |
    Apr 4, 2020

    Moving to Jenkins plug-in for proper triage