[p4] CruiseControl: changes on label in a date range
david.karr at wamu.net
Tue Dec 20 10:50:44 PST 2005
I'm having some trouble with my CruiseControl setup, which uses
Perforce. My CC config manages several applications, where each
application has several projects. Each application has a single "head"
project, which just syncs to the head and checks for changes to the
head. Those work fine.
I also have one project for each released version of the application.
These projects sync to a view with a label, and attempt to check for
changes with that same label-appended view specification. So, for
instance, an abbreviated view spec would be "//... at label". What I've
discovered is that CruiseControl will internally generate view
specification to check for changes in a date range, by appending the
user-supplied view specification with a date range, like
"<view>@<fromdate>,<todate>" (I believe that is the approximate syntax
they are using). This operation works fine in my "head" projects, but
in my "version" projects, when the view spec already has "@label" on it,
the resulting internal viewspec looks like
"//... at label@<fromdate>,<todate>". This doesn't parse.
So, is there a "standard" way for p4 to check for changes on a label in
a date range, or are those two things mutually exclusive?
I'm thinking that a reasonable workaround for my problem is to remove
the part of my CC config that uses Perforce to check for modifications,
and simply have it check the client view filesystem, which would have
just been modified with the sync, if there were any changes (although I
wonder what would happen if a changed file was "back-dated" to the time
Is this something that other people have run into?
More information about the perforce-user