[cmake-developers] Perforce Patch for CTest

[Pedro Navarro]

I was thinking that as the test requires the p4 tool to be installed, we
might as well require also p4d (the server, which is now free for up to 20
users). In that case the test can bring up a local server and work against
it which, in the end, will create less issues as the p4 database will be
deleted when the test ends. If we work against a real production server we
might not be able to use p4 obliterate and we will be leaving those
temporary checkins the test does polluting the history, and that might not
be desired.

Pedro


On Wed, Oct 16, 2013 at 8:08 AM, Pedro Navarro <pnavarro at netflix.com> wrote:

> Sounds good. Those environment variables are read automatically by
> Perforce's command line tools, so there's nothing to do on the test's end
> then.
>
> Pedro
>
>
> On Wed, Oct 16, 2013 at 5:23 AM, Brad King <brad.king at kitware.com> wrote:
>
>> On 10/15/2013 07:39 PM, Pedro Navarro wrote:
>> > That's exactly my point. Is it ok to rely on environment variables
>> (P4PORT, P4HOST), ie, expect the build machine to be set up in a way before
>> running the tests or are those values passed in some kind of configuration
>> file, added to the CMake Cache or passed as -D?
>>
>> For now I think it is okay to read those.  The surrounding dashboard
>> client script can set up the environment accordingly.
>>
>> Thanks,
>> -Brad
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20131016/c057f054/attachment.html>