Bug 767744 - [RFE] In provisioning, show ant task executed in destination deployment details
Summary: [RFE] In provisioning, show ant task executed in destination deployment details
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Provisioning
Version: 3.0.0
Hardware: Unspecified
OS: Unspecified
medium
urgent
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-14 19:26 UTC by Nabeel Saad
Modified: 2022-03-31 04:27 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Nabeel Saad 2011-12-14 19:26:47 UTC
Description of problem:
When you deploy a bundle, and click through the destination into the actual deployment.  Then you can see the different steps that took place, such as deployment started, file downloaded, build event, build event, build event, etc... It would be nice to be able to differentiate between the build events.  Can we not display at least the name of the task that is called in that build event?

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Heiko W. Rupp 2013-12-09 10:09:39 UTC
Nabeel,

can you explain this a little more please? Especially as you say "at least" -- what else would you want to see?
What is helpful in the field to see bundle deployment issues?

Comment 2 Nabeel Saad 2013-12-10 12:48:52 UTC
Hello Heiko,

I believe that each "build event" that I listed above is actually related to some ant task taking place in the bundle.

It would be nice to see more detail in the sense that it could show:
pre-install
post-install

or if it's even possible to show more detail such as listing the actual ant tasks taking place: exec, move, etc...

Does that make more sense? If not, I can try to get a screenshot to clarify what I'm talking about.


Note You need to log in before you can comment on or make changes to this bug.