Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-20220

Bamboo does not checkout Perforce changelist that exist in the branch

XMLWordPrintable

      Issue Summary

      Bamboo will checkout the latest changelist in the first build even though it does not exist in the branch. When switching branch in the repository, Bamboo does not checkout the changelist that exist in the branch too.

      Steps to Reproduce

      1. Create branch1 (changelist 10) and branch2 (changelist 11 - the latest changelist in repo) in Perforce
      2. Configure a plan to checkout branch1
      3. Run the plan
      4. Add a commit into branch2 - latest changelist 12
      5. Run the plan
      6. Add a commit into branch1 - latest changelist 13
      7. Run the plan
      8. Edit the repository to configure it to checkout branch2
      9. Run the plan

      Expected Results

      1. First run will show revision 10
      2. Second run will show revision 10
      3. Third run will show revision 13
      4. Fourth run will show 12

      Actual Results

      1. First run show revision 11 - this changelist does not exist in branch1
      2. Second run show revision 11 - new changelist 12 in branch2 does not affect the build
      3. Third run show revision 13 - only detect new changelist in branch1
      4. Fourth run will show 13 - this changelist does not exist in branch2

            [BAM-20220] Bamboo does not checkout Perforce changelist that exist in the branch

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 23 June 2020

            Hi,

            Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.

            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,

            Bamboo Team

            Martyna Wojtas (Inactive) added a comment - Atlassian Update - 23 June 2020 Hi, Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Bamboo Team

              Unassigned Unassigned
              klfoong Foong (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: