headers
Jeff Jensen | 2 Nov 2005 14:38

Re: [p4] Time zone problem with VSS and vsstop4

To follow up for the archives and the curious, Robert has done a fantastic
job of supporting me with this issue.  As he mentioned below, he wrote a
Ruby script to scan VSS for this problem.  It is on his utils page in the
public depot:

http://public.perforce.com/guest/robert_cowham/perforce/utils/index.html

A big thanks Robert!

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Jeff Jensen
Sent: Sunday, October 30, 2005 9:00 AM
To: 'Robert Cowham'; perforce-user <at> perforce.com
Subject: Re: [p4] Time zone problem with VSS and vsstop4

Thanks Robert - That's a great idea; a utility to report the pervasiveness
of the problem would determine our needed course of action.  Thank you in
advance :-)

-----Original Message-----
From: Robert Cowham [mailto:robert <at> vaccaperna.co.uk]
Sent: Sunday, October 30, 2005 7:27 AM
To: 'Jeff Jensen'; perforce-user <at> perforce.com
Subject: RE: [p4] Time zone problem with VSS and vsstop4

It's a known problem that is on the list to fix/address.

The reasons the scripts use time for sorting is to group files into
changelists.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter Prymmer | 2 Nov 2005 16:52
Favicon

[p4] Has anyone gotten p4 to work with Microsoft Visual Studio 2005 (Version 8)?


I have a report from a Windows user that p4 is not working well with the
very recently released
Microsoft Visual Studio 2005 (Version 8).

Does anyone know of any tricks to getting them to cooperate, or should I
consider
it currently unsupported?  Thank you.

Peter Prymmer

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 1 comment |
headers
John.Davis | 2 Nov 2005 16:52

[p4] Baselining client specs?

Hi, I have a problem - anyone solved this before?

I am trying to manage and keep records of build requests, which are 
basically
a Perforce client spec and a changelist number.  The idea is that,
from these two pieces of information, we can recreate builds reliably,
on a separate build machine as required. Currently, the build requests
are all entered into a Lotus Notes database by software developers,
and our build team use the database to schedule their build servers.

The problem I have is that the client specs can change, which means
we really need to identify the point in time for the client spec (in
a form we can use).  We can't use changelist numbers, as they don't relate
to changes in the client specs.  My next idea was to automatically record 
the
client version number and use that as a template for our build. For 
example,
we receive a build request, e.g. for client "savxp_main", changelist 
"14567":

p4 files //spec/client/savxp_main  ==> to get client version number (#5)

Then when we schedule the build we can do:

p4 client -t //spec/client/savxp_main#5  build_client

But this doesn't work - we get:

Revision chars ( <at> , #) not allowed in '//spec/client/savxp_main'.
(Continue reading)

Permalink | Reply | 7 comments |
headers
Jamison, Shawn | 2 Nov 2005 18:00

Re: [p4] Baselining client specs?

Why not store the results of p4 client -o specname as text in the lotus notes app for that build request?  

That way you have the request, date, Changelist, and client spec used for a build.

It's a hack but it would satisfy your need.

-Shawn J>

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com]On Behalf Of
John.Davis <at> sophos.com
Sent: Wednesday, November 02, 2005 10:53 AM
To: perforce-user <at> perforce.com
Subject: [p4] Baselining client specs?

Hi, I have a problem - anyone solved this before?

I am trying to manage and keep records of build requests, which are 
basically
a Perforce client spec and a changelist number.  The idea is that,
from these two pieces of information, we can recreate builds reliably,
on a separate build machine as required. Currently, the build requests
are all entered into a Lotus Notes database by software developers,
and our build team use the database to schedule their build servers.

The problem I have is that the client specs can change, which means
we really need to identify the point in time for the client spec (in
a form we can use).  We can't use changelist numbers, as they don't relate
to changes in the client specs.  My next idea was to automatically record
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Cowham | 2 Nov 2005 18:09
Picon

Re: [p4] Baselining client specs?

> Then when we schedule the build we can do:
> 
> p4 client -t //spec/client/savxp_main#5  build_client
> 
> But this doesn't work - we get:
> 
> Revision chars ( <at> , #) not allowed in '//spec/client/savxp_main'.
> 
> Maybe I'm trying to do entirely the wrong thing here - it 
> seems quite hard work to get at this information.  Another 
> possibility is to take a copy of the client spec itself, and 
> check this into Perforce, but this also seems a 
> duplication... Anyone have an elegant, automatable solution?

The spec file is just a text file. Using it is a little more rustic than you
might hope for.

Manual steps are:

P4 print -q //spec/client/savxp_main#5 > cl.txt

Edit cl.txt to change "savxp_main" in client name and view fields to
"build_client", and optionally root dir (or copy that from existing
build_client)

P4 client -i < cl.txt

E.g.

C:\bruno_ws>p4 print -q //spec/client/bruno_ws.p4s#1 > cl.txt
(Continue reading)

Permalink | Reply | 0 comments |
headers
Russell C. Jackson | 2 Nov 2005 18:10

Re: [p4] Baselining client specs?

You can automate this by doing the following:

When you launch a build, have the build run:

set p4client=generic client that has a view of the spec folder
p4 changes -m1 > change number. That is the change number of the time you
started the build.
p4 sync //spec/client/savxp_main <at> changenumber from above
p4 client -i < savxp_main (file you synced in the previous step)
set p4client=savxp_main
p4 sync -f  <at> change number from p4 changes -m1
start your build.

Thanks,
Rusty

----------------------------------------------------------------------------
-- 
RCJackson Consulting
Perforce Consulting Partner and Certified Trainer
----------------------------------------------------------------------------
--

-- 
Russell C. Jackson 
211 River Oaks Lane
Russellville, AR 72802 
----------------------------------------------------------------------------
--  
rusty <at> rcjacksonconsulting.com
http://public.perforce.com/guest/russell_jackson/pcp.html
tel:         479-696-9710
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dave Lewis | 2 Nov 2005 18:33
Favicon

Re: [p4] Baselining client specs?

  > Maybe I'm trying to do entirely the wrong thing here - it seems quite hard
  > work to get at this information.  Another possibility is to take a copy of
  > the client spec itself, and check this into Perforce, but this also seems 
  > a
  > duplication... Anyone have an elegant, automatable solution?

We use this solution, since spec depots were not available, but since the
mechanism is already in place, we continue to use it.

I haven't messed around with the spec depot much, can it be synced to a 
date/time spec?  if so, get the date/time spec equivalent to the changenumber
and use that.

also, I don't believe you can directly reference //spec/client/etc 
in the p4 client command... it didn't work for me, version or no version.

dave
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 1 comment |
headers
Stephen Vance | 2 Nov 2005 18:38

Re: [p4] Baselining client specs?

You could do

p4 print -q //spec/client/savxp_main#5 | sed -e 
's/savxp_main/build_client/' | p4 client -i

You may also need to change the Host field. A Python or Ruby script 
with -G or -R could make it more portable and let you address 
specific fields easily.

Also, for your files command, don't forget you can do either

p4 files //spec/client/savxp_main#head

or

p4 files //spec/client savxp_main <at> 2005/11/2:12:37:00

depending on whether you want to select the head or by date.

Steve

At 10:52 AM 11/2/2005, John.Davis <at> sophos.com wrote:
>Hi, I have a problem - anyone solved this before?
>
>I am trying to manage and keep records of build requests, which are
>basically
>a Perforce client spec and a changelist number.  The idea is that,
>from these two pieces of information, we can recreate builds reliably,
>on a separate build machine as required. Currently, the build requests
>are all entered into a Lotus Notes database by software developers,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kevin Hale Boyes | 2 Nov 2005 19:01

[p4] determine changelist

Here is what I'm wondering...

I come to work and do a (force) sync on my project.
I'm now current to a particular changelist number.
During the day, people commit changes which advances the "change"
counter.

I'd like to determine what changelist my view is currently at.
Is this possible?

Thanks,
Kevin.

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 1 comment |
headers
Peter Stephenson | 2 Nov 2005 19:04
Favicon

Re: [p4] Baselining client specs?

John.Davis <at> sophos.com wrote:
> p4 client -t //spec/client/savxp_main#5  build_client
> 
> But this doesn't work - we get:
> 
> Revision chars ( <at> , #) not allowed in '//spec/client/savxp_main'.

I may be barking up the wrong tree, but I think the template has to be a
really live client.  Can't you do something along the lines of:

p4 print //spec/client/savxp_main#5 |
  sed 's/^Client:.*$/Client: build_client/' | p4 client -i

or, maybe safer

p4 print //spec/client/savxp_main#5 |
  sed 's/Client:.*$/Client: tmp_build_client' | p4 client -i
p4 client -t tmp_build_client build_client

?

--

-- 
Peter Stephenson <pws <at> csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070

This message has been scanned for viruses by BlackSpider MailControl - www.blackspider.com
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
(Continue reading)

Permalink | Reply | 0 comments |

Gmane