You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we report the results of deployment to specific hosts by displaying a ruby data structure at the end of the deployment process:
% tpkg -s bogushost,realhost --qa
Exit statuses:
{"realhost"=>0, "bogushost1"=>1}
Users have pointed out that this is not ideal. If they want to access the individual status programmatically they have to parse the output, find this data structure, and read it back in via ruby. It would be much more convenient if we had an option to save individual status to a file, particularly in a more generic format like yaml.
Currently we report the results of deployment to specific hosts by displaying a ruby data structure at the end of the deployment process:
% tpkg -s bogushost,realhost --qa
Exit statuses:
{"realhost"=>0, "bogushost1"=>1}
Users have pointed out that this is not ideal. If they want to access the individual status programmatically they have to parse the output, find this data structure, and read it back in via ruby. It would be much more convenient if we had an option to save individual status to a file, particularly in a more generic format like yaml.
Was: https://sourceforge.net/apps/trac/tpkg/ticket/32
The text was updated successfully, but these errors were encountered: