How to disable read-only sandbox creation for mainline project

[pnone]

Hello Support,

In the mainline version of a project, whenever a user creates a sandbox, all the files on the PC are read-only mode.

Is there any way, where this feature can be disabled automatically for that mainline project hierarchy so that whenever sandbox is created, all the files on the PC are with read-write permission instead of read-only?

Thank you.

Regards

Pashan

[MichaelChatel · Accepted solution]

Hi Pashan,

This is likely due to the "locking policy" that is being used or your Integrity server configuration.  Lock policies can be set via the Administration Tool -> Configuration Management -> Policies -> Global Policies -> Locks  (you could also setup project-specific policies too)

The behaviour you describe, is by default. What is the reason or business case you're trying to solve, in having the whole sandbox be writable by default?

[pnone]

Hello Michael,

Only for a sub-project we want to have Read-Write access after new Sandbox creation.

Default is Read Only, which is fine for all the projects.

How do I change this default behavior only for a particular sub-project hierarchy?

This is needed because of our software build process which modifies the source files after creating the Sandbox.

Thank you.

Regards

Pashan

[KaelLizak]

Hello Pashan None‌,

From the command line, you can do this via CS144402‌, assuming you're using your software build process to create the sandbox as well.

Also, you could just have the local operating system make the files all writable.

Kind Regards,
Kael

[tdalon]

You could also remove the Read-Only attribute by script afterwards (see attrib command).