Closed lazarillo closed 1 year ago
Plugin does not install python, it just use already installed python version. Min (python and pip) version properties exists just to fail-fast your build and prevent running with too low python (pip) version. Just a check.
It was an intentional limitation because it's not easy to do automatic python installation in all possible situations (mostly, due to often limited rights).
To install python you could use some other plugin (like jetbrains envs plugin, maybe there are other plugins) or use something else (for example, rely on your CI abilities).
If you have docker installed on your build server, then you can simply use docker image with required python version: plugin would run python tasks inside docker and so there would be no need to install python locally.
The issue, I'm sure, is my own lack of understanding, or maybe a lack of documentation.
But I cannot figure out how to:
I am trying to specifically install a significantly older version of Python 3 than my provider (GCP) puts on its build machines by default, because I want to make sure that the package I am building and uploading is sufficiently backward compatible.
Can someone explain how I can do this, with an example? I have the following, but this is only setting the minimum value, and
checkPython
does not help me to install a new version.Also, I am doing this because I need to build a python package and then publish it to our private (Python) repository. If there is already a pre-built task to do this, I can use that task, too, but for now I already have everything working, except for setting the Python path.