CI Builds should be queued

Not sure where CI issues should go, so apologies for duping gitlab-org/gitlab-ci#359

We've had some issues where development code has made it live because GitLab CI runs both builds in the same folder simultaneously.

It would be great if the jobs were queued, preferably based on project and branch.

@mikew1 Is this about the GitLab Runner?

Hm, yes I guess it could be implemented there. But it's GitLab that dispatches CI jobs, so I figured the functionality should be added there.

Or am I missing something, is there already a way to do the following with GitLab?

• use a shared runner
• allow concurrency
• limit to one build per project

This is the solution I came up with. It replaces $CI_PROJECT_DIR with something more unique, thus allowing concurrency and the ability to easily access artifacts.

Status changed to closed

@mikew1 We plan to introduce sticky runners that will solve that issue. It will force proper ordering of builds.

mentioned in merge request !14785