Greetings,

I am using the repository label step to create a Perforce label at a certain point in our build pipeline and have noticed that this step uses the 'p4 labelsync' command to populate the label. The 'p4 labelsync' command only populates the specified labels with files that exist on the client's workspace and does not take into account any files that may have been deleted.

The issue here is that when a user syncs to the latest label containing our code, the files that have been deleted from the depot won't show up in the label, but they also don't get deleted from the user's workspace. As you might imagine, this can lead to confusing and inconsistent errors due to the user's workspace being in an incorrect state.

The simplest solution would be to change from 'p4 labelsync' to 'p4 tag', which includes all revisions (add, edit, AND delete) for all files in the labelspec view, not just the add and edit revisions.

Thanks,
-J. Mash