Right now, when the CLI hits the /complete endpoint we call submit_to_build_isolated() directly, without passing for admin_project_builds. That means that we don't check for concurrency limits and similar.
We need to find a way to differentiate a build that is TRIGGERED and waiting for the user to upload the artifacts, from a one that is TRIGGERED and the artifacts are already uploaded (the CLI hit /complete already). With that, we will be able to use admit_project_builds workflow by admitting those that are "upload completed"
Right now, when the CLI hits the
/completeendpoint we callsubmit_to_build_isolated()directly, without passing foradmin_project_builds. That means that we don't check for concurrency limits and similar.We need to find a way to differentiate a build that is TRIGGERED and waiting for the user to upload the artifacts, from a one that is TRIGGERED and the artifacts are already uploaded (the CLI hit
/completealready). With that, we will be able to useadmit_project_buildsworkflow by admitting those that are "upload completed"is_uploaded=Truefrom admission #13307