[
http://issues.hudson-ci.org/browse/HUDSON-8260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144833#action_144833 ]
oeuftete commented on HUDSON-8260:
----------------------------------
Good, I think this is just what I came to JIRA to request. If I'm reading this correctly, this is basically asking for something like "p4 sync -k" behind the scenes? If so, that fits my use case too where I want to set up a top-level launcher that does some downstream and Join Plugin stuff, needs to trigger only on new changes, but doesn't need the files itself.
> Option to disable syncing, while maintaining polling and changelog functionality
> --------------------------------------------------------------------------------
>
> Key: HUDSON-8260
> URL:
http://issues.hudson-ci.org/browse/HUDSON-8260> Project: Hudson
> Issue Type: New Feature
> Components: perforce
> Reporter: rpetti
> Assignee: rpetti
> Priority: Minor
>
> We would like to implement and option for disabling syncing, but allowing other functions such as changelog fetching, changelist number tracking, and polling to remain operational.
> As it stands right now, the view mask work-around breaks P4_CHANGELIST by preventing it from updating. We'll need to add (yet another) option in order to support this specific use-case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.hudson-ci.org/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Locked
