-
Notifications
You must be signed in to change notification settings - Fork 8
Restructure issues
commands
#210
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
Restructure issues
commands
#210
Conversation
|
d2c51f3
to
3c5ac24
Compare
Issues command output:
|
Hi Jeny, thanks for these changes. I'll add some comments:
|
c2bf3ed
to
1ab70d3
Compare
Thank you for the feedback.
Addressed all the comments except the last one.
Done.
Done. |
1ab70d3
to
9ceaec7
Compare
is not filtering by tree/branch
|
1 similar comment
is not filtering by tree/branch
|
I think this was already discussed on the etherpad.
Done. |
df6d8a9
to
910c239
Compare
what etherpad? |
This PR is based on the feedback I received from @padovan |
As per our latest conversation, I'll handle issue filtering from kci-dev side for now.
|
Filtering issues will be handled on this PR or a different PR? |
I'll make changes to this PR. |
ok, thanks |
Remove `issues` command group and subcommand handlers as part of command restructuring. Signed-off-by: Jeny Sadadia <[email protected]>
Hi @padovan Here is the sample output with issue filtering working:
Note: New issues will have a |
910c239
to
869104f
Compare
To avoid printing error returned from API, use `error_verbose` option while sending GET request to dashboard API. Add the option to `results builds` and `results boots` command. This change is needed to avoid a flood of error message while fetching new/missing issues with `results issues` command. Signed-off-by: Jeny Sadadia <[email protected]>
869104f
to
fbc9cde
Compare
@JenySadadia sounds good. The 2 issues that don't have next/master in the first incident still have incidents on the tree. As for the NEW tag, let's add it to the beginning of the line:
With |
Fetch KCIDB issue matching provided ID. Also get associated builds and tests. Sample command: `kci-dev results issue --id <id> --origin <origin>` Signed-off-by: Jeny Sadadia <[email protected]>
`kci-dev results issues` command utilities: - Fetch KCIDB issues from the dashboard with `results issues` command - Filter issues by checkout by providing `--giturl`, `--branch`, `--commit` and `--tree`(optional) options - Get new issues for checkouts with `--new` option - Get failed/inconclusive builds and boots without any associated issues with `--missing` option Signed-off-by: Jeny Sadadia <[email protected]>
fbc9cde
to
5256faf
Compare
Done. Updated the tag to have the red color. |
As we are showing issues, I also think that red is better |
This looks like it can be merged |
Restructure KCIDB issues related commands.
Modifications:
issues
command group and subcommand handlers as part of command restructuringresults issue
commandkci-dev results issue --id <id> --origin <origin>
results issues
command--new
optionany associated issues with
--missing
option