Spike: Investigate queries and UNION that is run for needs

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

Before we can move forward with increasing the project:needs limit discussed in #393885 (closed), we need to investigate the limitation that was initially set because when dependencies are resolved, complex db queries are run as well as a costly UNION.

Some additional details can be found here:

using Ci::PrepareBuildService to resolve cross dependencies(store their ids in Ci::Build#options or other table/column) and use those values when presenting the job to the runner

Additional details

Some relevant technical details, if applicable, such as:

• Does this need a feature flag? N/A
• Does there need to be an associated instrumentation issue created related to this work? N/A
• Is there an example response showing the data structure that should be returned (new endpoints only)? N/A
• What permissions should be used?
• Is this EE or CE?
  • EE
  • CE
• Additional comments:

Order of investigation table

Group	Issue Link
spike	👈 You are here
backend	#207329

Links/References