[JIRA] [core] (JENKINS-33007) Rename "node" to "agent" throughout Jenkins
Title: Message Title Oleg Nenashev commented on JENKINS-33007 Re: Rename "node" to "agent" throughout Jenkins I agree with Christopher Orr that the new "nice" taxonomy is a total mess if we take the huge amount of legacy info about Jenkins where nodes are... a kind of builders (including remote nodes). I would vote for Agent with "On-master agent" and "Remote agent" types. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33007) Rename "node" to "agent" throughout Jenkins
Title: Message Title Daniel Beck edited a comment on JENKINS-33007 Re: Rename "node" to "agent" throughout Jenkins [~jglick] We renamed '_slave_' to 'agent', but some, including [~orrc] appear to want to get rid of this nice taxonomy (master is a node, but not an agent) to include make 'agent' a second, redundant term for 'node', and remove the one for its meaning of "a node that is not master" (superseding 'slave') that we currently have. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33007) Rename "node" to "agent" throughout Jenkins
Title: Message Title Daniel Beck commented on JENKINS-33007 Re: Rename "node" to "agent" throughout Jenkins Jesse Glick We renamed 'slave' to 'agent', but some, including Christopher Orr appear to want to get rid of this nice taxonomy (master is a node, but not an agent) to include a second, redundant term for 'node', and remove the one for "a node that is not master" we currently have. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33007) Rename "node" to "agent" throughout Jenkins
Title: Message Title Jesse Glick commented on JENKINS-33007 Re: Rename "node" to "agent" throughout Jenkins I thought this was done already? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33007) Rename "node" to "agent" throughout Jenkins
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-33007 Rename "node" to "agent" throughout Jenkins Change By: Daniel Beck Labels: 2.0 2.0-planned Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33007) Rename "node" to "agent" throughout Jenkins
Title: Message Title Kohsuke Kawaguchi updated an issue Jenkins / JENKINS-33007 Rename "node" to "agent" throughout Jenkins Change By: Kohsuke Kawaguchi Labels: 2.0 2.0-planned Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33007) Rename "node" to "agent" throughout Jenkins
Title: Message Title Daniel Beck commented on JENKINS-33007 Re: Rename "node" to "agent" throughout Jenkins Related IRC discussion: [2016-02-29T22:13:38+0100] orrc: I thought that was going to happen in 2.0 anyways? [2016-02-29T22:13:52+0100] slave -> agent is done [2016-02-29T22:14:00+0100] right [2016-02-29T22:14:04+0100] so now we have "agent" and "node" [2016-02-29T22:14:42+0100] ah right, you and I already talked about this I see [2016-02-29T22:14:47+0100] • rtyler: cheers [2016-02-29T22:15:16+0100] yeah. so because of technical reasons, users get to see a mixture of terms, as I understand it [2016-02-29T22:34:10+0100] orrc: nodes = any machine in a Jenkins cluster, agent aka slave [2016-02-29T22:34:23+0100] orrc: was the discussion on the gov meeting for the rename [2016-02-29T22:34:31+0100] and why node wasn't selected [2016-02-29T22:34:39+0100] batmat: you misunderstand :) [2016-02-29T22:34:58+0100] batmat: I'd like to kill the word "node" entirely from Jenkins — node is already used [2016-02-29T22:36:11+0100] orrc: well, why not merge into one word, I'm not sure, but not sure agent is better to keep than node :) [2016-02-29T22:37:20+0100] batmat: did you see orrc's comment on the ticket above from last time we discussed this? [2016-02-29T22:38:30+0100] batmat: https://i.imgur.com/KCgg1in.png [2016-02-29T22:38:43+0100] "Slave foo" / "Mark this node offline" [2016-02-29T22:39:00+0100] also nice: "This *node* is offline because the *slave* agent failed to launch" [2016-02-29T22:39:10+0100] • orrc: wonders how "slave agent" got translated in "slave" -> "agent" [2016-02-29T22:40:11+0100] orrc: yeah right. IMO we should indeed review that screen in the 2.0 alpha (or the branch itself, and `git grep`ing that string) [2016-02-29T22:41:01+0100] batmat: I'd rather "node" wasn't used anyway — we've chosen "agent" to mean a machine where builds are happening, so it would be nice to use that *everywhere* [2016-02-29T22:41:08+0100] s/anyway/anywhere [2016-02-29T22:46:29+0100] with Jenkins 2.0: https://i.imgur.com/rkVktB8.png … [2016-02-29T22:51:23+0100] <@danielbeck> orrc node includes master, agent does not. That was my understanding. Otherwise we need more terminology … [2016-02-29T22:54:18+0100] danielbeck: yeah, that's clear. technically everything is a node, but there's no reason to expose this terminology to users. if master has executors (as it does by default) that's an agent that can run builds for me. if I attach another agent, that's another agent that can run builds for me [2016-02-29T22:54:47+0100] <@danielbeck> IOW it's just redundant and you now have "agents other than master" [2016-02-29T22:55:53+0100] <@danielbeck> rtyler I don't think it's possible [2016-02-29T22:57:00+0100] <@danielbeck> orrc AFAIK the intention was to have a drop in replacement for 'slave', so having 'agent' mean the same as 'node' would change its meaning and lead to the problem that you have no term for what used to be called slave. … [2016-02-29T23:01:58+0100] danielbeck: what type of problems are you thinking of that would be caused by "node" being called "agent"? [2016-02-29T23:02:42+0100] <@danielbeck> You mean besides confusion and redundancy, and the fact that we don't have a new term for what used to be called Slave? [2016-02-29T23:04:14+0100] <@danielbeck> Master is a node. A slave is a node. Master is not a slave. So we need to be very clear about which term we're replacing with another one, and that term is 'slave'. [2016-02-29T23:04:55+0100] <@danielbeck> Otherwise you'll just have 'agent' mean 'node', and people will continue using 'slave' because there's no alternative, and we won't have accomplished anything. [2016-02-29T23:05:04+0100] Yeah, that makes
[JIRA] [core] (JENKINS-33007) Rename "node" to "agent" throughout Jenkins
Title: Message Title Christopher Orr commented on JENKINS-33007 Re: Rename "node" to "agent" throughout Jenkins Tyler reminded me that the Jenkins master is available for build execution, which is perhaps why we have the mixture of references to nodes and slaves. But it wouldn't be so bad to call everything "agent" anyway? Master already has an arguably confusing dual purpose: managing configuration and everything, and also being a build executor (in an out-of-the-box Jenkins install). So we could say that the master has an agent embedded within it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33007) Rename "node" to "agent" throughout Jenkins
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-33007 Rename "node" to "agent" throughout Jenkins Issue Type: Improvement Assignee: Unassigned Components: core Created: 18/Feb/16 1:04 AM Labels: 2.0 Priority: Minor Reporter: Christopher Orr There is an inconsistent mixture of "slave" and "node" throughout the Jenkins core UI. For example, viewing the details of a slave shows the title "Slave foo", the breadcrumb "Jenkins > Nodes > foo", and the URL /computer/foo. As per JENKINS-27268, all instances of "slave" were renamed to "agent", and the changes were merged into the Jenkins 2.0 branch. Ideally we should take this chance to stop using the word "node" — I think it has much less meaning for regular users, and in general, compared to "agent". i.e. everywhere where "Node" is at the moment should become "Agent".
