Open bmuschko opened 5 years ago
@bmuschko I've hesitated fixing things as we've moved away from this plugin internally and on to using helm
instead. The problem is that kubernetes, especially for bigger workloads, can be very complicated to program and wire up even with this plugin vs when you use helm things are more/less push-button. I'm not sure how much traffic this plugin is getting, or use for that matter, but I'm not sure if it's a viable solution for kubernetes going forward.
Totally understand. I just checked JCenter and people still seem to use it so I guess we have to keep it around at least.
Really? That's great. No one has ever opened an ISSUE/PR so I assumed we were the only ones :) Kubernetes is very complicated and I tried my best here to make resuable parts, and succeeded to a degree, but it only gets you past the most simple of use-cases and understanding how to get more out of this (which is possible) takes a seasoned developer IMO. Wish folks would chime in that they are using it though ;) That gives me a little more motivation to fix the broken CI build.
I am kind of surprised that there isn't a stronger engagement from users. Maybe the plugin was applied to some builds and then forgotten. It might not be really used. It's too bad you can't get more specific stats e.g. by country/region/city.
The build on Travis CI is currently failing. We'll need to get that fixed.