|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I've thought of that, but it will still not be very accurate.
You need to compare the changes in one label to the changes of the label that was used in the previous build. This, as far as I know, cannot be done in perforce. Even if it could, it would require that the labels be unique and immutable (so that you can guarantee that the previous build's label actually represents the last build) A common use-case is to use a single label that updates continuously, which the build runs off of.
The only way I can see of doing this is to record the entire state of the synced client on disk somewhere, and compare that to what is on the label being built. This is non-trivial to do, and is a real performance killer.