I don't really ever weigh in on things but this time I'd like to.
I think its safe to say no one wants anything with a space or special
chars, due to obvious technical issues.
In that vein, 'Jenkins Server' could have such technical implications plus
it is very broad.
So we're left with one
Why not extend the butler analogy? Majordomo. Or MD for short?
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
I prefer server. It’s generic but short.
Allowlist is ok. I have no preference between denylist and blocklist.
Depending of the context where it is used it could perhaps be
includes/excludes.
Arnaud
Le ven. 12 juin 2020 à 05:34, Slide a écrit :
> Hi Everyone,
>
>
>
> Back in the Jenkins 2.0
> On 12. Jun 2020, at 20:05, Slide wrote:
>
> Jenkins Server makes sense to me as well. I'll add as a topic for the next
> Governance meeting.
It seems as if this thread so far lacks considerations regarding the
implementation of such a decision. This is concerning because a superficially
HiJeff,
I agree that Contributor Covenant 2.0 is generally better, especially for a
large community like Jenkins. This version basically includes statements of the
Community Covenant which covers wider areas. I am fine with exploring this
option more.
I have contacted the Contributor Covenant
Hi all,
I'd like to adopt the Tool Environment plugin and request commit access.
I'm trying to deliver JENKINS-48791 and in my PR Jesse suggested I adopt
it. It might be a good way for me to get into contributing with this small
plugin.
* Link to a plugin you want to adopt:
you correctly Pou ted out my examples where rubbish.
but you can not talk about the Jenkins server and know what the other is
talking about without saying, you mean Linux or the java process thing it's a
recepie for disaster or turning 2 words into 6 every time you want to use it.
today sure
Jenkins server is ambiguous it has as many minus votes as I can put (limited to
one)
login to the Jenkins server and run service start Jenkins.
login to the Jenkins server and create a new job
whatever we choose it can not be confused with the host/is/server/machine that
the is process
On Sat, Jun 13, 2020 at 1:19 PM James Nord wrote:
> Jenkins server is ambiguous it has as many minus votes as I can put
> (limited to one)
>
> login to the Jenkins server and run service start Jenkins.
>
>
Wouldn't that be better phrased as "login to Linux and run `systemctl start
jenkins`"
On Sat, Jun 13, 2020 at 3:04 PM James Nord wrote:
>
> but you can not talk about the Jenkins server and know what the other is
> talking about without saying, you mean Linux or the java process thing it's
> a recepie for disaster or turning 2 words into 6 every time you want to use
> it.
>
>
Here's my attempt at more precise details.
On Sat, Jun 13, 2020 at 3:02 AM Daniel Beck wrote:
>
>
> > On 12. Jun 2020, at 20:05, Slide wrote:
> >
> > Jenkins Server makes sense to me as well. I'll add as a topic for the
> next Governance meeting.
>
> It seems as if this thread so far lacks
11 matches
Mail list logo
