>
>
> 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
at various events, including DevOps World
- JW. Is that part of the swag budget?
Thanks,
Martin d'Anjou
Jenkins GSoC Org Admin
On Thu, Dec 27, 2018 at 7:03 PM Oleg Nenashev
wrote:
> Dear all,
>
> Please find the Jenkins GSoC budget status update for 2018. You can find
> my previous
Disclaimer: I do not use those plugins.
*Can you suggest a better UI name for this trait than "Discover branches"?*
No.
>
> *Does "Discover branches" scream out what it does?*
Yes.
>
> *Can you suggest a better UI name for the "Strategy" field in "Discover
> branches"?*
No.
>
>-
s soon as possible (March 25 is
the deadline).
Please copy the jenkinsci-dev@googlegroups.com mailing list on these
discussions, it allows Jenkins contributors and Google reviewers to
investigate the conversation history.
Best Regards,
Martin d'Anjou
--
You received this message becau
are in the issue link above.
If you are no longer interested in being the maintainer of the plugin,
please let me know, I will adopt it.
Best Regards,
Martin d'Anjou
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubs
