[JIRA] [p4-plugin] (JENKINS-33372) Perforce:Publish assets override new changes
Title: Message Title Guy Oh commented on JENKINS-33372 Re: Perforce:Publish assets override new changes Thanks Paul I did try to use different WorkSpace and eliminate the unnecessary Section (it is not one file only) however it seems that the process doesn't take the mapping into account as the relevant stream it is attached to has its own mapping which seems to override the configuration I put in It seems to me that i'll have to create a designated stream (possibly virtual stream) that will be connected to my Development stream and filter unnecessary path from there. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-33372) Perforce:Publish assets override new changes
Title: Message Title Guy Oh created an issue Jenkins / JENKINS-33372 Perforce:Publish assets override new changes Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 08/Mar/16 1:16 AM Environment: Jenkins Version:1.638 P4 Version:1.2.5 Labels: plugin p4-plugin Priority: Major Reporter: Guy Oh My Job is triggered on any files changes Perforce Repository setup is identical for Retrieving and Publish Assets The issue is along the following scenario: 1) file.txt content changed from 123 to 345 2) file.txt is submitted to the repository 3) Jenkins job is triggered due to this change 4) while jenkins jobs still running and before the "Perforce:Publish assets step" file.txt content changed again from 345 to 678 and submitted to the repository 5) Perforce:Publish assets step override the most updated version of the file to the previous one. meaning file.txt is submitted back to the repository with content "345".
