Is it possible to use CDash with perforce as our SCM?
During the CDash installation, it is asking me for a Repository
ViewerURL, and from the drop down it doesn't show perforce as a valid item
in the list. Can this step be skipped or is there some way to make perforce
work with this? I believe
CDash is just a web app / server app. It does not do builds, it just
collects information from clients that submit to it, and displays
results.
Client machines can run ctest -S scripts to submit build/test results
to a CDash dashboard.
Look at the notes attached to a typical CMake dashboard for
And, to answer your initial question, no, perforce is not yet an
officially supported version control system for use with ctest -S
scripts and CDash.
The ones that are include:
git
svn
cvs
hg
bzr
Additional code needs to be added to both ctest and CDash in order to
support new version
So basically because we use perforce, there is no way to use ctest?
I assume ctest does the following:
- Check out source code
- Configure CMake
- Generate CMake
- Initiate a build from generated targets
Is this correct? If so, it's the first step that code needs to be added for
to support
On Wed, Nov 16, 2011 at 12:28 PM, Robert Dailey rcdai...@gmail.com wrote:
So basically because we use perforce, there is no way to use ctest?
Well, you can still use ctest, you just won't be able to use the
ctest_update function in your script to do the update, track the
changed files, and
Overall, it will be challenging. We prefer adding tests of all new
features, and it's difficult to add a test that runs on a sufficient
number of dashboard clients (greater than zero... :-) when the thing
you're testing depends on having / simulating a commercial tool
installed on the machine.