You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
Today in Sourcegraph, there is a dequeue endpoint for each queue. If an executor instance were to support multiple different queue (or filters), executors should make a request to a general endpoint and have Sourcegraph provide an appropriate Job (this will help with fairness).
Done
Create a general "dequeue" endpoint
The request payload should include the queues
At this time, the first available Job that is included in the list of queues is to be returned
Fairness will be implemented in a followup Issue
The Job that is returned from the new endpoint should have the associated queue set on it
Unit Tests
Demo
Using something like Postman as the client will suffice
Technical Consideration
Keep the existing dequeue endpoint[s]. It must be kept for backwards compatibility.
Do not implement "fairness" at this time (unless makes sense)
Today in Sourcegraph, there is a dequeue endpoint for each queue. If an executor instance were to support multiple different queue (or filters), executors should make a request to a general endpoint and have Sourcegraph provide an appropriate
Job(this will help with fairness).Done
Jobthat is included in the list of queues is to be returnedJobthat is returned from the new endpoint should have the associated queue set on itTechnical Consideration