I have set my an environmental variable in my setup.py script and I would like to access this in my Pipelines script.
os.environ["MY_PKG_VERSION"] = str(version)
The thing is every time I echo this in my Pipelines script
- echo $MY_PKG_VERSION
nothing shows up. I tried creating an unsecured environmental variable in Pipelines (Settings->Pipelines->Environmental Variables) and accessed it via Python to update it, but this doesn't update it despite it working locally.
import os import re # Update the current version to the new version current_version = os.environ['MY_PKG_VERSION'] release_version = int(re.sub(".\d+$", "", current_version)) patch_version = int(re.sub("^\d+.", "", current_version)) new_patch_version = patch_version + 1 new_version = "%d.%d" % (release_version, new_patch_version) # Set version number as environmental variable os.environ['MY_PKG_VERSION'] = new_version print(current_version) print(new_version)
If $MY_PKG_VERSION is set to 0.1, then current_verision==0.1 and new_version==0.2. This script is run via Pipelines without failing and the print() outputs are displaying the correct values.
Ideally, I would be able to use the environmental variable set in my Python code within the Pipelines script by concatenating it to another string.
Any ideas on how to go about achieving this?
I am looking for changing the "APPLICATION_ENVIRONMENT" directly in bitbucket-pipelines.yml. Any idea how to do that?
We have specific branches that need to de deployed on specific environment on AWS Beanstalk?
Thank you for your help.
Bitbucket Pipelines environment variables are currently immutable. So you are unable to modify them during your build.
In regards to having the version numbers, you should follow this issue for updates: https://bitbucket.org/site/master/issues/12838/build-number-that-increments-on-every
If you need a unique identifier for you version and are okay with it not being an ordered number, you can use the environment variable $BITBUCKET_COMMIT.
Are there any other use-cases for you where you would want to modify an environment variable, or just for version numbers?
My use case is purely for modifying the version number, which is pretty critical. I see the ticket was opened six months ago. Is Atlassian intended to add the feature of either setting environmental variables or having an auto incriminating version number attainable also as an environmental variable?
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs