[GRADLE-1368] Load properties from a global gradle.properites file Created: 04/Feb/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Improvement
Reporter: Joe Schmetzer Assignee: Unassigned
Resolution: Won't Fix Votes: 1


Our build system uses the $HOME/.gradle/gradle.properties to store the location of our central repo and associated credentials. However, this file is difficult to centrally maintain for all developers, as well as our large continuous integration build farm. It simplify things a lot if gradle would also read properties from a global gradle.properties file (e.g. /etc/gradle/gradle.properties on a unix-like system). This file could then be easily pushed out to all our users and build farms without having to manage complex per-user directory logic.

Comment by Hans Dockter [ 05/Feb/11 ]

I think that would make sense. Configuration management is anyhow an area where we have a lot of plans to make things richer and more flexibile.

Comment by Luke Daley [ 17/Feb/12 ]

I'm not sure about adding direct support for this.

At the moment you could achieve this by using a distribution init script which loads the properties file from wherever you like and apply it.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:53:47 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.