Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: p4-plugin
-
Labels:None
-
Environment:Platform: All, OS: All
-
Similar Issues:
Description
We have a need to trigger Hudson to build a project tree based on a known
Perforce Changelist number. This may seem backwards from the Hudson paradigm,
but our existing build system checks out a build ID file and increments a build
counter along with saving the Changelist number being used to submit the
change. This Changelist number is then used to synch the entire branch to a
known moment in time. This approach was chosen over applying a label to avoid
the overhead of applying 4-5000 labels to our source. Using the known
Changelist eleminates mistakenly including any changes that occur after the
know point in time.
Is this possible using the Perforce plugin, or with any combination of existing
plugins?
Would this be a feasable/desirable enhancement for the existing Perforce plugin?
Ah yes, I see. Passing changesets that way would probably be OK. I should try.
I thought the 'p4 counter' solution might be able to provide changelogs. The job would know the value of the counter (same as changelist number) for every build and should be able to find all changes between those. Precisely like it does for the polling.
Of course, if the plugin wants to be very defensive, I must admit that of course it's possible to play games with the counters and update them behind the scenes (even back in time). Although you technically can do that with changelist numbers as well, that series of numbers is always increasing.