[JIRA] [core] (JENKINS-35450) Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT
Title: Message Title Liam Newman commented on JENKINS-35450 Re: Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT The originally agreement was that the term slave would be removed from the UI, but left in the APIs to avoid breaking compatibility both for plugins and customer tools/scripts. The problem is that line of where the UI stops and the API begins is a somewhat fluid when your users are engineers. I understand that env vars are effectively part of the API and so changing them is problematic and could be considered out of scope. But they are also part of the end-user experience (the UI) for every Jenkins user. 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-35450) Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT
Title: Message Title Liam Newman commented on JENKINS-35450 Re: Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT Oleg Nenashev How about providing both vars for a while with at task for removing the "slave" one in six months? Is eternal backward compat required? 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-35450) Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT
Title: Message Title Oleg Nenashev commented on JENKINS-35450 Re: Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT This change will be incompatible. -1, needs a better design 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-35450) Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-35450 Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/07 11:52 PM Priority: Minor Reporter: Liam Newman Found while using Jenkins 2.6 docker container, so it needs to be fixed both there and in core. Add Comment This message was sent
