Again, you're welcome to try and push forward that initiative if you think
it's important.
2016-08-27 20:10 GMT+02:00 Kiran :
> The CM tools have terms for servers that receive changes. I don't see why
> a CI tool would not have one. Apparently the Jenkins community is mature
> and has gotten t
The CM tools have terms for servers that receive changes. I don't see why
a CI tool would not have one. Apparently the Jenkins community is mature
and has gotten this far with no term. To me, a term would really make
things easier.
On Thursday, August 18, 2016 at 6:52:23 PM UTC-4, Kiran wrot
> On 24.08.2016, at 10:11, Stephen Connolly
> wrote:
>
> The "permanent" bit was added to indicate that this is an agent that will
> stick around
Even more nit: 'permanent' replaced 'dumb'.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
On Friday 19 August 2016, Baptiste Mathus wrote:
> Hi,
>
> Fwiw, slave in Jenkins 1.x and "permanent agent" in Jenkins 2.x is indeed
> the same thing.
>
>
> Nit:
Agent and slave are the same thing. The "permanent" bit was added to
indicate that this is an agent that will stick around as distinct
Well, I guess not. You're probably the first one to ask about this.
The question you're asking seems to me to be quite too generic to have a
dedicated term.
As for defining term in general in OSS and in this project, "asking"
Kohsuke is not how it works. Or I mean, you can do it here in public (no
When an organization adopts Jenkins, I think there is a need for a term
that receives an artifact from Jenkins. Given that it is open source, how
does one create a new word? Should I try to ask Kohsuke Kawaguchi to
create a term? When other people talk about Jenkins with non-technical (or
se
Hi,
Fwiw, slave in Jenkins 1.x and "permanent agent" in Jenkins 2.x is indeed
the same thing.
This vocabulary change is the result of
https://issues.jenkins-ci.org/browse/JENKINS-27268 to remove the term
'slave' from Jenkins.
As for your question, I guess there's no general answer. IMO you have t
A Jenkins slave (or agent in 2.x) is a service running on "an auxiliary
server" as you describe it, which can be assigned jobs to execute by the
Jenkins master. There is no Jenkins-specific term for a server that
receives artifacts from Jenkins jobs. You would call it whatever you'd
call it if
In the context of Jenkins, is a slave server one that receives a build? Or
is it an auxiliary server that offloads some of the computing demand for
resources of a distributed build?
With Jenkins 2.x, the term is "permanent agent." I want to know precisely
what to call a server that receives a
