-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
In Perforce, after sync with depot, the files in workspace are read only so any build processes which tries to modify them will fail.
Allow write operations on Perforce workspaces.
[BAM-1364] Perforce checkout files to be writable
Deleted Account (Inactive)
added a comment - There are ways to work around this from within the plan. The files that need to be modified can be checked out prior to the stage/job that needs to modify them. For example, the teams I work with need to update a resource file with a build number (that is not the Bamboo build number). That file is checked out, incremented and checked in within the build.
Perforce is a pretty flexible platform. If people want to use it the way that is described here, it is happy to oblige. One need only define the workspace with the option "allwrite" in the client specification. See this link for details: http://www.perforce.com/perforce/doc.current/manuals/p4guide/02_config.html#1067985
I don't see any need for Bamboo to support this, because it can be defined by the Perforce user.
Deleted Account (Inactive)
added a comment - There are ways to work around this from within the plan. The files that need to be modified can be checked out prior to the stage/job that needs to modify them. For example, the teams I work with need to update a resource file with a build number (that is not the Bamboo build number). That file is checked out, incremented and checked in within the build.
Perforce is a pretty flexible platform. If people want to use it the way that is described here, it is happy to oblige. One need only define the workspace with the option "allwrite" in the client specification. See this link for details: http://www.perforce.com/perforce/doc.current/manuals/p4guide/02_config.html#1067985
I don't see any need for Bamboo to support this, because it can be defined by the Perforce user. Bill, I've rephrased the description.
To be honest, I don't think this feature should be implemented, it goes against basic Perforce usage principles. What do you think?
Deleted Account (Inactive)
added a comment - There's a terminology overload causing confusion here. Some other products (svn, cvs, maybe git?) retrieve source from the repository and call that a checkout (even though it's not reserved in any way), leaving it writable. Let's not confuse their paradigms with Perforce's, which is more like that of ClearCase or PVCS - where checking out is an explicit reservation of a file for editing.
In Perforce lingo, getting files from the depot is called a sync, not a checkout. A checkout/edit/open action reserves the user the ability to edit the file and then submit it back to the respository. Perforce never checks out files as read-only. Perforce fetches/syncs workspace files as read-only.
In Perforce, checked out files are reserved for editing, and are by nature writable.
Deleted Account (Inactive)
added a comment - There's a terminology overload causing confusion here. Some other products (svn, cvs, maybe git?) retrieve source from the repository and call that a checkout (even though it's not reserved in any way), leaving it writable. Let's not confuse their paradigms with Perforce's, which is more like that of ClearCase or PVCS - where checking out is an explicit reservation of a file for editing.
In Perforce lingo, getting files from the depot is called a sync, not a checkout. A checkout/edit/open action reserves the user the ability to edit the file and then submit it back to the respository. Perforce never checks out files as read-only. Perforce fetches/syncs workspace files as read-only.
In Perforce, checked out files are reserved for editing, and are by nature writable.
Thanks Bill.