>From my point of view, this type of plugin would be useless as without setting up the Job to use the parameter it is just another step that slows the user from starting a build.
For example the user adds a String parameter name MESSAGE with a value "reason for building", when is this going to be used in any of the build steps unless they have a some code to check for it. if it is checked e.g. if ($MESSAGE != "") then print $MESSAGE to file.txt However if the user has to add it, how are they to know the correct name and what it does. so I would just add the parameter it as an option and leave the default to "", with a description on how it affects the build. In most cases the current parameters can be setup to provide a standard set of defaults that the build uses, (allowing the user to just accept these values) while allowing them to be changed to provide behaviour for the less often used cases. And from a security point of view if only I had access to create and modify jobs, all other users can start them, I would not want other users to be able to add extra parameters, over and above then ones that are exposed with the job. Chris. On Friday, October 26, 2012 12:35:59 PM UTC+1, AdvanTiSS wrote: > > Could you describe usecase for that parameter? > > On Friday, October 26, 2012 1:54:20 PM UTC+3, LordShacks wrote: >> >> Hi >> >> I am currently attempting to write a Jenkins plugin that is similar to >> the Parameterized Build option in the Configure Project page. >> >> I want to create a plugin that lets the user specify the type of >> parameter in addition to the parameter value when the Build Now button is >> pressed. >> >> As far as I can see there is no currently functionality in Jenkins that >> allows the parameter type and value to be specified when a build is >> scheduled. >> >> I was wondering if it is possible to implement this feature in Jenkins. >> >> Many thanks >> >
