Hi, I maintain a plugin (dotnet-sdk) that mostly provides a global tool and associated wrapper. But it also has a bunch (currently 11) convenience steps that can be used (instead of the wrapper plus bat/pwsh/...). I got a ticket saying that this caused a bit of a clutter for freestyle jobs, because the list popped up by "Add build step" gets pretty long, which was fair enough. It turned out to be very easy (using isApplicable()) to have each of the steps optionally "hide" itself based on a flag in a GlobalConfiguration.
However, that only prevents it from being added to a freestyle job (using the UI anyway); it does not seem to affect steps that are already in use. So I was wondering if it was considered frowned upon to scan through all freestyle jobs to see if a particular step is in active use somewhere, and if not, what the typical performance implications are. I was thinking of adding such a check in a doCheck for each of the checkboxes in the GlobalConfiguration, so that if you uncheck the Foo step, it can validate it with a warning "this step is currently in use by N project(s)". I'm just not sure whether that's considered a no-no, and if not, how such a check would scale to a large instance with hundreds (or thousands, if that's likely?) of projects. Any advice would be helpful. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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/jenkinsci-dev/CAKMi--C6harOuZCHiFw-C-AZJ35NAyz2dHPqtZeuiBCrof%2BF9g%40mail.gmail.com.
