Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52169

One Time Force Sync

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: p4-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      We are actively migrating from the "old" perforce jenkins plug-in to the "new" perforce jenkins plugin that is supported by perforce.

      With the old perforce plugin, it was possible to use an environment variable in order to control whether or not the -f option (see one_time_force_sync.png) was passed to the p4 sync command.

      If I tick the box next to P4FORCESYNC option (see p4forcesync.png), it sets the matching environment variable to true, which results in the "One Time Force Sync" option of the plugin to be set to true, which results in the '-f' flag being added to the sync command for that one build.

      We used this environment variable quite a bit. Most of our jobs are parameterized builds. One of the parameters is typically P4FORCESYNC. 

      For example, we will occasionally want to refresh the timestamps of all of the files in our art pipeline, to generate a full build of every asset.

      Is this something that can be achieved with the current p4 plugin? Could this be added as a feature request?

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            s3037560 Kevin Park
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: