Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-1237

Builder and Global level environment variables

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • Tasks, Variables
    • None
    • 0

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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.

            Unassigned Unassigned
            57b2883d76f9 Eric White
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: