The pipeline always run on a bad agent.

[zszen]

I have two agent for gocd-server. One on ubuntu installed with apt tool. Another run on docker compose (it is not good).

I duplicate a pipeline. It run on the bad agent. And it don't change agent after I remove the docker-agent. I also input the resource keywords for lock on the right one. But it don't work. .

Now I have only one agent. And the pipeline always waiting a agent. ;(

[chadlwilson]

Can you share your agents page? And the job configuration for the def job in that pipeline (I.e which resources it requires to run)

[zszen]

pipeline job's resource

agents list

history. The task timeout

[chadlwilson]

Is your 'nacos_standalone' pipeline assigned to the 'docker' environment?

Your agent is configured with that environment so will only run matching pipelines.

If not, you can either remove the environment from the agent or map the pipeline.

[zszen]

I deleted the problem agent yet before that. the only agent is the right env for pipeline. I have two pipelines. The first is correct runing on the ubuntu agent. But the problem one can't re-choice agent. Always waiting for the problem agent which I deleted.

I found that I add nacos pipeline to env. it works. I don't understand. does not global env only set env variable only ?

[chadlwilson]

Environments are a way to both set environment variables for ALL pipelines, as well as a way to segregate where ALL jobs in a pipeline run, without setting resources at the job level.

For example, if an agent used for deployment only has access to the production environment, you want to reflect that so agents for other environments don't pick up jobs for production.

You don't need to use environments if you don't want to use either of these capabilities. Agents without an environment set will pick up jobs for pipelines which ALSO don't have an environment (aka the "default“ environment)

Use the docs :)
https://docs.gocd.org/current/configuration/managing_environments.html