Deployments saying "0 agents started deployment (minimum: 1)" when everything else appears to work

andrew.c's Avatar

andrew.c

20 Mar, 2017 04:29 PM

Our deployments are not working correctly. We are using the AppVeyor Agent, and the deployment has worked (see Deployment-summary.png)

The Deployment section says:

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

What does this mean? and how can we fix it?

  1. Support Staff 1 Posted by Feodor Fitsner on 20 Mar, 2017 04:35 PM

    Feodor Fitsner's Avatar

    AppVeyor update has been deployed and now, by default, agent deployment is failing if no agents responded to deployment event: https://github.com/appveyor/ci/issues/1337#issue-209336465

    In case you need "original" behavior when agent deployment is green if no agents responded add agents_expected to agent provider settings with value set to 0 (expect no agents):

    agents_expected: 0
    
  2. 2 Posted by andrew.c on 20 Mar, 2017 05:17 PM

    andrew.c's Avatar

    Thanks I can add this which may fix the status, but it feels like something is wrong because an agent did respond - the deployment to TESTSERVER succeeded, and this used the agent?

  3. Support Staff 3 Posted by Ilya Finkelshte... on 20 Mar, 2017 05:21 PM

    Ilya Finkelshteyn's Avatar

    Hi Andrew,

    Deployment log screenshot does not display TESTSERVER added to the deployment. Can you please provide us screenshot of TESTSERVER deployment? Also screenshot of your environment settings and YAML file will not hurt.

  4. 4 Posted by andrew.c on 20 Mar, 2017 05:33 PM

    andrew.c's Avatar

    Our environment settings are not in the yml, (except for the name) I've screenshots that may help.

    One thing we've wonder may be causing this is at the same time we do this deployment we do about 20 other on the same agent from the same build. The project has many components and each component is set up with a separate appveyor "deployment".

  5. Support Staff 5 Posted by Feodor Fitsner on 20 Mar, 2017 06:57 PM

    Feodor Fitsner's Avatar

    OK, this might be a racing condition (checking deployment status and the agent added deployment job). I've added an issue to introduce custom waiting timeout: https://github.com/appveyor/ci/issues/1423

  6. 6 Posted by andrew.c on 21 Mar, 2017 08:46 AM

    andrew.c's Avatar

    Do you think there is something about our setup that is causing this? it didn't happen last week. It doesn't happen every time now on every deployment.

  7. 7 Posted by andrew.c on 21 Mar, 2017 10:10 AM

    andrew.c's Avatar

    We've added into our "AppVeyor Agent" environment settings

    ARTIFACT.agents_expected = 0

    but still the Deployment step still says "(minimum: 1)"

    Does the documentation needs updating to include this setting? are we using it incorrectly?

  8. 8 Posted by andrew.c on 21 Mar, 2017 12:15 PM

    andrew.c's Avatar

    agents_expected = 0 instead of ARTIFACT.agents_expected = 0 solves the problem

  9. Support Staff 9 Posted by Ilya Finkelshte... on 21 Mar, 2017 02:40 PM

    Ilya Finkelshteyn's Avatar

    Thank you for update. Yes it is "global" setting. Sorry for the trouble. We tried to make customers aware of situation where no agents picked up the job, but it seems that we need to make is smarter. Please watch this issue.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Already uploaded files

  • Deployment-detail.png 13.2 KB
  • Deployment-summary.png 3.56 KB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

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