Body: <p>Two weeks ago the deployment time for my Azure Bots started to be totally atypical</p>
  
  <p>Before it was running between 2-4 minutes max. but since then it takes more than 30mins or most of the times directly fails and the only output I see is the following:</p>
  
  <p>Log file:
  <a href="https://pastebin.com/axHujWam" rel="nofollow noreferrer">deploy.log</a></p>
  
  <pre><code>Thread was being aborted.
  Thread was being aborted. 
  </code></pre>
  
  <p>that doesn't say that much.</p>
  
  <p>This fails when I configure the continuous deployment option through the portal.azure site. If I disconnect it and set up the autodeploy from the visual studio team services sites it works.</p>
  
  <p>In the activity log I could find this:</p>
  
  <blockquote>
    <blockquote>
      <p>Operation name Write Deployments</p>
      
      <p>Time stamp Thu May 17 2018 14:46:49 GMT+0200 (W. Europe Daylight Time)</p>
      
      <p>Event initiated by XXXXX@XXXX.XXX</p>
      
      <p>Error code ClientClosedRequest</p>
      
      <p>Message The connection has been closed by the client while the server is still processing its request for 'Microsoft.Web'.</p>
    </blockquote>
  </blockquote>
  
  <p>Any idea about this?</p>
  
Comments: CC BY-SA 4.0
Comments: 2018-06-04T18:16:48.087Z
Comments: I agree. Azure CI is very slow. I am thinking of moving to alternative way of deployment to azure using Chef.
Comments: emp51302
Comments: CC BY-SA 4.0
Comments: 2018-06-05T09:41:02.903Z
Comments: This sounds like a support case for Azure, I don't see how anyone could have the slightest idea on what's going wrong there without working for Azure.
Comments: Tensibai
Comments: CC BY-SA 4.0
Comments: 2018-06-06T06:38:28.897Z
Comments: @Tensibai you are right. I opened a ticket in support, but I thought maybe someone could be aware of the problem and found a setting to tweak the deployment
Comments: blfuentes
Tags: <continuous-integration><continuous-deployment><azure><azure-devops>
Title: Continuous integration azure slow or fails
UserDisplayName: blfuentes
ThreadText: # Continuous integration azure slow or fails
  
  (Asked by: username_0 on 2018-05-17)
  
  Two weeks ago the deployment time for my Azure Bots started to be totally atypical
  
  Before it was running between 2-4 minutes max. but since then it takes more than 30mins or most of the times directly fails and the only output I see is the following:
  
  Log file:
  [deploy.log](https://pastebin.com/axHujWam)
  
  ```
  Thread was being aborted.
  Thread was being aborted. 
  
  ```
  
  that doesn't say that much.
  
  This fails when I configure the continuous deployment option through the portal.azure site. If I disconnect it and set up the autodeploy from the visual studio team services sites it works.
  
  In the activity log I could find this:
  
  > > Operation name Write Deployments
  > >
  > > Time stamp Thu May 17 2018 14:46:49 GMT+0200 (W. Europe Daylight Time)
  > >
  > > Event initiated by XXXXX@XXXX.XXX
  > >
  > > Error code ClientClosedRequest
  > >
  > > Message The connection has been closed by the client while the server is still processing its request for 'Microsoft.Web'.
  
  Any idea about this?
  
  **Tags:** continuous-integration, continuous-deployment, azure, azure-devops
  
  > **Comments:**
  > **username_1**: I agree. Azure CI is very slow. I am thinking of moving to alternative way of deployment to azure using Chef.  
  > **username_2**: This sounds like a support case for Azure, I don't see how anyone could have the slightest idea on what's going wrong there without working for Azure.  
  > **username_0**: @username_2 you are right. I opened a ticket in support, but I thought maybe someone could be aware of the problem and found a setting to tweak the deployment  
  
  ---
  
  ## 0 answers
  
  