|
||||||||||||
|
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.
Assigning to one of the Perforce plugin maintainers to ask a question.
Perforce already has a trigger mechanism, all that needs to be done is add support for that on Jenkins, similar to that in the Subversion and Git plugings: https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin
Something like this I imagine would be executed in the perforce trigger script:
/usr/bin/wget \
--header "Content-Type:text/plain;charset=UTF-8" \
--post-data "$CHANGELIST $P4_PATH`" \
-
output-document "" \--timeout=2 \
http://server/perforce/notifyCommit?rev=$REV
Is there some any other way of doing this already?
(Polling the respository seems like a suboptimal solution. Can miss changelists, and has to be done quite frequently)