IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 Submitted
Workspace IBM Developer for z/OS
Categories Host/Distributed SCM Integration
Created by Guest
Created on Feb 24, 2026

RELATED IDEAS

Native GitLab Runner for z/OS security

The security concepts of GitLab runners are mainly intended for distributed environments owned by a single application. With the introduction of the GitLab Runner for z/OS, which is a system shared by hundreds of users and applications, a new security concept is required.

It should be possible to configure the setup of the GitLab Runners in such a way that users of the runner—whether intentionally or unintentionally—can cause as little damage as possible to the target system. Since the technical user under which the GitLab Runner operates must have extensive permissions in order to execute build and deployment commands, and since the GitLab Runner in principle executes any commands passed to it from the pipeline, this creates potential for problems. To reduce this risk, it could, for example, be sensible for the GitLab Runner to perform a check against RACF, or to restrict the commands that the runner is allowed to execute via Bash.

Idea priority High

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.