Issue with Parallel Builds on a Single Runner – Build Steps Queued and Running Switching Between Different Pipeline Builds

When multiple builds are initiated to run in parallel on a single runner, the expected behavior is for the build started first to run, while the subsequent builds are queued. However, there is an issue where the build steps started first sometimes gets queued, and the build steps started later begins running.

Please add a lock to ensure that a build started earlier completes all its steps before allowing the subsequent builds, which started a bit later in the sequence, to be queued.