Bug 2537 - When you STOP a build, it's not obvious what to do next
Summary: When you STOP a build, it's not obvious what to do next
Status: VERIFIED FIXED
Alias: None
Product: Hob
Classification: Build System, Metadata & Runtime
Component: hob (show other bugs)
Version: 1.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.3 M5
Assignee: Cristiana Voicu
QA Contact:
URL:
Whiteboard: merged
Depends on:
Blocks: 3160
  Show dependency tree
 
Reported: 2012-06-04 16:32 UTC by Dave Stewart
Modified: 2012-09-27 09:06 UTC (History)
8 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments
Stopping a build (455.65 KB, application/pdf)
2012-08-28 16:33 UTC, Belen Barros Pena
no flags Details
Stopping a build (458.85 KB, application/pdf)
2012-08-28 16:35 UTC, Belen Barros Pena
no flags Details
Stopping a build (458.77 KB, application/pdf)
2012-08-30 09:04 UTC, Belen Barros Pena
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Stewart 2012-06-04 16:32:55 UTC
This is on the version of Hob running in the released v1.2 Build Appliance.

When I hit Force Stop, the build stops but it is not obvious what to do next to get back to the configuration screen.

After long minutes of searching, I do eventually notice the "return to configuration" button appears at the bottom, but it doesn't catch my eye at all.

Please make it much more obvious, maybe put the new button at the top or something to make it clearer what to do next.
Comment 1 Belen Barros Pena 2012-08-28 16:33:56 UTC
Created attachment 742 [details]
Stopping a build

I finally got to this one: attached a description of how we could handle the stopping scenario. 

Let me know what you think.

Belen
Comment 2 Belen Barros Pena 2012-08-28 16:35:39 UTC
Created attachment 743 [details]
Stopping a build
Comment 3 Belen Barros Pena 2012-08-30 09:04:41 UTC
Created attachment 749 [details]
Stopping a build
Comment 4 Cristiana Voicu 2012-09-18 07:25:03 UTC
Hello Belen,

"Edit image" button should be more customized. If you the prior step is 'Edit recipes' screen, it should be call "Edit recipes". The same for packages and image. Am I right? That's happening also when you an error.

Thank you!
Comment 5 Belen Barros Pena 2012-09-18 09:35:01 UTC
Yes, happy with that. Then, we have the following cases:

Case 1: building without editing the base image. When you stop the build, we use 'edit image' as the button label. The button brings you back to the Image configuration screen (no matter when you stopped the build)

Case 2: you edit the base image and you stop the packages build. When you stop the build, we use 'edit recipes' as the button label. The button brings you back to the recipes selection screen

Case 3: you edit the base image and you stop the image build. When you stop the build, we use 'edit packages' as the button label. The button brings you back to the packages selection screen

Please note that the build fail scenario should behave exactly the same way.

(In reply to comment #4)
> Hello Belen,
> 
> "Edit image" button should be more customized. If you the prior step is
> 'Edit recipes' screen, it should be call "Edit recipes". The same for
> packages and image. Am I right? That's happening also when you an error.
> 
> Thank you!
Comment 6 Cristiana Voicu 2012-09-20 11:06:47 UTC
patch merged to master
Comment 7 Belen Barros Pena 2012-09-20 16:15:07 UTC
This is looking really good. We just need a couple of small changes:

1. For the 'Edit recipes' button, change the tooltip to "Edit the included recipes"

2. For the 'Edit packages' button, change the tooltip to "Edit the included packages"

3. Eliminate the alert that comes up when you click 'Edit packages'. You just stopped building, so we should assume you want to view the packages (not building them again). If you want to build them again, you can do so easily from the packages screen.

Thanks!
Comment 8 Belen Barros Pena 2012-09-21 09:58:56 UTC
Forgot to reopen yesterday when I created comment 7 (sorry)
Comment 9 Cristiana Voicu 2012-09-24 08:38:03 UTC
I have created a new bug for comment #7. The bug number is 3160
Comment 10 Belen Barros Pena 2012-09-27 08:54:54 UTC
Should I change this one to resolved, then?

(In reply to comment #9)
> I have created a new bug for comment #7. The bug number is 3160
Comment 11 Belen Barros Pena 2012-09-27 09:06:16 UTC
Marking as verified. Changes requests on comment 7 will addressed on 3160