Publish Plugins under GitHub organisation

beatrizsanchez · November 23, 2018, 9:47am

Hi I’ve published a plugin in the Gradle Plugin Portal with my gradle account which was created using my GitHub credentials. In GitHub I am part of an organisation and I would like the plugins I publish to the gradle plugin portal to be be associated to that organisation. I can’t find a way to do this and if in fact this feature does not exist, I believe it would be a good new feature.

donv · May 18, 2023, 11:10am

Hi!

Did you ever figure this out?

Vampire · May 18, 2023, 2:14pm

GitHub - gradle/plugin-portal-requests: Gradle Plugin Portal issues and requests. is the place for portal bug reports, feature request, and support requests. If what you ask for is not possible, you should probably open an issue there.

donv · May 19, 2023, 6:46am

Thank you, @Vampire , for your response and for pointing me to the tracker.

The feature as been requested three years ago here:

github.com/gradle/plugin-portal-requests

Support for user groups

opened 05:48PM - 07 Aug 20 UTC

sebersole

a:feature

Not sure how widely useful this would be, but for development teams (such as the… Hibernate project) where more than one developer might work on plugins, it sure would be nice to simply have a group that real users could be added to. At the moment we are forced to create a "group user" and all members of the team need to know the API key for the group user associated with the plugins they wish to publish. It gets worse when someone (such as myself) works on plugins for multiple groups - managing `~/.gradle/gradle.properties` to change the API key based on the group that particular plugin belongs to is simply difficult (if I even happen to remember) ### Expected Behavior It would be very nice if instead a user could instead use there personal portal API key to publish these plugins. This would mean a few changes I assume: 1) The ability to define a group 2) The ability to associate one-or-more users to a group 3) The ability to associate a plugin with a group rather than simply the user who happened to publish it. ### Current Behavior Currently each group must define a distinct user representing the group. An individual developer wishing to publish a group-owned plugin must (remember to) open `~/.gradle/gradle.properties` and change the API key entries for the plugin they plan to publish each time they wish to publish a plugin - which again is difficult when a developer develops / publishes plugins for multiple groups. ### Context I develop multiple plugins. Some of those are "personal plugins" - plugins I develop personally for various things. Some are related to builds for the Hibernate project. Some are related to builds for the Quarkus project. Some are ... Again, opening and changing my `~/.gradle/gradle.properties` every time I publish a plugin is just a real PITA For example, see https://github.com/gradle/plugin-portal-requests/issues/55 and https://discuss.gradle.org/t/share-publishing-of-a-plugin-to-portal-with-users/35290/8

and here: