[GPRD] Vulnerabilities Scan result API available before pipeline completes

Production Change

Change Summary

This change enables reports ingestion once all security jobs complete so that the results will be available as soon as possible and will require anymore for the pipeline to complete

This change was requested by multiple customers because, currently, pipeline vulnerability APIs return zero vulnerabilities if the pipeline is not completed. This limitation prevents customers from validating security scan results within the same pipeline and from automatically failing builds based on security findings

Change Details

1. Services Impacted - ServiceGitlab

2. Change Technician - @schmil.monderer

   DRI for the execution of this change

3. Change Reviewer - @ryaanwells

   DRI for the review of this change

4. Scheduled Date and Time (UTC in format YYYY-MM-DD HH:MM) - 2025-08-26 18:00

5. Time tracking - Instantly by enabling FF

   Time, in minutes, hours, or days, needed to execute all change steps, including rollback

6. Downtime Component - N/A

   If there is a need for downtime, include downtime estimate here

Set Maintenance Mode in GitLab

If your change involves scheduled maintenance, add a step to set and unset maintenance mode per our runbooks. This will make sure SLA calculations adjust for the maintenance period.

Detailed steps for the change

Pre-execution steps

• Make sure all tasks in Change Technician checklist are done
• For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
  • The SRE on-call provided approval with the eoc_approved label on the issue.
• For C1, C2, or blocks deployments change issues, Release managers have been informed prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
• There are currently no active incidents that are severity1 or severity2
• If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.

Change steps - steps to take to execute the change

Estimated Time to Complete (mins) - Instantly by enabling FF

• Set label changein-progress /label ~change::in-progress
• Enable ingest_sec_reports_when_sec_jobs_completed FF globally on production
• Set label changecomplete /label ~change::complete

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - Instantly by disabling FF

• Disable ingest_sec_reports_when_sec_jobs_completed FF globally on production
• Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

• Metric: Metric Name
  • Location: Dashboard URL
  • What changes to this metric should prompt a rollback: Describe Changes

Change Reviewer checklist

C4 C3 C2 C1:

• Check if the following applies:
  • The scheduled day and time of execution of the change is appropriate.
  • The change plan is technically accurate.
  • The change plan includes estimated timing values based on previous testing.
  • The change plan includes a viable rollback plan.
  • The specified metrics/monitoring dashboards provide sufficient visibility for the change.

C2 C1:

• Check if the following applies:
  • The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
  • The change plan includes success measures for all steps/milestones during the execution.
  • The change adequately minimizes risk within the environment/service.
  • The performance implications of executing the change are well-understood and documented.
  • The specified metrics/monitoring dashboards provide sufficient visibility for the change.
    • If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
  • The change has a primary and secondary SRE with knowledge of the details available during the change window.
  • The change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval.
  • The labels blocks deployments and/or blocks feature-flags are applied as necessary.

Change Technician checklist

• The change plan is technically accurate.
• This Change Issue is linked to the appropriate Issue and/or Epic
• Change has been tested in staging and results noted in a comment on this issue.
• A dry-run has been conducted and results noted in a comment on this issue.
• The change execution window respects the Production Change Lock periods.
• For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
• For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue. Mention @gitlab-org/saas-platforms/inframanagers in this issue to request approval and provide visibility to all infrastructure managers.
• For C1, C2, or blocks deployments change issues, confirm with Release managers that the change does not overlap or hinder any release process (In #production channel, mention @release-managers and this issue and await their acknowledgment.)