[GRADLE-3273] Add ability to specify publish api key and secret via plugin bundle DSL Created: 07/Apr/15  Updated: 24/Jan/17  Resolved: 24/Jan/17

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

Type: Improvement
Reporter: Tom Dunstan Assignee: Tom Dunstan
Resolution: Duplicate Votes: 3


Should be possible to set publishing api key / secret via the plugin bundle DSL. This allows using environmental variables or other sources for these values, when setting via gradle.properties or system properties is not preferred.

One use-case for this is public CI systems that don't mask secure vars when echoing out the command line.

Original report: http://discuss.gradle.org/t/add-apikey-and-apisecret-to-pluginbundle-extension-for-plugin-publish-plugin/8636

Was using Travis CI, not sure if Travis masks secure vars that are part of a command line, but it's a valid request nonetheless.

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 Micah Zoltu [ 20/Nov/16 ]

I believe this request meets the criteria for being retained. It should be categorized as a feature request I believe.

Comment by Eric Wendelin [ 24/Jan/17 ]

Moved to https://github.com/gradle/gradle/issues/1246

Generated at Wed Jun 30 12:44:30 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.