Pipeline node properties does not recognize new environment variables
See original GitHub issueCreate a notebook with some environment variables in a cell:
print(os.getenv('USER', default_value))
print(os.getenv('LOGNAME', default_value))
Add node to the pipeline and then go to node properties
Add more environment variables to the same or another cell:
print(os.getenv('USER', default_value))
print(os.getenv('LOGNAME', default_value))
print(os.getenv('CONDA_DEFAULT_ENV', default_value))
Save the notebook, reopen the pipeline and the node properties
No changes, this is because we are reading/parsing the env_vars values during node add.
This should be fixed by implementing #957 and then integrating on the UI.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (10 by maintainers)
Top Results From Across the Web
How To Set Jenkins Pipeline Environment Variables?
This is an extensive guide to Jenkins pipeline environment variables. Find out how Jenkins set environment variables for all your projects ...
Read more >How to use Jenkins Node Environment Variables in a Pipeline ...
In the Jenkins --> Manage Jenkins --> Manage Nodes --> Configure Node, under Node Properties, you can configure Environment Variables for ...
Read more >Using environment variables - Jenkins
This approach to defining environment variables from within the Jenkinsfile can be very useful for instructing scripts, such as a Makefile , to...
Read more >Jenkins Pipeline Environment Variables - The Definitive Guide
Hi Андрей, you have added environment block inside the script which does not work the way you expect. Instead, you should use withEnv...
Read more >Jenkins Environment Variables: Ultimate Guide - phoenixNAP
Placing this block inside of the pipeline means the variable is available for use at any step of the pipeline. Placing it at...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@kevin-bates you are correct. The implementation does not resonate this today because they were originally created as two distinct extensions without the ability to share code. Now that we managed to merge them as one extension, we should cleanup the implementation.
Also, we should always keep an eye on
submitting notebook
versuspipelines
as they have similar semantics and dialogs but completely different implementations, and this is one behavioral difference.