I’ve created two canned responses and allowed anyone to use them. It’s a site-wide toggle but I don’t see any reason why only specific users can use them.
Feel free to suggest updates or suggest other new ones. Heck, feel free to try them out on this post.
As a reminder, the term “slave” to refer to an agent has been deprecated since 2016. Please refer to
On Jenkins Terminology Updates for more details. We request you update your post.
“it doesn’t work” is always hard to remote debug. Try to always include these 3 things.
what did you try? (Code samples, command lines, screenshots, videos, etc)
what did happen? (Error messages, description, outputs, stuff)
what did you expect to happen?
Otherwise, it’s hard for us to get into your context and you’ll have to have someone who is exactly knowledgeable come along.
wrt: “Slave Usage”, while “slave” seems to the the most prominently used inappropriate term, would it be appropriate to genericise/expand the canned response to include the use of terms “master” (controller and branch context), “whitelist” and “blacklist”, etc.?
Jenkins Terminology Changes and Cloudbees Continuous Improvement To Maintain A Culture of Continuous Respect
I’ll admit, because its less of a drastic change, and the big admin notice for master => builtin, its been an issue less, or I noticed it less, So I hadn’t thought about it.
I’ll gladly add one if you want to draft one up (even if its just copy and paste mine) and that’ll probably help me remember to do it.