Cisco Cisco Unified Customer Voice Portal 10.0(1) Guía Del Usuario
C
HAPTER
2:
B
UILDER FOR
V
OICE
XML
S
TUDIO
V
OICE
XML
S
TUDIO
U
SER
G
UIDE
FOR
C
ISCO
U
NIFIED
C
USTOMER
V
OICE
P
ORTAL
49
Version Control Integration
Version control software facilitates multiple developers working on a single voice application,
and also allows developers to revert their applications to an earlier state should the need arise.
Cisco Unified CVP VoiceXML Studio is built on top of Eclipse, which allows developers to
leverage the version control support that Eclipse offers. Cisco Unified CVP VoiceXML Studio
includes support for Concurrent Versions System (CVS); other version control systems are
supported by adding additional plug-ins to Cisco Unified CVP VoiceXML Studio's Eclipse
foundation.
and also allows developers to revert their applications to an earlier state should the need arise.
Cisco Unified CVP VoiceXML Studio is built on top of Eclipse, which allows developers to
leverage the version control support that Eclipse offers. Cisco Unified CVP VoiceXML Studio
includes support for Concurrent Versions System (CVS); other version control systems are
supported by adding additional plug-ins to Cisco Unified CVP VoiceXML Studio's Eclipse
foundation.
Using Version Control to Support Multiple Developers
Once Cisco Unified CVP VoiceXML Studio is configured to access your source control system,
it can be used to support multiple developers working on a single voice application. Each
developer can work on a different part of a voice application simultaneously. However, it is
recommended that only one developer work on any given page of the application at any given
time. If this guideline is followed, only the page folders listed under the
it can be used to support multiple developers working on a single voice application. Each
developer can work on a different part of a voice application simultaneously. However, it is
recommended that only one developer work on any given page of the application at any given
time. If this guideline is followed, only the page folders listed under the
pages
subfolder of the
callflow
folder should be checked in (not individual elements).
For example, if a developer makes a change on
page32
, no one else should be working on
page32
concurrently. The developer can safely check-in the
page32
folder when he or she is
done. Other developers can then check-out the
page32
folder, close and reopen their callflows,
and the changes will be reflected.