Track submissions by project
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- php
- Domain
- database, full-stack
Research direction
Start by locating the existing /monitor page and the submission-processing entry points, then trace how submissions and failures are currently represented. Define the submissions table and the /submissions and /projects//submissions pages so they show queue status and errors, and verify that the new pages replace /monitor as described.
Written by the indexing model from the issue text.
Description
Feature Request
How can we make CDash better?
Submissions can fail to display for a number of reasons, including parse failures, validation failures, or infrastructure issues. Additionally, submissions can appear to have failed if the queue is backlogged and results take longer than usual to appear. CDash currently displays the number of submissions by hour on the /monitor page, but there is no tracking of actual submissions.
I propose tracking each submission file individually, in a new submissions(id, projectid, buildid, created_at, status, details) table. Doing so allows us to add a new /submissions page, which would replace the /monitor page, as well as a new /projects/<id>/submissions page. These new pages would allow users to understand where their submissions are in the queue, and see any errors associated with failed submissions.
- Dominant language
- PHP
- Stars
- 248
- Forks
- 83
- Avg merge
- 12h 9m
- Merged PRs (30d)
- 47
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Kitware/CDash
-
bug report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug report
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
bug report
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
bug report
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
phpstan/phpstan-doctrine#794 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Automattic/static-site-importer#1767 ·