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
Hi all,
According to the feedback here and in the chats, I believe it makes sense
to proceed with creating the SIGs. While we wait for the additional
feedback, I have created the Gitter channels so that we can discuss next
steps there:
- https://gitter.im/jenkinsci/embedded-sig
-
Probably you could find an answer in this discussion:
https://groups.google.com/d/msg/jenkinsci-dev/zNukeuLK4Og/SvX-b5exCgAJ
BR, Oleg
On Tuesday, January 8, 2019 at 5:44:33 AM UTC+1, Ryan wrote:
>
> Hi Jenn,
>Is there an update for this Roadmap?:
>
Hi Baptiste,
I understand the concerns.
If I may suggest one improvement I would suggest ACKing the message sooner,
explaining the timeout. I wasn't sure if my email just went into peoples
spam filters or was it the holidays/new year's lull
regards,
Jakub Bocheński
On Mon, Jan 7, 2019 at
If anything, I could see gRPC being a more useful protocol than CRDs here.
On Mon, Jan 7, 2019 at 8:07 PM Jesse Glick wrote:
> On Mon, Jan 7, 2019 at 6:57 PM Oleg Nenashev
> wrote:
> > I have also reached out to the Jenkins X team. Their feedback is that
> they would rather prefer to see
On Tue, Jan 8, 2019 at 9:17 AM Martin d'Anjou wrote:
> So you are really saying that Jenkins needs a new type of execution engine in
> order to support plugins that return non-simple data.
No no, I am saying that Jenkins needs a new type of execution engine,
and the proposed replacement would
>
>
> Besides not existing?
So you are really saying that Jenkins needs a new type of execution engine
in order to support plugins that return non-simple data.
This is way beyond my level of expertise. Has anything been attempted or
discussed in that area?
> If you are limiting yourself to
