Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Export env vars that point to cloned path #1

Closed
PI-Victor opened this issue Feb 5, 2019 · 2 comments
Closed

Export env vars that point to cloned path #1

PI-Victor opened this issue Feb 5, 2019 · 2 comments
Labels
enhancement New feature or request to do
Milestone

Comments

@PI-Victor
Copy link
Owner

Export env variables with the name that was defined as alias in the config.yaml plus WORKSPACE.
e.g.: API_WORKSPACE
This env variable will have the full path to where we cloned the repository.

@PI-Victor PI-Victor added this to the v1.0.0 milestone Feb 5, 2019
@PI-Victor PI-Victor added enhancement New feature or request to do labels Feb 5, 2019
@PI-Victor
Copy link
Owner Author

although, in hindsight, these variables might be shell session bound.
Their lifecycle might be over by the time jenkins would try to use them.

@PI-Victor PI-Victor pinned this issue Feb 5, 2019
@PI-Victor
Copy link
Owner Author

environment variables set with os.environ['TEST'] = 'test' are process bound, which means they are gone after the app finishes.
an alternative would be to use the python shell command to export them to the env.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request to do
Projects
None yet
Development

No branches or pull requests

1 participant