Hello, On Tue, Oct 01, 2019 at 09:24:13 +0800, M S wrote: > Then in the scenario where someone wants to have some "global default" > settings for a specific task plugin, what would be the recommended > approach? > > Right now it feels like the only way to achieve this is by including > something like a properties file that is packaged together with the plugin. > The downside to this is that anytime you update the configuration in that > type of resource, I would also need to restart GoCD server as well.
Task plugins were the first kind of plugins in GoCD's plugin infrastructure. They used to have plugin settings a long time ago, if I recall correctly. That ability was then removed. Even normal tasks are fully self-contained. Adding plugin settings seemed to add confusion to it. I agree that this ended up making them inconsistent, compared to the other plugins. You're right that the way to approach is to have a properties file. It need not be packaged with the plugin, though. It just needs to expect it in a certain location on the filesystem. > I also noticed that Task Plugins are not allowed to have icons that can > appear in the plugins manager page. That makes me a little sad. :( Oh, that makes me a little sad as well. :( I think our thinking around task plugins evolved to the extent that we subconsciously started ignoring it. Task plugins are a bit of an anti-pattern, in that it isn't what is recommended practice in CD -- in that the plugin ties you to the CD system, rather than allowing you to deploy / build independent of it. Ideally, it's part of a script which is version controlled and called from the CD system. At least that's what I think. Cheers, Aravind -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/20191001223356.r5rveuic276kuo7w%40arvindsv.com.
