Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show more feedback on building crates #826

Closed
Kixiron opened this issue Jun 8, 2020 · 2 comments
Closed

Show more feedback on building crates #826

Kixiron opened this issue Jun 8, 2020 · 2 comments
Labels
A-frontend Area: Web frontend E-medium Effort: This requires a fair amount of work

Comments

@Kixiron
Copy link
Member

Kixiron commented Jun 8, 2020

Currently crates are not added into the releases database until they're fully built, but that's not needed. When adding crates to the queue, we should download the source files and add them to the database and give the release a status page that allows users to see that their crate is building and what its position in queue is. This allows us to better display build failures and to even display source files of failed builds and binaries. Crates on the /queue page should link to the crate's status page instead of the crates.io page

@Kixiron Kixiron added E-medium Effort: This requires a fair amount of work A-frontend Area: Web frontend labels Jun 8, 2020
@jyn514
Copy link
Member

jyn514 commented Jun 8, 2020

Note that in particular, this means we show the sources for a crate regardless of whether the build succeeded.

@syphar
Copy link
Member

syphar commented Oct 21, 2024

I think this is solved with #2467 , and #2529

@syphar syphar closed this as completed Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-frontend Area: Web frontend E-medium Effort: This requires a fair amount of work
Projects
None yet
Development

No branches or pull requests

3 participants