Bug 1276575

Summary:	[RFE] include recipe whiteboard in tasks/executed listing
Product:	[Retired] Beaker	Reporter:	Karel Srot <ksrot>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	medium
Version:	develop	CC:	azelinka, ksrot, mastyk, mjia
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-02 11:53:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Karel Srot 2015-10-30 08:06:48 UTC

Description of problem:

We do frequently access task results through links such as the one below

https://beaker.engineering.redhat.com/tasks/executed?recipe_task_id=35510143&recipe_task_id=35509736&recipe_task_id=35509981&recipe_task_id=35510035&recipe_task_id=35509898&recipe_task_id=35509844&recipe_task_id=35510089&recipe_task_id=35509790

My problem is that some of those tasks were executed with a newer package version which we state using whiteboard notes like "server - new" and "server - old". Having the whiteboard included in the listing would help me to quickly identify package version for individual tasks (and eventually failures).

Comment 1 Roman Joost 2015-11-04 05:33:14 UTC

Dear Karel,

thank you for your report. We're currently working on improving the overall user experience with the jobs page and are keen to improve whatever depends on it.

I'd like to ask if you could elaborate on your wish including the whiteboard. What is your primary goal you want to achieve with the grid? What does the grid provide you the recipe page doesn't? If the task grid would be missing tomorrow, what would you miss?

Thank you for the effort.

Comment 2 Karel Srot 2015-11-04 08:52:01 UTC

Hi Róman,

our common testing approach during a bug verification is:
 1. run test with old package version for all supported architectures
 2. run test with new package version for all supported architectures
 3. compare the above (ideally old would fail and new pass)
This typically results at least in two jobs with multiple recipes. Moreover, we frequently have to reschedule a recipe due to aborts. In the end test results are spread in several jobs and recipes.

The URL from #c0 is the easiest for how to access test results of a particular task from all provided recipes. We do store such URL in TCMS test case run in notes so we can access test results when needed.

As I said, such results contain test executed both with the old and the new version of a package that is being tested (this is intentional since we want to compare those results). Unfortunately, on the page it is not visible whether a particular task was running with old or new package. We do store this information in recipe whiteboard and therefore having this information visible would let us to instantly see which package version was installed. See
  https://beaker.engineering.redhat.com/recipes/2290508
and
  https://beaker.engineering.redhat.com/recipes/2290500

Comment 3 Martin Styk 2020-06-02 11:53:52 UTC

Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>