Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13924

Very inefficiently deleting CloudFormation stack

      When waiting for the CloudFormation stack to delete, the method is calling DescribeStacks without passing in a StackName. This results in a call that will get all the information about all stacks, not just the one we are waiting for. This adds a lot of time to call. By simply adding the name into the call, we make a much lighter and faster call. This was already done while waiting for the stack to create.

          [JENKINS-13924] Very inefficiently deleting CloudFormation stack

          Damon Evans added a comment -

          Fixed patch. The original one didn't handle the exception that was thrown (I had confused it with the ListStacks call).

          Damon Evans added a comment - Fixed patch. The original one didn't handle the exception that was thrown (I had confused it with the ListStacks call).

          lsb want added a comment -

          dazigizad
          Thanks for you provide the patch.
          Which patch should I use? or both two patch.
          and I got other issue that if one job launch two job instance and job configurate to delete automatic when job done, the one instance will delete all Stack created by the two job instance. I don't whether have any relationship with this issue.

          lsb want added a comment - dazigizad Thanks for you provide the patch. Which patch should I use? or both two patch. and I got other issue that if one job launch two job instance and job configurate to delete automatic when job done, the one instance will delete all Stack created by the two job instance. I don't whether have any relationship with this issue.

            edovale edovale
            dazigizad Damon Evans
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: