This message was deleted.
# general
s
This message was deleted.
😢 2
r
Yeah some of my team’s builds are failing now on account of being uanble to download plugins
g
Same here ,( And Gradle sometimes inserts
gradlePluginPortal()
before private Nexus instance, so no luck with private mirror/cache
l
status.gradle.com is updated - looks like an Heroku outage.
v
And Gradle sometimes insertsĀ 
gradlePluginPortal()
Ā before private Nexus instance, so no luck with private mirror/cache
Would be interesting to know when it does that and then reported as error. I've never seen that happen and if that is true, it is a bug. It's not uncommon in bigger companies to be restricted to use only internal repository. So when you define an internal repository, Gradle should not add the portal back in itself.
āž• 1
v
But where does it add the plugin portal when you have own repos defined? Or is the application of a settings plugin already too late and the plugin portal is already added by then?
g
I'm not sure when since I apply plugin via settings' plugins block. I'll try to reproduce it on 7.4 but iirc it wasn't deterministic at the first sight
@Vampire, it's another chicken&egg problem since gradle has to add plugin portal to resolve my settings plugin first and then I add my repos there. So current behavior is not a bug. Earlier I added private repos in init script using
beforeSettings
and I think 7.4 wouldn't add plugin portal since
pluginManagement#repositories
will be populated by the time it tries to resolve settings plugins.
šŸ‘Œ 1