Unmet requirements

I tried to pass an env variable to my script in "command parameters". Like this : "mycommand -p %env.myvar%". But when I do this, it prompts "incompatible agents"->"Unmet requirements: env.myvar exists". What does it mean? I am sure I don't have myvar defined anywhere else.

3 comments
Comment actions Permalink

It means TeamCity did not find such environment variable on any agent. What are you trying to achieve? Who should provide value for this environment variable?

0
Comment actions Permalink

Oh, I see. The environment var is passed to TeamCity server through HTTP request like this: curl .http://..&env.name=xxx&env.value=xxx. I want to use the var in my agent command line script. So seems the right way is to first define an empty var first, and then let the http request parameter to overwrite the empty var. Is this correct?

Thanks,

Raymond

0
Comment actions Permalink

Yes, you should add environment variable to the build configuration with some value. This is because requirements to start a build are calculated on the base of build configuration settings. We will address this problem in the future releases.

0

Please sign in to leave a comment.