Jump to content


Tracing revision history of shelve

shelve

  • Please log in to reply
2 replies to this topic

#1 engr.vns

engr.vns

    Advanced Member

  • Members
  • PipPipPip
  • 43 posts

Posted 29 June 2020 - 07:40 AM

Is there a way to track the revision history of a shelf create by another user such as - when it was last updated and what the changes to the shelf were?
Sometimes, a shelf is provided by a user to be unshelved and used. Subsequently the shelf may have been updated by the provider (add/delete files)

Does the p4 server maintain revision history of a shelf?

Thanks

#2 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 1192 posts

Posted 29 June 2020 - 03:03 PM

No, shelves are not themselves versioned.  At that point what you want is a branch; each revision to a branch is stored forever and can be referenced even after the branch has been merged back to the parent.

#3 CarolineB

CarolineB

    Advanced Member

  • Members
  • PipPipPip
  • 44 posts

Posted 02 September 2020 - 07:26 AM

If I may, there could be a way to get an history for your shelve, if you use Swarm & reviews. When using Swarm reviews, Perforce stores in some changelists all the intermediate steps, the successive modifications which have been done on your reviewed shelved files; you can see that with the Swarm API, when asking info about a review clNumber:

  curl -l $swarmURL/api/v9/reviews/clNumber | jq '.[] | { changes: .changes, commits: .commits}'
   { "changes": [

    434321,

    434371,

    435690,

    435698,

    440123,

    442456],

...

}


434321 being the initial number of the CL, containing the first shelved files content, and the other CLs storing the evolutions on your shelved files. These intermediate CLs are created by Swarm, using a service account.


Thus, with this, you can get an history, but it means you have to use Helix Swarm :)







Also tagged with one or more of these keywords: shelve

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users