I haven't seen any other responses here than this one from Slide so I'm going to assume lack of response means there are no objections. I also haven't received any concerns about use case or configuration, so I'm not planning on tying this work as a dependency with Jesse's work with WebSockets. Both efforts can proceed independently.

I'm still working on a timeline for when these changes will go in. Currently I'm leaning towards waiting a little before making this change.

Jeff

On 12/3/19 11:58 AM, Slide wrote:
I'm a bigĀ +1 on this.

On Tue, Dec 3, 2019 at 11:05 AM Jeff Thompson <jthomp...@cloudbees.com <mailto:jthomp...@cloudbees.com>> wrote:

    For historical reasons, Jenkins still ships with old, deprecated
    protocols, JNLP1-connect, JNLP2-connect, and JNLP3-connect. These all
    have fundamental issues and known bugs. They were all superseded
    by the
    JNLP4-connect protocol released in Jenkins 2.27 over three years ago
    (October 2016). They have all been deprecated and unsupported since
    Jenkins 2.75 over two years ago. Since then there have been UI
    messages
    and an administrative monitor strongly discouraging their use.
    (See more
    information about the protocols at
    https://github.com/jenkinsci/remoting/blob/master/docs/protocols.md )

    As part of cleaning up technical debt I propose to remove these
    protocols. Does anyone have any concerns? If you do, please share use
    case or configuration details.

    There is a proposal to add WebSockets as another agent connection
    mechanism. (See
    
https://github.com/jenkinsci/jep/blob/2c137aa7884fd6360f133964422fd997351a7ebb/jep/0000/README.adoc

    ) This may cover use cases where someone still uses the older
    protocols.
    We could make the removal of the old protocols dependent on
    completion
    of WebSocket support.

    Jeff Thompson


-- You received this message because you are subscribed to the Google
    Groups "Jenkins Users" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to jenkinsci-users+unsubscr...@googlegroups.com
    <mailto:jenkinsci-users%2bunsubscr...@googlegroups.com>.
    To view this discussion on the web visit
    
https://groups.google.com/d/msgid/jenkinsci-users/0d38edaf-2cc2-d390-2332-aaa3105d9972%40cloudbees.com.



--
Website: http://earl-of-code.com
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com <mailto:jenkinsci-users+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVeptB-Vo5fnft6d08ar-X20BHxGByN5AoCnz%2BO%2B-tcr4A%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVeptB-Vo5fnft6d08ar-X20BHxGByN5AoCnz%2BO%2B-tcr4A%40mail.gmail.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/00e706c8-923b-bf13-cf57-732dba27ad91%40cloudbees.com.

Reply via email to