Currently, environment variables may be set per plan.
For environments with a large number of plans, it would be handy to be able to define environment variables globally for a particular builder or globally.
Users, should be given option to set user environment levels per builder or globally.
Example: My maven is running out of memory, and requires the environment variable
MAVEN_OPTS="-Xms512m -Xmx1024m -XX:MaxPermSize=512m"
to be set.
I would like to be able to set this to a reasonable level for anything built with maven, but don't want to edit 120 plans to do this.
The problem is Bamboo will pick up JAVA_OPTS from command line and pass it down to the build: we should be able to override JAVA_OPTS or any other variable at a global or per builder level.
- is related to
-
BAM-7132 Project Level Global Variables
- Closed
[BAM-1237] Builder and Global level environment variables
Workflow | Original: JAC Suggestion Workflow [ 3016339 ] | New: JAC Suggestion Workflow 3 [ 3606462 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2702922 ] | New: JAC Suggestion Workflow [ 3016339 ] |
UIS | New: 0 |
Backlog Order (Obsolete) | Original: 11670000000 | |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1418386 ] | New: Confluence Workflow - Public Facing v4 [ 2702922 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Component/s | New: Variables [ 18191 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 618339 ] | New: Bamboo Workflow 2016 v1 [ 1418386 ] |
Workflow | Original: Bamboo Workflow 2014 [ 604424 ] | New: Bamboo Workflow 2014 v2 [ 618339 ] |
Workflow | Original: Bamboo Workflow 2010 [ 202334 ] | New: Bamboo Workflow 2014 [ 604424 ] |