jenkins-control-plugin icon indicating copy to clipboard operation
jenkins-control-plugin copied to clipboard

Published 20 hours ago • verified publisher icon MCMicS

Run configuration

Open klyashko opened this issue 4 years ago • 6 comments

Hi. Thanks for the useful plugin.

Have you considered to implement run configuration for being able to save common jobs configuration with it's parameters to don't fill them in each time?

klyashko avatar Apr 28 '20 19:04 klyashko

Not yet but sounds great.

Thanks for this suggestion

MCMicS avatar Apr 28 '20 19:04 MCMicS

@klyashko Do you think that only jobs with parameters should avaiable for run configuration? And do you have an update scenario if new paramter are added or some removed?

I would think it is easier to check if all parameters are still available and fail otherwise

Whats your opinion?

MCMicS avatar May 19 '20 18:05 MCMicS

@MCMicS About first question, having an opportunity to run a job without parameters with shortcut seems good to me. In case of adding new parameters you can just render them in edit window and that's enough. In case of removal I like your idea.

klyashko avatar May 19 '20 19:05 klyashko

If a new parameter was add you show the current dialog with new one only right?

Another option is to show current build dialog if parameter mismatch (either new added or old was removed)

MCMicS avatar May 19 '20 19:05 MCMicS

I mean if new parameter was added I'd suggest two option:

  1. Don't do anything until a user decide to edit the configuration (I think that it's the most common case. And if it's required Jenkins will fail to start the job)
  2. Fail when user tries to run it with message what happened. Or show edit dialog. (that's more defensive option)

klyashko avatar May 19 '20 20:05 klyashko

Thanks for feedback. I will try one of the option and look how the ux is.

I'm currently working on it but don't if it is in next release. Maybe i create an preview for the feature to test

MCMicS avatar May 19 '20 20:05 MCMicS