It can not work for repo: ourregistry.com/${CI_REPO_OWNER}/$repo_name because it not expands those variables registry_url and repo_name and they are blank.
I read the documents. I think this not available now - we can expand env vars in commands: block only. (I am correct?)
We have microservices and so many '.woodpecker.yml' files! Very hard to use. So would be good to have them "DRY" with more variables substitution/expansion.
Clear and concise description of the problem
Hello!
We can use environment var like:
But not like this (I use docker plugin only for example):
It can not work for
repo: ourregistry.com/${CI_REPO_OWNER}/$repo_name
because it not expands those variablesregistry_url
andrepo_name
and they are blank.I read the documents. I think this not available now - we can expand env vars in
commands:
block only. (I am correct?)We have microservices and so many '.woodpecker.yml' files! Very hard to use. So would be good to have them "DRY" with more variables substitution/expansion.
Suggested solution
Please can we use env vars anywhere in file?
Alternative
No response
Additional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]