• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Repository (Perforce)
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3015964 ] New: JAC Suggestion Workflow 3 [ 3595503 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2702559 ] New: JAC Suggestion Workflow [ 3015964 ]
            Owen made changes -
            Backlog Order (Obsolete) Original: 5100000000
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1410810 ] New: Confluence Workflow - Public Facing v4 [ 2702559 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 615346 ] New: Bamboo Workflow 2016 v1 [ 1410810 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2014 [ 600801 ] New: Bamboo Workflow 2014 v2 [ 615346 ]
            James Dumay made changes -
            Workflow Original: Bamboo Workflow 2010 [ 203459 ] New: Bamboo Workflow 2014 [ 600801 ]
            Przemek Bruski made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Thanks Bill.

            Przemek Bruski added a comment - Thanks Bill.

            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.

              Unassigned Unassigned
              edwin@atlassian.com edwin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: