Quantcast

[JIRA] (JENKINS-14428) Provide group operations for "Disable build slicer"

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14428) Provide group operations for "Disable build slicer"

JIRA noreply@jenkins-ci.org
Issue Type: Improvement Improvement
Assignee: mdonohue
Components: configurationslicing
Created: 13/Jul/12 7:44 PM
Description:

Please take a look at adding three buttons to the disable build slicer configuration page:

Check all, Uncheck all, Invert Selection

+ provide a regexp based configuration the same way as it is done to specify the jobs for the view. We have 700+ jobs - clicking through them is pain.

Project: Jenkins
Priority: Minor Minor
Reporter: eguess74
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14428) Provide group operations for "Disable build slicer"

JIRA noreply@jenkins-ci.org
Jacob Robertson resolved Improvement JENKINS-14428 as Fixed

Here is what I could do quickly for you, and it lines up with what I needed for myself anyways.

  • Added a "string slicer" that behaves like all the other slicers - this allows you to quickly cut and paste many job names into the "true" or "false" buckets
  • You can (and should) use the "Configuration By View" feature that is already implemented. It allows you to configure jobs that are already organized by views. (explained in more detail on the wiki) This is the way I will be directing anyone that requests easier ways to do configuration slice by selecting jobs more fine-grained. Rather than this plugin trying to implement every feature requested for choosing which jobs to select, just make sure that you have smarter views, and then this plugin can configure one view at a time. See the View Job Filters plugin if you need help getting started on that.

See latest version 1.32 of this plugin for the string slicer feature.

Change By: Jacob Robertson (14/Jul/12 7:28 PM)
Status: Open Resolved
Resolution: Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14428) Provide group operations for "Disable build slicer"

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
eguess74 commented on Improvement JENKINS-14428

Thanks for fast turn around - i will install and report how it will go.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-14428) Provide group operations for "Disable build slicer"

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
eguess74 commented on Improvement JENKINS-14428

The string variant worked very well, thank you!
AS for the configuration by views - We do have views and we use them to separate our hundreds of projects to groups, but even if I would want to use it - it will still require me to click through dozens of check boxes if i want to disable the whole group. Therefore "check all"/"uncheck all" still makes a lot of sense to me. What if i need to disable three/four groups??

Our job names are actually including group name (in a format of group+jobname), therefore if I would like to work with one or more groups I will now go to the string slicer, cause it has jobs listed in alphabetic order so i can manage them much easier, but never to "by view" - too many clicks.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Loading...