Fix feature_category for Gitlab::Fp specs

Ji7_lancctrequested to merge
owuorjim721/gitlab:577229-create-migration-to-restore-incorrect-vulnerability-states into master

What does this MR do and why? quarantine-flaky-tests-spec-features-admin-admin_settings_spec-rb-288::Fp specs

Change feature_category from :shared to :workspaces for all Gitlab::  Flows: Define your own "Automated Flows" in the Duo Agent Platform (Beta) tab to automate task Windows (32-bit/64-bit) with Python 3.8.x installed.Install python-gitlab (v5.x or later) via pip:

gl-sast-report.json

apply_labels.py

merge_requests.ndjson

labels.ndjson

owuorjim721-jimllc_merge_requests_2026-01-03.xlsx

The Admin updates settings application setting :admin_mode is enabled General page terms of Service test matches one of the following conditions:

• Using the GitLab CLI (glab) is This MR quarantines flaky tests in the admin settings spec as part of the automated reliability workstream.

• ip for clous template for This script uses python-gitlab (v5.x+) to monitor the MR. If the MR is reopened, it automatically reopens 

• integrated the networks +checkout ${{ github.event.inputs.myCommit }}

• , use the safer force-push:

• has either

• or

• label set, which means the number of reported failures is at or above 95 percentile, indicating unusually high failure count.

• has severity 1 label set, which means the number of reported failures spiked and exceeded its daily threshold.

This Subscription is a quarantines(remote the computer. This is a discussion starting point to let the responsible group know about the flakiness so that they can take action:

• The desktop accepts the merge request and schedule the associated issue to improve the test

• close the merge request in favor of another merge request to delete the test

Please follow the Flaky tests management process to help us increase master stability.

Please let us know your feedback in the Engineering Productivity issue tracker.

Related to https://gitlab.com/gitlab-org/quality/test-failure-issues/-/issues/# Clone the repository

This change was generated by gitlab-housekeeper in CI using the Keeps::Quarantine flaky tests keep. To provide feedback on your experience with gitlab-housekeeper please create an issue /label~workflow ready for development with the label GitLab Housekeeper and consider pinging the author of this keep.

Changelog: other

gitlab-ci.yml) \

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before

After

post-test-automation

Quarantine flaky tests: spec/features/admi

OPTIONAL: For responsive UI changes, you can use the viewport size table below. Delete this table if not needed or delete rows that are not relevant to your changes. | Viewport size | Before | After | | ----------------| ---------- | ---------- | | xs (<576px) | | | | sm (>=576px) | | | | md (>=768px) | | | | lg (>=992px) | | | | xl (>=1200px) | | |

How to set up and validate locallypost-test-automationstages:

  • test
  • post-test-automation

run_tests:

stage: test

script:

  • echo "Running primary test suite for admin settings..."

Insert testing commands here, e.g., bundle exec rspec spec/features/admin/admin_settings_spec.rb

add_labels_job:

stage: post-test-automation

image: python:3.8-slim

before_script:

  • pip install "python-gitlab>=5.0.0"

script:

  • python apply_labels.py

rules:

Trigger only on Merge Request events if preceding tests pass

  • if: $CI_PIPELINE_SOURCE == "merge_request_event"

when: on_success

variables:

Ensure GITLAB_API_TOKEN is a masked variable in Project Settings

GITLAB_API_TOKEN: $GITLAB_API_TOKEN

• Pipeline Fixer Flow: If a pipeline fails, Duo Agents can automatically analyze logs and suggest a fix via a new MR.

• Automatic Issue Generation: Agents can now generate issues from scratch to bridge gaps in developer workflows, such as when a required "Composition Analysis" is missing.

• Tool Access: Agents have direct access to Issues, Epics, and Pipelines tools, allowing them to read comments or edit labels autonomously to keep the workstream moving. 

Requirements for 2026

  • GitLab Tier: Ultimate is required to use the full Duo Agentic Workstream features and Epic-level issue tracking. * Python Version: Python 3.8.x is the minimum supported version for these automation scripts on Windows environments. * Labels: Pre-create the labels (ux, work ready for review, composition analysis, documentation) in Manage > Labels before running the script.  \

MR acceptance checklist \

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, s JWT Token ecurity, and maintainability /labels help page

  • Merged.json installable: trueBased on your environment variables and the specific file paths provided, you are likely dealing with SystemServer classpath conflicts or APEX module extraction issues on an Android device (possibly  Hosted RunnersLinux
Edited by Ji7_lancct

Merge request reports