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

Repository checkout tasks (CVS) should respond to stopping the build

XMLWordPrintable

    • 1

    • 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.

      Bamboo build hangs, if there is an issue with repository check-out on manual builds and stopping the build has no affect.

      I first noticed this behaviour during blitzkrieg testing last week - and Mark just told me, the issue was also reported by Andreas in Bamboo 1.2x

            [BAM-2123] Repository checkout tasks (CVS) should respond to stopping the build

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 7 April 2020

            Hi,

            Thank you for raising this suggestion. 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.

            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 - 7 April 2020 Hi, Thank you for raising this suggestion. 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. 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

            James Dumay added a comment -

            Hi David,

            This has been reported before (and I tried to fix this years ago when I was still a developer) but unfortunately I can't find the ticket. From what I remember, the very old CVS library (from Netbeans) does not allow its thread to be interrupted which is what the build management code uses to stop a version control request.

            To be honest with you it is unlikely that we will update the CVS implementation to be interruptible since CVS is used by a increasingly small amount of teams. Apart from this issue, the CVS implementation doesn't have any huge issues and I believe it would be too risky to update it to a newer version.

            If you see this behaviour on Subversion or any other version control system we support we would be able to fix it with a higher degree of confidence.

            Thanks
            James

            James Dumay added a comment - Hi David, This has been reported before (and I tried to fix this years ago when I was still a developer) but unfortunately I can't find the ticket. From what I remember, the very old CVS library (from Netbeans) does not allow its thread to be interrupted which is what the build management code uses to stop a version control request. To be honest with you it is unlikely that we will update the CVS implementation to be interruptible since CVS is used by a increasingly small amount of teams. Apart from this issue, the CVS implementation doesn't have any huge issues and I believe it would be too risky to update it to a newer version. If you see this behaviour on Subversion or any other version control system we support we would be able to fix it with a higher degree of confidence. Thanks James

            David Ehringer added a comment -

            Hi James,

            The OS is RHEL 5.6 and 6.x. Our version control is mostly SVN (although I haven't seen this issue with SVN) but we do have CVS as well, which is where this has been happening.

            Thanks,
            Dave

            David Ehringer added a comment - Hi James, The OS is RHEL 5.6 and 6.x. Our version control is mostly SVN (although I haven't seen this issue with SVN) but we do have CVS as well, which is where this has been happening. Thanks, Dave

            James Dumay added a comment -

            Hi David,

            What operating system is your build running on and what version control do you use?

            Thanks,
            James

            James Dumay added a comment - Hi David, What operating system is your build running on and what version control do you use? Thanks, James

            David Ehringer added a comment -

            This bug is still an issue in Bamboo 4.3.

            David Ehringer added a comment - This bug is still an issue in Bamboo 4.3.

              Unassigned Unassigned
              Anonymous Anonymous
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: