Skip to Main Content
Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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.

Status Under review
Created by Guest
Created on Oct 12, 2026

GitHub & Harness CI/CD Integration for IBM Workload Scheduler (Schedule-as-Code)

Enterprise customers are increasingly adopting GitHub and Harness as their strategic DevSecOps toolchain. Whilst IBM Workload Scheduler provides APIs, Composer and Automation Hub integrations, there is currently no IBM-supported integration that enables scheduling definitions to be managed as code, version controlled in GitHub, validated through Harness CI, and promoted through Development, Test and Production using a governed CI/CD process. This requires customers to build and support bespoke deployment frameworks, validation logic, rollback processes and deployment scripts for IdWS, IcWS and IzWS environments. [yourautomationhub.io], [help.hcl-s...ftware.com]

Current Workaround

Customers must currently develop and support their own integration using:

  • GitHub repositories
  • Harness CI/CD pipelines
  • Custom validation scripts
  • Composer commands
  • IWS REST APIs
  • z/OS deployment tooling
  • Manual rollback and recovery processes

This results in duplicated effort, inconsistency between customers, increased operational risk and slower adoption of self-service scheduling.

Requested Enhancement

Provide an IBM-supported GitHub and Harness integration allowing IWS scheduling definitions to be managed as code and deployed through a standard CI/CD workflow.

The solution should provide:

  • Native GitHub integration
  • Support for existing Composer scheduling definitions
  • Harness CI validation templates
  • Automated impact assessment
  • Secure credential management
  • Dev → Test → Production promotion
  • Approval gates
  • Deployment verification
  • Immutable release packaging
  • Audit reporting
  • Drift detection
  • Recovery and rollback capabilities

The integration should support:

  • IcWS (Containerised IWS)
  • IdWS (Distributed IWS)
  • IzWS (IWS for z/OS)

Business Value

This capability would:

  • Enable true Schedule-as-Code for IBM Workload Scheduler.
  • Align IWS with modern platform engineering practices.
  • Improve governance and auditability.
  • Reduce manual deployment activities.
  • Increase customer self-service.
  • Reduce operational risk.
  • Accelerate onboarding of scheduling workloads.
  • Improve consistency across environments.
  • Reduce dependency on specialist administrators.
  • Provide an enterprise-standard deployment model aligned with GitHub and Harness.
Idea priority High