RHQ & Powershell
Michael Foley
mfoley at redhat.com
Tue Mar 26 21:13:59 UTC 2013
I guess the saying "If it ain't broke, why fix it?" comes to mind. Or, put another way ... the risk/reward ratio seems like division by 0. All risk, and no reward.
Another way of looking at this is cost/benefit ratio. The costs here are both development time refactoring, as well as QE time retesting. And ... at risk of sounding pessimistic ... the GSS time in dealing with new customer issues in this area.
Sounds like a cool idea ... but it doesn't make sense to me. I don't know what problem you are trying to solve, or what additional customer-facing value you are trying to deliver.
I am -1 on this idea unless a stronger case can be made.
Michael Foley
QE Lead, JBoss Operations Network
----- Original Message -----
From: "Stefan Negrea" <snegrea at redhat.com>
To: "rhq-devel" <rhq-devel at lists.fedorahosted.org>
Sent: Tuesday, March 26, 2013 5:02:21 PM
Subject: RHQ & Powershell
Hello Everybody,
The current RHQ Windows scripts use Batch. While this works out of box on all Windows versions, the scripts are quite complicated and very brittle. For the past few years Microsoft built Powershell to replace Batch. With Windows 7 PowerShell got integrated in Windows; and for older versions (eg. XP, Vista, Server 2003) Powershell can be easily installed. As far as I know, it's just a program that runs on .Net framework.
Here is the official Microsoft tutorial for Powershell:
http://technet.microsoft.com/en-us/library/cc196356.aspx
Should we consider migrating current Windows Batch scripts to PowerShell?
Thank you,
Stefan Negrea
Software Engineer
_______________________________________________
rhq-devel mailing list
rhq-devel at lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fedorahosted.org/pipermail/rhq-devel/attachments/20130326/11cb8a81/attachment.html>
More information about the rhq-devel
mailing list