• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • P4 Plugin version 1.8.4

      I can observe that some text files (but also binary files) have been submitted through p4publish step even though they were unchanged. I can check that those files were unchanged in the perforce history.

      Considering our machine will build and submit binaries for every relevant code change, this could lead to a lot more submits from the build machine than necessary, so this is a critical issue for us.

          [JENKINS-49534] p4publish submits files that are unchanged

          Karl Wirth added a comment -

          support@perforce.com are working with Samuel.

          Karl Wirth added a comment - support@perforce.com are working with Samuel.

          Samuel Kahn added a comment -

          Alternatively, is there a way to set the "revert unchanged" flag on the workspace described from the jenkinsfile using a stream spec ? This would solve the problem I suppose.

          Samuel Kahn added a comment - Alternatively, is there a way to set the "revert unchanged" flag on the workspace described from the jenkinsfile using a stream spec ? This would solve the problem I suppose.

          I have a similar issue and I'm seeing symbolic links getting re-submitted when they are unchanged.

          I had similar problem with text files but it was caused by RCS keyword expansion being enabled on those files.

          Is there a known problem with p4publish?

          Andrew Barnish added a comment - I have a similar issue and I'm seeing symbolic links getting re-submitted when they are unchanged. I had similar problem with text files but it was caused by RCS keyword expansion being enabled on those files. Is there a known problem with p4publish?

            p4karl Karl Wirth
            kahncode Samuel Kahn
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: