DefangLabs / DefangLabs/defang

Build Queues

Open
#170 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

byoc later
Dominant language
Go
Stars
166
Forks
24
Avg merge
10h 8m
Merged PRs (30d)
33

Description

This ties in with https://github.com/defang-io/defang/issues/169 to some extent. With most systems I've come across with build queues, you can see historical data about how builds went, but you also get information about queued builds:

  • if they're in the same project/org you might see other queued builds
  • if they're not, you might see a number of builds ahead of yours
  • systems like GitLab sometimes give you information about build runners

Essentially, given that the build queue and build runner status determine how fast my build becomes available, I want to be able to have a sense of what's going on there.

The DX could be as simple as:

defang cd status

and then getting:

4 builds currently in queue

Or it could be more like my proposal in the other issue and provide something like:

etag service status started completed build time
6238gf782 ui queued - - -
328hf0j0 api queued - - -
fjd8s038 ui in progress 2024-03-06T20:50:40Z - 2m32s
792h39jfds ui failed 2024-03-06T19:50:40Z 2024-03-06T19:54:40Z 4m0s
792h39jfds api complete 2024-03-06T19:50:40Z 2024-03-06T19:52:45Z 2m5s

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing defang cd status entry point and the related issue 169. Clarify whether the command should report queue counts, runner information, build history, or the proposed per-service table; done should provide an agreed, observable view of queued and running builds.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, cloud, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.