Last week, we presented uDeploy to the Global Rational Users Group. Members of the user group community can watch the replay.
Q. What is the install footprint for uDeploy for a particular box, which is used for testing for example.
A. While waiting for work, the memory footprint is pretty light – usually just enough memory to support two small Java processes. The agent is very low overhead from a CPU perspective as well.
Q: How can people re-use standard deployment flows across similar applications?
A. uDeploy has an idea of Component Templates. These templates, facilitate putting all the common information for similar components in one place (artifact sources, processes, etc). Individual deployable components, are pointed at a Template (or version thereof) and inherit the settings.
Q: If you have multiple applications that are tracked separately, how do you see which of those share a specific component? In other words, if you are changing a specific database, which of the applications that are tracked in udeploy will be affected?
A: uDeploy is designed with the idea that multiple Applications will share Components. By looking at a given Component, you can see which Applications consume it. Also, if one Application makes a change
Q: What kind of reports or information is shown on the dashboard?
A: The interface supplies an overview of which components have been deployed where at what versions. There are also deployment history reports, as well as duration and frequency reports. The reports are designed to help with audit / governance or provide KPIs around utilization.
q: Does uDeploy integrate with ClearCAse?
Yes, ClearCase is a supported source for deployable artifacts.
Q: Does uDeploy have a command line interface?
It does, and the CLI is documented.