I am not familiar with the plugin implementation enough, though I see no
reason why such behaviour should not be in core as well. Anyway, having 2
plugins that does to same with slightly different defaults sounds odd to me.
How about adding an option to the existing plugin that would register
On 19.06.2015, at 15:13, ogondza ogon...@gmail.com wrote:
I see no reason why such behaviour should not be in core as well.
I started working on something like this a while back.
https://github.com/daniel-beck/jenkins/commit/d9f140904b7850c77f68829b2161d8d2ee39e85c
Maybe it's time to finish
I have seen the plugin, thanks Oliver.
I would like to do the opposite: replace the old action with the new
one that I've implemented.
My contractors are confused by the presence of two similar icons, and
they would like to preserve the one nearest to their reality.
On Fri, Jun 19, 2015 at 10:37
There already is a plugin that injects parameters via URL already[1]. In
that particular case it is the _plugin's_ URL that was hidden as it was
causing confusion to users and was accessed by pre-generated URLs most of
the time.
[1]
Hi all,
Apart from a specially crafted CSS, is there any way to hide default
Jenkins action?
For example, the Build Now action.. I have developed a custom action, which
basically does a BuildWithParams with a variable set of default parameters.
I would like to hide the Build Now action, in order
