headers
Jeff A. Bowles | 1 Apr 2006 07:18
Picon
Favicon

Re: [p4] Using a changelist id as a build number?


On Mar 31, 2006, at 11:20 AM, <Ken.Williams <at> thomson.com> wrote:

> I think the easiest way to avoid a race condition is to first ask 'p4
> counter change' what the current changelist number is, then sync to  
> that
> number and build.  If someone submits more changes while you're doing
> that, you never need to care, you won't see those changes.
>
> If you want to get fancier, you can sync to that change number then  
> ask
> 'p4 changes -m1 ...' what changelist is actually present in your build
> directory (presumably you don't care about changes outside that  
> space).
> If it's the same as last time you built (which you could keep track of
> with a p4 counter or elsewhere) then you can skip the build.

	You might just do a "p4 changes -m1 //depot/pathname/..."
	(I'd add "-s submitted" as an option, also) at the beginning of the
	script.

	It'll give you a change number back.

	Sync to that change number. Put that change number in your
	version.h that you generate. Put it in your build reports as
	"build path: //depot/pathname/... <at> xxxx" where 'xxxx' is the
	change number.

	No muss, no fuss.  And no race.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Chuck Karish | 3 Apr 2006 01:42
Picon

Re: [p4] Debugging "commit" triggers

On 3/31/06, Weintraub, David <david.weintraub <at> bofasecurities.com> wrote:
> You Unix heads keep forgetting: Email is not
> standard equipment in the Wonderful World of Windows.

Are you responding to this?

> > emailing error output to the administrator, or at
> > the least sending it to a log or syslog

Windows has both local and remote (like syslog) application logs.

> However, it would be nice if trigger errors got logged to the Perforce
> log file and this included the STDOUT from the trigger.

I very much prefer to keep output from p4d separate from
output from user programs, including triggers.  On Windows
I'd have triggers send their output to the applicaiton log.

--
Chuck Karish   karish <at> well.com   (415) 317-0182

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 501 comments |
headers
Andy Finkenstadt | 3 Apr 2006 01:45

Re: [p4] integration of outside repositories into p4 depots

note002 and note015 were perfect for my needs. 

I haven't yet written the automated, nightly/weekly job to integrate 
outside changes in an unattended fashion, but at this point that's just 
a Small Matter of Programming. (SMOP**)

-andy

*SMOP : a small matter of programming is something that you estimate 
will take a couple hours and end up taking a couple weeks after contact 
with the real world.

Andreas Axelsson wrote:
> Sounds like you could use the Vendor pattern here. It's very useful for
> importing external changes into the depot and we use it all the time. It
> handles edits, adds and removes with minimal scripting.
>
> http://www.perforce.com/perforce/technotes/note015.html
>
> /axl
>
> -----Original Message-----
> From: perforce-user-bounces <at> perforce.com
> [mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Andy
> Finkenstadt
> Sent: den 27 februari 2006 21:13
> To: 'Perforce Users Mailing List'
> Subject: [p4] integration of outside repositories into p4 depots
>
> Greetings,
(Continue reading)

Permalink | Reply | 501 comments |
headers
Chuck Karish | 3 Apr 2006 01:52
Picon

Re: [p4] Using a changelist id as a build number?

On 3/31/06, Jeff A. Bowles <jab <at> pobox.com> wrote:
>         You might just do a "p4 changes -m1 //depot/pathname/..."
>         (I'd add "-s submitted" as an option, also) at the beginning of the
>         script.
>
>         No muss, no fuss.  And no race.

What you usually want is

  p4 changes -m1 //depot/pathname/...#have

which returns the latest change that's synced to that tree in your client.
This gives a complete representation of the source tree you're building if
the client had previously been updated with a command like

  p4 sync //depot/pathname/...

If different parts of the tree had been synced to different versions you
need a label or a brranch to record the contents of the build.

--
Chuck Karish   karish <at> well.com   (415) 317-0182

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 1 comment |
headers
Jeff A. Bowles | 3 Apr 2006 06:33
Picon
Favicon

Re: [p4] Using a changelist id as a build number?


On Apr 2, 2006, at 4:52 PM, Chuck Karish wrote:
> On 3/31/06, Jeff A. Bowles <jab <at> pobox.com> wrote:
>>         You might just do a "p4 changes -m1 //depot/pathname/..."
>>         (I'd add "-s submitted" as an option, also) at the  
>> beginning of the
>>         script.
>>
>>         No muss, no fuss.  And no race.
>
> What you usually want is
>
>   p4 changes -m1 //depot/pathname/...#have
>
> which returns the latest change that's synced to that tree in your  
> client.

	The reason I did not give that is that I, consistently, say in these
	emails that you should figure out the change number, then sync
	that down.

	When I teach Perforce classes, I emphasize that it is partly about
	using the tool and partly about the software engineering to minimize
	risks and surprises.

	That way, you have no question what the command was. I also
	have no reliance on the SCM/librarian figuring it out from "what you
	have" (Perforce does that well, others might not).

	And I check the "can I rebuild from this chgnum/label" question,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeff Jensen | 3 Apr 2006 20:32

[p4] Preventing spaces in job names

Hi, my users (especially the new ones) keep putting spaces in job names. 
Perforce just doesn't work well with spaces in job names.

What are suggested solutions to prevent this?

My best thought so far is a job form trigger to prevent it.  Anyone have one to
share before I create a Python one?

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 1 comment |
headers
Jeff A. Bowles | 3 Apr 2006 21:54
Picon
Favicon

Re: [p4] Preventing spaces in job names


On Apr 3, 2006, at 11:32 AM, Jeff Jensen wrote:

> Hi, my users (especially the new ones) keep putting spaces in job  
> names.
> Perforce just doesn't work well with spaces in job names.
>
> What are suggested solutions to prevent this?
>
> My best thought so far is a job form trigger to prevent it.  Anyone  
> have one to
> share before I create a Python one?

	I would write a slightly more general tool, that you pass in
	two arguments from the command-line:
		"job" (type of form)
		"%formname%" (name of the form, note the quotes in both)
	Maybe even "%user%" (as provided by p4d)

	The script would inspect the name of the form and perhaps
	use different rules for the type of form:
		"jobs must match the reg expr (\S+)"
		"labels must start with the name of the current user"
		"client names must be of the form loginid_project"
	and so on. (You might make rules based on users being in
	certain groups, but decide before-hand whether this script
	runs 'p4' commands directly.)

	You could then use this script - a pretty general one - to enforce
	a number of things like this, for labels and jobs and perhaps
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dave Robertson | 3 Apr 2006 21:54
Favicon

[p4] Perforce European User Conference: Call for Papers


Perforce Software is excited to announce that its first European 
User Conference will be held on September 19, 2006 at The Marriott
Hotel County Hall, London, UK.

Have you used Perforce to overcome a particularly difficult development
problem? Do you have a complex development project that you are using
Perforce to manage? Has Perforce helped your organisation to deal with
new challenges in your marketplace?

If so, or you have an idea for a paper that other Perforce users would
benefit from, please consider giving a 45-minute presentation at the
conference.

Please submit an outline or draft (as a Word, text, or PDF document) 
of your paper by April 15. You will be notified of your paper's status 
by April 30. If your paper is accepted, you'll be asked to submit an
abstract and a short biography by July 1 for posting on our Web site.
The final draft of your paper is due no later than July 15.

To submit a draft, email conference <at> perforce.com, or visit our Web site
for more information:

  http://www.perforce.com/perforce/eucon2006/index.html

--

-- 
Dave Robertson
Director of European Operations
phone: +44 (0) 845 345 0116
_______________________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Adrian Kalaveshi | 4 Apr 2006 02:14

Re: [p4] wiki with storage in Perforce

Does anyone know if this exists yet?

[Tue, September 14, 2004 5:56 am] Nick Barnes said:
> Does anyone know of a Wiki-like tool which stores its data in Perforce?
>
> Nick Barnes
> Ravenbrook Limited
> _______________________________________________
> perforce-user mailing list  -  perforce-user <at> perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 5 comments |
headers
Weintraub, David | 4 Apr 2006 14:33
Favicon

Re: [p4] wiki with storage in Perforce

Trac uses Subversion, and there is someone with a "Perforce plug-in" to
change the Wiki base from Subversion to Perforce:

<http://trac-hacks.org/wiki/PerforcePlugin>

Trac is a wiki-based defect tracking system.

-----Original Message-----
From: perforce-user-bounces <at> perforce.com
[mailto:perforce-user-bounces <at> perforce.com] On Behalf Of Adrian
Kalaveshi
Sent: Monday, April 03, 2006 8:14 PM
To: perforce-user <at> perforce.com
Subject: Re: [p4] wiki with storage in Perforce

Does anyone know if this exists yet?

[Tue, September 14, 2004 5:56 am] Nick Barnes said:
> Does anyone know of a Wiki-like tool which stores its data in
Perforce?
>
> Nick Barnes
> Ravenbrook Limited
> _______________________________________________
> perforce-user mailing list  -  perforce-user <at> perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>

_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
(Continue reading)

Permalink | Reply | 0 comments |

Gmane