Add environment variable to existing matrix (TravisCI) migration #3317
-
I don't have WoodpeckerCI at hand but plan to migrate to Codeberg.org which do host an instance. The config seems quit similar to TravisCI. I burn a lot of energy and hours at TravisCI. So I would like to point out one of my conceptual problems with Travis and want to find out if Woodpecker handle this differently. There is a quiet simple config for Python.
This will result in 6 jobs (3 Python versions x 2 architectures) all using PYTHONUNBUFFERED. Now I want to add another environment variable to two of the jobs running Python 3.8.
My problem on TravisCI and its logic is that this doesn't add this variable to the existing job but it simply creates a 7th job not using PYTHONUNBUFFERED (which is IMHO configured on a global level) but FOO. How would I solve this with Woodpecker? One important thing here is to keep the matrix implicit. I just give a list of 3 Python versions and 2 architectures. The matrix (6 jobs) is created implicit and automatic. I don't want to change that. Most TravisCI example I could find to start naming each of the 6 jobs explicit via "include:". So you will have 6 "include" repeating some of the same configs. When you want to modify something on a global level (e.g. modify the value of PYTHONUNBUFFERED) you have to edit all 6 includes. This redundancy is IMHO unneeded and gives a high risk of introducing undiscovered bugs. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
You could use something like this: matrix:
include:
- PYTHON: "3.8"
FOO: bar
- PYTHON: "3.9"
- PYTHON: "3.10" |
Beta Was this translation helpful? Give feedback.
You could use something like this: