Plugin publish fails:

Help/Discuss Plugin Portal
#1

I received the following error trying to publish gradle-clojure.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':gradle-clojure-plugin:publishPlugins'.
> Failed to post to server.
  Server responded with:
  Website, 'https://github.com/gradle-clojure/gradle-clojure', is invalid: URL must not contain github.com/gradle

Seems like the validation is overreaching here. Maybe search for github.com/gradle/ instead?

Let me know if you need any more information to get this fixed.

Build scan

#2

Are you doing this?

   ...{
          website = 'https://gradle-clojure.github.io/gradle-clojure/'
          vcsUrl = 'https://github.com/gradle-clojure/gradle-clojure'
          ...
      }

Or this?

   ...{
          website = 'https://github.com/gradle-clojure/gradle-clojure'
          vcsUrl = 'https://gradle-clojure.github.io/gradle-clojure/'
          ...
      }

I think you want the first one.

Reading the error message, it looks like it thinks you’re trying to publish to a namespace reserved for the Gradle organization’s plugins. Which I think is what the second snippet would be doing.

Do you work for Gradle?

#3

I’m doing this.

pluginBundle {
  website = 'https://github.com/gradle-clojure/gradle-clojure'
  vcsUrl = 'https://github.com/gradle-clojure/gradle-clojure.git'
  //...
}

I don’t work for Gradle, and I agree that they’re trying to reserve a namespace for themselves. However, I’m expecting they were trying to reserve the gradle organization on GitHub, rather than any user/org beginning with gradle. Since there are a number of plugins whose names start with gradle-, this isn’t likely to be an issue limited to gradle-clojure.

#4

You’re right. Plus I see it’s obviously worked for you before.

#5

Howdy ajoberstar,

Did you ever get that fixed? What was the solution?

#6

I haven’t tried again, and haven’t had a response here. Not sure if there’s some other place I should submit this. I don’t believe they have a public repo for the plugin portal or the plugin publish plugin.

#7

It’s real easy to get the impression that Gradle’s people aren’t super duper enthusiastic about helping out the non-paying members of their community. Or is it just me? :wink:

Have you tried their „How do I get further help?“ form?

There’s nothing in Gradle’s Plugin Portal Approval Policy (by @eriwen) that explicitly says you should not expect what you did to work. After all, the same thing worked before. So your situation could be seen as a „regression defect“ on Gradle’s part.

If you don’t get a reply to your direct request for help, maybe raising an issue in github should be your next step?

1 Like
#8

Hey Andrew,

Sorry for the delayed reply here. This is an overzealous check that the group when publishing plugins cannot contain “gradle”.

The whole Gradle team is traveling internationally this week, so support will be delayed unfortunately. I will notify responsible folks of this request, but the quickest resolution will be to use something else other than “gradle” in the group ID when publishing for now.

Don’t be afraid to use the “further help” form suggested by @lingocoder which sends support folks an email.

Cheers,
Eric

1 Like
How time have need the Gradle plugin for the load on the plugins.gradle.org
#9

Thanks for that info. Looks like it checks the VCS url too, and I can’t practically do anything about that one. I’ll have to wait until you guys are able to make a fix. I’ll send the same info over in the help form.

#10

FYI, the support form only allows a message with 255 characters. So wasn’t practical to provide much info, so I’m just sticking with this forum post for now.

#11

I’ve found the offending code. I’ll work with the plugin portal owners to set this bug straight.

Sorry for the trouble, Andrew.

1 Like
#12

Thanks again for helping get this over to the right people. Any update on a fix?

#13

@sterling is working on a fix. It’s slow progress due to the Gradle world meeting in Spain.

Will give you an update again soon.

Cheers,
Eric

1 Like
#14

@eriwen or @sterling Any update on resolving this publishing issue? I’ve been held up from making fixes to my plugin for the last month now.

#15

FYI, I gave up waiting for this fix. Don’t want to keep delaying getting my plugin out there, so I’ve renamed the plugin from gradle-clojure to clojurephant. New plugin IDs are pending approval, but those usually get a timely response.

#16

I’d love to see the day where Gradle stop trying to host binaries. The team’s resources are obviously better spent doing all things Gradle rather than building a fully fledged binary repository which in my opinion would be better served by using an existing, off the shelf solution

#17

Agreed, especially considering how limited (and unchanging) the portal is. There’s no visibility into things (like usage by version of the plug-in) I get for free if it was still hosted on Bintray.

#18

Sorry, I was trying to get this done for you this week.

A new version of the plugin portal was deployed earlier today:
https://plugins.gradle.org/

If you’d like, you can resubmit with the original names you wanted and I’ll cancel the new ones, or you can continue with what you’ve switched to since you’ve already gone through the trouble.

1 Like
#19

@sterling I appreciate having the fix in place now, should help others if they had a similar naming scheme. I’ll stick with the new names, since I’ve already changed all the code/GitHub/Bintray names.

#20

I’ve been waiting for a latest version badge for over two years. Again this would be available if plugins were hosted on bintray

1 Like