showing my agent is unassigned.

[Rohan Paunikar]

hi,

can anyone help me it is showing my agent is unassigned. but it is there.

Rohan

[Chad Wilson]

Hi Rohan

From this part of your screenshot of the agent, it looks like your agent has been designated with the custom Environment "Default" and Resource "Windows".

Is the pipeline you are running part of an environment called "Default"? With this agent configuration, your pipeline would need to be part of the same environment in order to have pipelines run on this agent, as in the docs.

If you are not intending to use environments to control which jobs can run on your agent (in other words - you are OK to run pipelines from ANY environment on the same agent), you are probably best to not have the agent declare any environments at all. In that case the UI will say 'none specified'.

The other reason that it cannot be assigned may be that your job declares that it requires a Resource other than "Windows", as declared by the agent. If your job doesn't declare any required resources, this won't be the reason for failure to assign an agent.

Hope that helps - otherwise please share the job configuration in more detail to avoid guesswork. :-)

-Chad

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/49161da6-fee1-4978-8ecf-45ffbc2574b2n%40googlegroups.com.

[Rohan Paunikar]

Thanks Chad for help. My issue is resolved. Yes it was happened bcaz of the envirnment.

Rohan