Skip to content

Draft: SaaS CI job restrictions in pipeline chain for unverified users

Ruby Nealon requested to merge rnealon/ci-limits-for-saas-restricted-users into master

What does this MR do and why?

Add a check to the CI Pipeline chain to limit how many jobs a user can run without first going through the identity verification flow.

DO NOT MERGE - this is a draft and the exact criteria for restrictions needs confirming

Things still to confirm:

  • exact criteria for restrictions - working with the assumption of max 1 running job (with no parallel for unverified users)
  • count_other_active_jobs_by_same_user logic is correct
    • right now we are just adding command.pipeline_seed.size and current_user.pipelines.builds_count_in_alive_pipelines
    • not sure if command.pipeline_seed.size is the right thing to be using
  • manual local testing (I have been struggling to get the CI runner working locally)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

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

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request reports