deeply misleading for everyone, and mainly
> newcomers that there is an empty maven module in the source tree.
>
>
>
> Le dim. 6 janv. 2019 à 18:32, Oleg Nenashev > a écrit :
>
>> Hi,
>>
>> I am not against removing CLI over Remoting. Or maybe it makes sense to
he meantime, it would be deeply misleading for everyone, and mainly
newcomers that there is an empty maven module in the source tree.
Le dim. 6 janv. 2019 à 18:32, Oleg Nenashev a
écrit :
> Hi,
>
> I am not against removing CLI over Remoting. Or maybe it makes sense to
> move it to
Since the response was mostly positive, I filed
https://github.com/jenkinsci/jenkins/pull/3838
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-d
It’s not exactly a third opinion because I agree with Jesse. Jenkins build and
test structures are already complicated enough. I would hope to not increase
that complexity with a clear, demonstrated need.
Jeff Thompson
> On Jan 7, 2019, at 7:20 AM, Jesse Glick wrote:
>
> On Sun, Jan 6, 2019 a
On Sun, Jan 6, 2019 at 12:32 PM Oleg Nenashev wrote:
> maybe it makes sense to move [Remoting-based CLI] to a plugin
Not possible I am afraid. It either needs to be baked into core and
supported, or deleted.
> It is just a matter of time till we hit another Java-specific test class
There is no
Hi,
I am not against removing CLI over Remoting. Or maybe it makes sense to
move it to a plugin (without adding it as a detached plugin). But I do not
quite get the need to simplify the component structure. It is just a matter
of time till we hit another Java-specific test classes & Co.
+1 from me as well.
On Fri, Jan 4, 2019 at 3:21 PM Jeff Thompson
wrote:
> +1
>
> I support this proposal. We’ve seen another case recently of a problem
> with this antiquated mode. We have had to adjust tests to continue
> supporting it.
>
> I don’t think there is enough value in continuing to s
+1
I support this proposal. We’ve seen another case recently of a problem with
this antiquated mode. We have had to adjust tests to continue supporting it.
I don’t think there is enough value in continuing to support it, particularly
with the costs to keep coaxing it along.
Jeff Thompson
> On
As of JENKINS-41745, merged in Jenkins 2.54 more than a year and a
half ago, the Remoting transport for the Jenkins CLI has been
deprecated as inherently hard to secure and just plain unwise. As far
as I know, all important CLI commands have long since removed any
dependency on this mode, or offere
