Jump to content


P4V 2017.3 passes incorrect parameters when unshelving using stream mapping, files not in workspace view

p4v 2017.3 unshelve stream bug

  • Please log in to reply
1 reply to this topic

#1 dekarguy

dekarguy

    Member

  • Members
  • PipPip
  • 13 posts
  • LocationAustin

Posted 25 January 2018 - 05:23 PM

Following the instructions on http://answers.perfo...rticles/KB/3651

We have a mainline stream, which a handful of files are shelved on, and a direct child development stream we are trying to unshelve the files to

on //stream/main, shelve files and revert them
change workspace to //stream/development, right click the changelist, unshelve, and click Map Unshelved files using stream //stream/development
with p4 logging, the following command is generated
p4 unshelve -s 1234 -f -c 1234 -S //stream/development -P //stream/development
an error that files are not mapped to workspace view shows and the files are not unshelved


If I go to the command line, the following commands work correctly
p4 unshelve -s 1234 -S //stream/development
p4 unshelve -s 1234 -S //stream/development -P //stream/main

This has worked properly in previous versions of P4V, it seems like 2017.3 erroneously adds the -P parameter forcing an incorrect parent instead of leaving it out or making it selectable in the UI

#2 P4Reg

P4Reg

    Advanced Member

  • Staff Moderators
  • 98 posts

Posted 29 March 2018 - 11:09 AM

Just updating this posting following a support request with the same issue

There is an open bug report for this. You can workaround this issue in P4V by creating a new workspace for your development stream rather than reusing an existing one.





Also tagged with one or more of these keywords: p4v, 2017.3, unshelve, stream, bug

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users