tony707 Posted April 25, 2016 Report Share Posted April 25, 2016 Hi, We're currently using Plastic SCM for game development and have some concerns with our workflow. We would like to use the branch per task pattern but exclusive checkouts and branching do not work well together. Thats why we want to set before-checkin and before-clientcheckout triggers to ensure the user has the last file version across the whole repository (last checkin in time) and not only the current branch. Before-checkin works fine but the before-clientcheckout trigger seems to only send the file path, and we does not know the current file changeset as provided in before-checkin. Is there a way to retrieve this information ? Thank's for your help. Link to comment Share on other sites More sharing options...
manu Posted April 25, 2016 Report Share Posted April 25, 2016 Hi Tony! I don't see this solution doable. Notice that if you can even prevent the co operation when the artist is not having the asset up to date you'll need to, later, use the merge operation/cherry pick, to get that new revision in the artist wks, which is not very friendly, confusing and I'm afraid sometimes not doable since the source merge changeset will may be storing not only the asset you want, but also more files. What do you think? Link to comment Share on other sites More sharing options...
tony707 Posted April 25, 2016 Author Report Share Posted April 25, 2016 Hi, Yes I know this is not friendly but everyone begin to be used to branching. This solution could have ensure only one new revision exists at a time in every branch and pervent merge conflicts. So you say people working on unmergeable files should only work on the same branch with exlusive checkouts ? Is it possible to setup partial read only files ? Let's say we only want to set readonly the files that need to be checkout ? THank you Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.