I am trying to identify how to provide the value of the "version" field on one or more of the wheel files were are generating. This value would eventually be provided from our build system (currently gitlab). Is there a way to pass this into a given invocation of pants. In other words:

python_distribution(
    name="tools_dist",
    dependencies=[
        "tools:tool_files",
        "tools:tools_pyproject",
        "tools/src:tools_lib",
        "shared:shared_dist",
    ],
    provides=python_artifact(
        name="awesome_tools",
        version = "$WANT_THIS_TO_BE_SOME_MAGIC_VARIABLE_SET_AT_PANTS_RUN_TIME",
        authors = "Ryan",
        authorEmail = "<mailto:rmahoney@aledade.com|rmahoney@aledade.com>",
        readme = "README.md"
    ),
    sdist=False, # Do NOT generate an sdist (as a result only a wheel is generated)
)

Is there a way to pass this into a given invocation of pants.

You may leverage environment variable for this:

...
    python_artifact(
        name="awesome_tools",
        version = env("SOME_VERSION", "0.0.0"), # the 0.0.0 part is an optional default in case the env var is undefined.
        ...

then:

# SOME_VERSION=1.2.3 pants package ...

Oh thank you! that is WAY easier.

sweet

I'll role my version up to rc4 and go my merry way!

+1 to that, the env() tool will be amazing, can’t wait to use it!

hi @cool-account-59189 I have been following your attempts of using vcs_version and the env in the python_artifact. Did you managed to inject it ? I am not able to figure it out by myself, so any help would be welcome 🙏

hiya, yup hold on I'll paste in what we ended up doing:

I see, this is similar of what I came up after reading your threads. As I have many artifacts and projects, I expose the versions in file in the rood of the monorepo: VERSIONS.env

export AWESOME_PROJECT_SPECIFIC_WHEEL_BUILD_VERSION=0.0.1
export AWESOME_PROJECT_2_SPECIFIC_WHEEL_BUILD_VERSION=0.0.1

and then in each BUILD file:

provides=python_artifact(
        name="awesome_tools",
        version=env("AWESOME_PROJECT_SPECIFIC_WHEEL_BUILD_VERSION", "0.1.0"),
        author="Awesome",
        author_email="<mailto:support@awesome.com|support@awesome.com>",
        long_description_content_type="text/markdown",
    ),

provides=python_artifact(
        name="awesome_tools",
        version=env("AWESOME_PROJECT_SPECIFIC_2_WHEEL_BUILD_VERSION", "0.1.0"),
        author="Awesome",
        author_email="<mailto:support@awesome.com|support@awesome.com>",
        long_description_content_type="text/markdown",
    ),

So i generate the packages as

source VERSIONS.env && pants package ::

This helps me to maintain all the versions explicit in one entrypoint, but it forces our team to manually bump versions by hand before merging and deploying, which is prone to errors. That's why I was interested in still injecting the

vcs_version

, but I think it is still not possible, and also I wonder if it would just update all versions at once with the last commit / tag (unless I do the --changed-since=origin/main, or something)...not sure what is going to be the optimal solution to us. If I manage to automatize it or create a plugin worth to share I will keep you updated ! many thanks @cool-account-59189 !

So in our build environment (gitlab) the value of that environment variable is set to something like:

OH WOW !!!! that is actually an approach I totally missed as I was just with tunnel vision around the vcs_version !! You just made my day !!