I like Jenkins Server too

> On Jun 12, 2020, at 10:41 AM, Matt Sicker <[email protected]> wrote:
> 
> I also like Jenkins Server as a simple name.
> 
> Other ideas: JenkinsD (like SystemD or any daemon), Jenkins Principal
> (matches the principal/agent paradigm of agents executing code on
> behalf of the principal).
> 
> On Fri, Jun 12, 2020 at 12:37 PM Vlad Silverman <[email protected]> wrote:
>> 
>> I agree, “Jenkins Server” reflects primary functionality and definitely 
>> makes sense.
>> 
>> Thx, Vlad
>> 
>> On Jun 12, 2020, at 10:21 AM, Mark Waite <[email protected]> wrote:
>> 
>> My favorite is Jenkins server.  I'll use whatever term is ultimately 
>> selected, but "Jenkins server" is easier for me than "Control Plane".
>> 
>> On Fri, Jun 12, 2020 at 10:13 AM Jeff Thompson <[email protected]> 
>> wrote:
>>> 
>>> My favorite is "Jenkins server" or something like that. There are already 
>>> existing usages and it's reasonably explanatory. Something with "manager" 
>>> could also work, but I don't find the term as clean and clear.
>>> 
>>> Outside of bias issues, one of the problems with whitelist and blacklist is 
>>> that the terms don't really say what they do. Sometimes the interpretation 
>>> depends on which way you're looking at it. Somewhat similar to whether a 
>>> class hierarchy goes up or down.
>>> 
>>> "AllowList" and "DenyList" are good matching pairs that convey more 
>>> semantics about what they do.
>>> 
>>> In other discussions we have noted that not all usages of 
>>> whitelist/blacklist fall into the same behavioral meaning. Sometimes we 
>>> will need to use different terminology to better convey the meaning.
>>> 
>>> Jeff
>>> 
>>> On 6/12/20 3:20 AM, Oleg Nenashev wrote:
>>> 
>>> I am +1 for changing the terminology, and I encourage Jenkins contributors 
>>> to participate in this effort. It is not something we could change in a 
>>> minute, but we could do a gradual cleanup and improve the overall 
>>> documentation while doing so.
>>> 
>>> I am -1 w.r.t "host" due to the following reasons:
>>> 
>>> Host term is very generic, it has thousands of usages in Jenkins 
>>> https://github.com/search?q=org%3Ajenkinsci+host&type=Code. Choosing this 
>>> term will require a careful cleanup to avoid confusion in user 
>>> documentation and the codebase
>>> "agent host" is often used to describe target hosts for outbound agents
>>> 
>>> My suggestion would be to consider a "Jenkins server" term. You can see 
>>> that such a term is already used in our codebase, website and on 3rd party 
>>> resources.
>>> 
>>> Best regards,
>>> Oleg
>>> 
>>> On Friday, June 12, 2020 at 6:42:34 AM UTC+2, Marky Jackson wrote:
>>>> 
>>>> It is a suggestion for consideration if you would like.
>>>> 
>>>> On Jun 11, 2020, at 9:35 PM, Richard Bywater <[email protected]> wrote:
>>>> 
>>>> 
>>>> Good point. I actually wonder if Manager is a reasonable replacement?
>>>> 
>>>> On Fri, 12 Jun 2020 at 16:04, Marky Jackson <[email protected]> wrote:
>>>>> 
>>>>> The concern with controller may be a conflict with Kubernetes on Jenkins 
>>>>> given the same name. This was originally my suggestion but than I 
>>>>> remembered I was also part of renaming in that community.
>>>>> 
>>>>>> On Jun 11, 2020, at 9:02 PM, Richard Bywater <[email protected]> wrote:
>>>>>> 
>>>> 
>>>> --
>>>> 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/CAAy0hwcrbnGua2b3sHamE2AG1r3z8cXBxA02%2B4NrQHMWqQjzyg%40mail.gmail.com.
>>> 
>>> --
>>> 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/4ffdf650-4bb4-4878-a629-4e49c3ac06b5o%40googlegroups.com.
>>> 
>>> 
>>> --
>>> 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/e024d4a9-09e1-ff95-3bbc-a35d486e21ed%40cloudbees.com.
>> 
>> 
>> --
>> 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/CAO49JtH%3DNGuf%2BEOoh9gXyOY53vx761aV-w4V07hA7SxwZ%2B_Q1A%40mail.gmail.com.
>> 
>> 
>> --
>> 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/7EF2760C-0B57-42AA-A600-B55E557956D3%40gmail.com.
> 
> 
> 
> --
> Matt Sicker
> Senior Software Engineer, CloudBees
> 
> --
> 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/CAEot4oxiMsarDuQp8KcgUcv08TVtHFBpsz2m4qRECdBo%2BvhzGw%40mail.gmail.com.

-- 
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/F2B3AC63-DD98-48A4-A5F2-064D9336C1BD%40gmail.com.

Attachment: signature.asc
Description: Message signed with OpenPGP

Reply via email to