[JIRA] [core] (JENKINS-35451) Change name of "slave.jar" to "agent.jar"

2016-06-09 Thread bitwise...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liam Newman edited a comment on  JENKINS-35451 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change name of "slave.jar" to "agent.jar"  
 
 
 
 
 
 
 
 
 
 Is eternal backward compatibility a core requirement?  Can we create a plan for phasing these out?  Provide both for some time period and then remove the old.  File names in particular heavily influence the terms people use when talking about the product and features. Keeping "slave" in the file names essentially defeats any effort to remove the term "slave" from association with our product.  As part of this transition, we're seeing people add the term "agent" but not remove the term "slave" from descriptions.   "I'm have a problem with my jenkins slave agent."   To get people to drop "slave", I think we need to  not  show them "slave-blah" every time they start an agent. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35451) Change name of "slave.jar" to "agent.jar"

2016-06-09 Thread bitwise...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liam Newman commented on  JENKINS-35451 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change name of "slave.jar" to "agent.jar"  
 
 
 
 
 
 
 
 
 
 
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 filenames and urls are effectively part of the API and so changing them is problematic and could be considered out of scope. But filenames and urls are also part of the end-user experience (the UI) for every Jenkins user. And the files and urls related to adding an agent are some of the first and most commonly used.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35451) Change name of "slave.jar" to "agent.jar"

2016-06-09 Thread bitwise...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liam Newman updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35451 
 
 
 
  Change name of "slave.jar" to "agent.jar"  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liam Newman 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35451) Change name of "slave.jar" to "agent.jar"

2016-06-09 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-35451 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change name of "slave.jar" to "agent.jar"  
 
 
 
 
 
 
 
 
 
 
> Can we create a plan for phasing these out? Provide both for some time period and then remove the old.  
We cannot, because there is no API deprecation policy/engine. As a remoting maintainer, I'm strongly -1 on removing original links within any visible timeframe. Too much fixing efforts and regressions due to just a renaming 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35451) Change name of "slave.jar" to "agent.jar"

2016-06-09 Thread bitwise...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liam Newman commented on  JENKINS-35451 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change name of "slave.jar" to "agent.jar"  
 
 
 
 
 
 
 
 
 
 
Is eternal backward compatibility a core requirement? Can we create a plan for phasing these out? Provide both for some time period and then remove the old.  
File names in particular heavily influence the terms people use when talking about the product and features. Keeping "slave" in the file names essentially defeats any effort to remove the term "slave" from association with our product. As part of this transition, we're seeing people add the term "agent" but not remove the term "slave" from descriptions. "I'm have a problem with my jenkins slave agent." To get people to drop "slave", I think we need to show them "slave-blah" every time they start an agent. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35451) Change name of "slave.jar" to "agent.jar"

2016-06-09 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-35451 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Change name of "slave.jar" to "agent.jar"  
 
 
 
 
 
 
 
 
 
 
It's not so easy, because many automation flows download slave.jar, windows-slave.exe and other such files from Jenkins. We can only add new endpoints and fix UIs, but the previous entries must be retained 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-35451) Change name of "slave.jar" to "agent.jar"

2016-06-07 Thread bitwise...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liam Newman created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35451 
 
 
 
  Change name of "slave.jar" to "agent.jar"  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 2016/Jun/07 11:58 PM 
 
 
 

Environment:
 

 Jenkins 2.6 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Liam Newman 
 
 
 
 
 
 
 
 
 
 
Found when launching a jnlp agent from command line: "java -jar slave.jar -jnlpUrl ..."  
The name of this jar should match agreed naming guidelines. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment