Hi,
You probably might have found a solution now. Anyway I had similar
requirement recently and found this thread. Later I came across a plugin
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Dynamic+Parameter+Plug-in.
Using this plugin you can send a dynamic parameter to the build. It al
Hi,
The environment variable BUILD_CAUSE already provides you how the build has
been triggered. You don't need any plugin or parameter to get this
information.
Cheers,
Vincent
2013/7/29 Benjamin Hofmann
> My personal usecase would be to differ between an auto triggered build and
> a manual b
My personal usecase would be to differ between an auto triggered build and
a manual build. But I believe the envinject can fulfill that need quite
well.
On Monday, July 22, 2013 11:42:20 AM UTC+2, Daniel Beck wrote:
>
> An actual use case for this might be helpful. Right now, this looks a lot
>
An actual use case for this might be helpful. Right now, this looks a lot like
an XY problem [1].
Also, a possible solution is a Choice parameter with only one value to select.
But note that e.g. Parameterized Trigger will just override this when you
specify a different value there, so it's on
Although not ideal, you can use this plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Global+Variable+String+Parameter+Plugin
-Hao
On Jul 21, 2013, at 4:53 PM, Thomas Fields wrote:
> >>No, that I am aware of. I've been kind of thinking about something similar
> but more of like a set of var
>>No, that I am aware of. I've been kind of thinking about something similar
but more of like a set of variables that can be defined with the job, and
then referenced in multiple places within the job configuration.
Yeah, something like this would be perfect for my needs.
Surely it's not too diff
envinject plugin does this. But not visible as 'fake' job parameters.
On 21.07.2013, at 15:49, Pete wrote:
> No, that I am aware of. I've been kind of thinking about something similar
> but more of like a set of variables that can be defined with the job, and
> then referenced in multiple pla
No, that I am aware of. I've been kind of thinking about something similar
but more of like a set of variables that can be defined with the job, and
then referenced in multiple places within the job configuration.
On Sun, Jul 21, 2013 at 1:17 AM, Thomas Fields wrote:
> Hi there,
>
> In my job c
Hi there,
In my job configs I've been ticking the "This build is parameterized" box
and then using the String parameter option. I can then use my new parameter
through most of my job setup and so far this has been working great.
I'm now in a situation where I want my String parameter to be unedit
