Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.
You are not logged in.
Pages: 1
I have read the documentation and find the references to source control ambiguous and confusing.
I noticed a forum message that says that PowerGen does not have source control functions.
This aligns with the functionality I find in the product, but is not what I think documentation implies.
With a help topic "How to use PowerGen for Source Control and Release Control" something more.
Have I overlooked something. Does PowerGen provide no help extracting the source files from a Source Control tool.
If the assumption is that these functions are readily available outside of PowerGen then why not give some examples.
I am am on my way to becoming a dissatified user/customer. I don't like being misled about a tools capability.
From my experience using Powergen, it doesn't have "Integrated" source control capabilities. This is probably due to the number of SCC providers out there.
As for example scripts have you had a look at http://www.ecrane.com/scripts.htm.
We use Merant PVCS 7.5 as our source control which has a command line version that we use in a batch script to extract all our objects based on a version label set against each object. This command line interface extracts all the objects to a build pc and then we use Powergen to perform the actual build.
Hope this helps...
If there are parts of our documentation that are misleading, please point out where and we'll correct it.
PowerGen does not have an interface to source control systems. We would have to use the SCC-API which is idiosyncratic in each vendor's implementation and is a subset of most vendor's capabilities. Instead we rely on the SC system's command line interfaces which all provide rich functions to accessing the objects stored in them. Not only does this provide a more robust and functional interface, it's also considerably faster.
Regards,
Phil
Pages: 1