Deployment: 0 agents started deployment (minimum: 1)

alessandro's Avatar

alessandro

Mar 22, 2017 @ 12:19 PM

After the latest Appveyor update, on the 2nd of March, our deployments stopped working. Apparently the deployment agent cannot be contacted or times out when the deployment command is sent. The deployment log can be found below:

Sending message to connected AppVeyor agents to start deployment... Waiting for remote deployment agents to start deployment... 0 agents started deployment (minimum: 1)

  1. 1 Posted by Ilya Finkelshte... on Mar 22, 2017 @ 04:16 PM

    Ilya Finkelshteyn's Avatar

    Hi Allessandro,

    Please take a look at this discussion for explanation and workaround. Did in you case deployment actually happened on remote server(s)?

    Ilya.

  2. 2 Posted by alessandro on Mar 30, 2017 @ 01:10 PM

    alessandro's Avatar

    Ilya,

    The discussion you provided does not offer a proper solution to the problem. The problem is that no deployment agent is picking up the job after the 2nd of March update. The "workaround" described in the discussion just ensures that a deployment that doesn't get picked up by agents is considered successful.

  3. 3 Posted by Ilya Finkelshte... on Mar 30, 2017 @ 03:36 PM

    Ilya Finkelshteyn's Avatar

    Oh, I see, sorry, I misunderstood that. So in your case 2nd of March change achieved what it was intended to achieve -- expose deployments that silently fails. I suspect that it could fail before 2nd of March, but did not manifest itself. Could you please go to target server(s) and check event log messages in AppVeyor event log (located under Applications and Services log)? Also what you see if you restart AppVeyor deployment agent service?

    Ilya.

  4. Ilya Finkelshteyn closed this discussion on Aug 25, 2018 @ 02:15 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac