[JIRA] (JENKINS-50211) Add an option to optionally reject connections from agents with unsupported Remoting versions

5 views
Skip to first unread message

o.v.nenashev@gmail.com (JIRA)

unread,
Mar 16, 2018, 4:50:02 AM3/16/18
to jenkinsc...@googlegroups.com
Oleg Nenashev created an issue
 
Jenkins / Bug JENKINS-50211
Add an option to optionally reject connections from agents with unsupported Remoting versions
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 2018-03-16 08:49
Labels: remoting
Priority: Minor Minor
Reporter: Oleg Nenashev

It is a follow-up to JENKINS-48766. That story adds warnings for unsupported agent versions, but it actually does not reject them. It would be useful to have such feature in the core or in Version Column Plugin. Core is preferable though this feature may be detached to a plugin later as a part of JENKINS-44100.

Acceptance criteria:

  • There is a Global Configuration entry for Remoting. An existing section for Remoting protocols may be used
  • There is a checkbox in the configuration, which turns on rejection of unsupported versions
  • SlaveComputer#setChannel() checks the option status. Depending on it, it may either accept or reject the connection
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

o.v.nenashev@gmail.com (JIRA)

unread,
Mar 16, 2018, 4:56:02 AM3/16/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
It is a follow-up to JENKINS-48766. That story adds warnings for unsupported agent versions, but it actually does not reject them. It would be useful to have such feature in the core or in Version Column Plugin. Core is preferable though this feature may be detached to a plugin later as a part of JENKINS-44100.

Acceptance criteria:

* There is a Global Configuration entry for Remoting. An existing section for Remoting protocols may be used
* There is a checkbox in the configuration, which turns on rejection of unsupported versions
* SlaveComputer#setChannel() checks the option status. Depending on it, it may either accept or reject the connection
* Nice2have: Automatic test which confirms that the flag survives restarts
* Nice2have: Automatic test which picks unsupported version of Remoting and confirms that it cannot connect

o.v.nenashev@gmail.com (JIRA)

unread,
Mar 16, 2018, 4:57:01 AM3/16/18
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Mar 16, 2018, 4:57:02 AM3/16/18
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Mar 16, 2018, 4:58:02 AM3/16/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
It is a follow-up to JENKINS-48766. That story adds warnings for unsupported agent versions, but it actually does not reject them. It would be useful to have such feature in the core or in Version Column Plugin. Core is preferable though this feature may be detached to a plugin later as a part of JENKINS-44100.

Acceptance criteria:

* There is a Global Configuration entry for Remoting. An existing section for Remoting protocols may be used
* There is a checkbox in the configuration, which turns on rejection of unsupported versions
* SlaveComputer#setChannel() checks the option status. Depending on it, it may either accept or reject the connection
* Nice2have: Automatic test which confirms that the flag survives restarts
* Nice2have: Automatic test which picks unsupported version of Remoting and confirms that it cannot connect . See examples in https://github.com/jenkinsci/jenkins/blob/master/test/src/test/java/jenkins/slaves/OldRemotingAgentTest.java

gautam.abhishek46@gmail.com (JIRA)

unread,
Mar 17, 2018, 5:26:02 PM3/17/18
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jan 28, 2019, 2:24:01 AM1/28/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Labels: newbie-friendly remoting
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

o.v.nenashev@gmail.com (JIRA)

unread,
Jan 28, 2019, 2:25:03 AM1/28/19
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jan 28, 2019, 2:25:03 AM1/28/19
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Jan 28, 2019, 2:26:02 AM1/28/19
to jenkinsc...@googlegroups.com

sumitsarinofficial+jenkins@gmail.com (JIRA)

unread,
Mar 12, 2020, 5:03:03 PM3/12/20
to jenkinsc...@googlegroups.com
Sumit Sarin assigned an issue to Sumit Sarin
Change By: Sumit Sarin
Assignee: Sumit Sarin
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

sumitsarinofficial+jenkins@gmail.com (JIRA)

unread,
Mar 25, 2020, 4:44:02 AM3/25/20
to jenkinsc...@googlegroups.com
Sumit Sarin started work on New Feature JENKINS-50211
 
Change By: Sumit Sarin
Status: Open In Progress

sumitsarinofficial+jenkins@gmail.com (JIRA)

unread,
Apr 4, 2020, 1:46:02 PM4/4/20
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages