We develop software for an interior design program. It takes about 20 minutes to build the software. We have a localhosted Windows server as our only runner. I've set up a pipeline that does a "test build" of each pull request which is working great. The "test build" is just for developer feedback and does not get deployed anywhere. I've also set up a custom pipeline for actual "build + deploy" jobs. However, since we only have one runner, the "deploy" jobs get placed in the queue after all "test build" jobs. This means that if there's 3 "test build" jobs in the queue, it could take an hour before it begins the "deploy" job. Is there a way to prioritize jobs, so "deploy" pipelines always get moved up in the queue?