It would be better to handle implementation details should in separate threads. Technical complexity is implied here. Actual cleanup will of deprecated terminology is likely to take years, and we will have plenty of time to deep dive on it. Let's focus on terminology.
I like Daniel's suggestion about using separate terms depending on the case, e.g. Jenkins Web UI, Jenkins agent controller, etc. We already have examples of multi-tenant and multi-setver Jenkins instances, as well as other architectures like Jenkinsfile Runner which is arguably "serverless". Breaking down a single term would be a good investment in future. -- 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/625ecc00-1994-4259-8191-274dbe205f21o%40googlegroups.com.
