Ok.
IMHO, It would be better to avoid too much complexity in your job
configuration. Personally, I would create one job per use case : each one
with default parameters value targeting each environment type
(dev/uat/prod/...).
In this way, you will have a simple job configuration (easily
maintainable), but also a clear and distinct build history for each
environment type.
Moreover, if you want to avoid managing too much jobs with the
(almost) same configuration, I would suggest you to consider some plugins
which can help you for that : Jenkins Pipeline (I'm assuming that your are
using FreeStyle job, right ?), Job DSL Plugin, Job Builder, ...
Hope it helps.
2017-06-30 14:06 GMT+02:00 paul b <pblake...@gmail.com>:
> I have tried to understand the various options but I am not too sure I can
> use it. Unless I am missing something...
>
> All I want is something simple like the following.
>
> my choice(dropdown) selections are:
> 1. dev
> 2. sit
> 3. uat
> 4. prod
>
> For example when I select dev I would like it set variables like
> server=dev-server
> port=dev-port
>
> so for each environment I can chose different servers and ports.
>
> which I can then pass into my maven build like
> mvn clean deploy -DSERVER=${server} -DPORT=${port}
>
>
> On Friday, 30 June 2017 12:49:33 UTC+1, mpapo - Michael Pailloncy wrote:
>>
>> Have you tried this plugin https://wiki.jenkins.io
>> /display/JENKINS/Extended+Choice+Parameter+plugin ?
>>
>> 2017-06-29 22:26 GMT+02:00 paul b <pbla...@gmail.com>:
>>
>>> Hi,
>>> I wondered if it is possible to do a parameterised build which can set
>>> multiple values. I would like to use the choice(dropdown box) and select a
>>> single value but that then set multiple values/parameters. This is
>>> mentioned in the by Martin Woit <https://wiki.jenkins.io/display/~mwoi> in
>>> the following. I also would like to use the choice of target of dev, sit
>>> etc etc. Sure other people have faced this same problem many times.
>>>
>>> https://wiki.jenkins.io/display/JENKINS/Parameterized+Build
>>>
>>> Hope you can help.
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/025ba41f-82d7-4e19-89d6-785884ff2757%
>>> 40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/025ba41f-82d7-4e19-89d6-785884ff2757%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/6f55af96-5003-4334-8b6a-db74505df33c%40googlegroups.
> com
> <https://groups.google.com/d/msgid/jenkinsci-users/6f55af96-5003-4334-8b6a-db74505df33c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAPO77c0b%3DTx-B7RMpy5CNSv%3D9B9wgXs%3DCBgEdhR5UYTESaAyhQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
