Jenkins: Filter build history by label or parameter
Is it possible to filter the build history in Jenkins so that only builds with a specific label or parameter show up?
Let's say I have some job that is parametrized. One of the parameters is a simple string which can either be "experimental" or "official". Is there any plugin which lets me filter the build history to only show the "official" builds?
jenkins continuous-integration jenkins-plugins
asked Apr 21 '15 at 9:52
Andreas FinklerAndreas Finkler
425413
add a comment |
Is it possible to filter the build history in Jenkins so that only builds with a specific label or parameter show up?
Let's say I have some job that is parametrized. One of the parameters is a simple string which can either be "experimental" or "official". Is there any plugin which lets me filter the build history to only show the "official" builds?
jenkins continuous-integration jenkins-plugins
asked Apr 21 '15 at 9:52
Andreas FinklerAndreas Finkler
425413
looking for same kind of plugin or method to do.
– Ramkumar D
Nov 11 '16 at 11:57
Related: stackoverflow.com/q/29768722/398670
– Craig Ringer
Nov 13 '18 at 2:11
Related: issues.jenkins-ci.org/browse/JENKINS-21056
– Craig Ringer
Nov 13 '18 at 2:12
add a comment |
Is it possible to filter the build history in Jenkins so that only builds with a specific label or parameter show up?
Let's say I have some job that is parametrized. One of the parameters is a simple string which can either be "experimental" or "official". Is there any plugin which lets me filter the build history to only show the "official" builds?
jenkins continuous-integration jenkins-plugins
asked Apr 21 '15 at 9:52
Andreas FinklerAndreas Finkler
425413
Is it possible to filter the build history in Jenkins so that only builds with a specific label or parameter show up?
Let's say I have some job that is parametrized. One of the parameters is a simple string which can either be "experimental" or "official". Is there any plugin which lets me filter the build history to only show the "official" builds?
jenkins continuous-integration jenkins-plugins
jenkins continuous-integration jenkins-plugins
asked Apr 21 '15 at 9:52
Andreas FinklerAndreas Finkler
425413
asked Apr 21 '15 at 9:52
Andreas FinklerAndreas Finkler
425413
asked Apr 21 '15 at 9:52
Andreas FinklerAndreas Finkler
425413
asked Apr 21 '15 at 9:52
Andreas FinklerAndreas Finkler
425413
asked Apr 21 '15 at 9:52
Andreas FinklerAndreas Finkler
425413
425413
looking for same kind of plugin or method to do.
– Ramkumar D
Nov 11 '16 at 11:57
Related: stackoverflow.com/q/29768722/398670
– Craig Ringer
Nov 13 '18 at 2:11
Related: issues.jenkins-ci.org/browse/JENKINS-21056
– Craig Ringer
Nov 13 '18 at 2:12
add a comment |
looking for same kind of plugin or method to do.
– Ramkumar D
Nov 11 '16 at 11:57
Related: stackoverflow.com/q/29768722/398670
– Craig Ringer
Nov 13 '18 at 2:11
Related: issues.jenkins-ci.org/browse/JENKINS-21056
– Craig Ringer
Nov 13 '18 at 2:12
looking for same kind of plugin or method to do.
– Ramkumar D
Nov 11 '16 at 11:57
looking for same kind of plugin or method to do.
– Ramkumar D
Nov 11 '16 at 11:57
Related: stackoverflow.com/q/29768722/398670
– Craig Ringer
Nov 13 '18 at 2:11
Related: stackoverflow.com/q/29768722/398670
– Craig Ringer
Nov 13 '18 at 2:11
Related: issues.jenkins-ci.org/browse/JENKINS-21056
– Craig Ringer
Nov 13 '18 at 2:12
Related: issues.jenkins-ci.org/browse/JENKINS-21056
– Craig Ringer
Nov 13 '18 at 2:12
add a comment |
3 Answers
3
active
oldest
votes
You can do it via this plugin https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters
The needed section for reading is "Filter by Job Parameterization"
answered Apr 21 '15 at 15:09
Stan EStan E
2,5701025
4
this does not seem to work in the way i expected. I have a job called joba, that accepts a parameter param. If i run this joba twice, once with param=abc and once with param=def. If I create a view using a filter based on the name=param value=abc, the view shows joba, but it shows build #2 with param=def, while I would like only those builds that had param=abc.
– Paul
Feb 26 '16 at 17:33
1
@Paul, me too looking for a plugin like you mentioned here.
– Ramkumar D
Nov 11 '16 at 11:59
This does not satisfy the question's requirements. They want to filter runs within a job. The View Job Filters plugin inspects the most recent run's parameters to decide whether or not to show the whole job in the list of jobs. It doesn't filter the runs at all.
– Craig Ringer
Nov 13 '18 at 2:07
add a comment |
Created question in monitoring plug-in for Jenkins GitHub site, and found this question...
https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/361
answered Mar 1 '18 at 7:51
DrasiusDrasius
3411522
add a comment |
Quicksearch of builds (runs) + custom run descriptions
Out of the box Jenkins supports a quicksearch over the build history that matches by label (description). Anything you put in the label can be used in the search:
... so you can use any plugin that can change the build label to add the info you want, then use quicksearch. The above example used the Pipeline plugin with the Groovy postbuild plugin, but you could use anything you feel like; say the description setter plugin or job name setter plugin.
You can then inject things like parameters into the job name. It's ugly, and annoying, and verbose. And there's no convenient way to save canned filters. But it works.
This workaround has a number of deficiencies:
- You can't save filters
- You can't view the build trend for a given filter (parameter, branch, etc)
- You can't view the Pipeline history for just a filter
which is why many people use:
Job templating - create duplicate jobs
If you want canned filters and convenient saved views, the widely used workaround at the moment seems to be to use the Jenkins Job Builder, a job template plugin, etc, to spawn lots of similar jobs. Use separate jobs to manage separate suites of parameters, etc. Then use Views to group up the jobs how you want.
Write a plugin?
I haven't found any pre-existing plugin to do it. You could implement your own Item that provides a custom job display and/or override the "Build History" list, but I haven't found any canned ones yet.
The Build History UI element is the BuildHistoryWidget (BuildHistoryWidget.java). It implements ExtensionPoint so you can override it with an @Extension. You shouldn't need to patch Jenkins.
A Google search for "extends HistoryWidget" -"class BuildHistoryWidget" failed to find any existing implementations.
Extend Pipeline Stage View Plugin
If you use Pipeline (Workflow) jobs, you may wish to consider extending or modifying the Pipeline Stage View Plugin to meet your needs.
It looks like it's designed to be somewhat extensible. See pipeline-staged.hbs.
answered Nov 13 '18 at 2:18
Craig RingerCraig Ringer
194k34392519
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f29768722%2fjenkins-filter-build-history-by-label-or-parameter%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can do it via this plugin https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters
The needed section for reading is "Filter by Job Parameterization"
answered Apr 21 '15 at 15:09
Stan EStan E
2,5701025
4
this does not seem to work in the way i expected. I have a job called joba, that accepts a parameter param. If i run this joba twice, once with param=abc and once with param=def. If I create a view using a filter based on the name=param value=abc, the view shows joba, but it shows build #2 with param=def, while I would like only those builds that had param=abc.
– Paul
Feb 26 '16 at 17:33
1
@Paul, me too looking for a plugin like you mentioned here.
– Ramkumar D
Nov 11 '16 at 11:59
This does not satisfy the question's requirements. They want to filter runs within a job. The View Job Filters plugin inspects the most recent run's parameters to decide whether or not to show the whole job in the list of jobs. It doesn't filter the runs at all.
– Craig Ringer
Nov 13 '18 at 2:07
add a comment |
You can do it via this plugin https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters
The needed section for reading is "Filter by Job Parameterization"
answered Apr 21 '15 at 15:09
Stan EStan E
2,5701025
4
this does not seem to work in the way i expected. I have a job called joba, that accepts a parameter param. If i run this joba twice, once with param=abc and once with param=def. If I create a view using a filter based on the name=param value=abc, the view shows joba, but it shows build #2 with param=def, while I would like only those builds that had param=abc.
– Paul
Feb 26 '16 at 17:33
1
@Paul, me too looking for a plugin like you mentioned here.
– Ramkumar D
Nov 11 '16 at 11:59
This does not satisfy the question's requirements. They want to filter runs within a job. The View Job Filters plugin inspects the most recent run's parameters to decide whether or not to show the whole job in the list of jobs. It doesn't filter the runs at all.
– Craig Ringer
Nov 13 '18 at 2:07
add a comment |
You can do it via this plugin https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters
The needed section for reading is "Filter by Job Parameterization"
answered Apr 21 '15 at 15:09
Stan EStan E
2,5701025
You can do it via this plugin https://wiki.jenkins-ci.org/display/JENKINS/View+Job+Filters
The needed section for reading is "Filter by Job Parameterization"
answered Apr 21 '15 at 15:09
Stan EStan E
2,5701025
answered Apr 21 '15 at 15:09
Stan EStan E
2,5701025
answered Apr 21 '15 at 15:09
Stan EStan E
2,5701025
answered Apr 21 '15 at 15:09
Stan EStan E
2,5701025
2,5701025
4
this does not seem to work in the way i expected. I have a job called joba, that accepts a parameter param. If i run this joba twice, once with param=abc and once with param=def. If I create a view using a filter based on the name=param value=abc, the view shows joba, but it shows build #2 with param=def, while I would like only those builds that had param=abc.
– Paul
Feb 26 '16 at 17:33
1
@Paul, me too looking for a plugin like you mentioned here.
– Ramkumar D
Nov 11 '16 at 11:59
This does not satisfy the question's requirements. They want to filter runs within a job. The View Job Filters plugin inspects the most recent run's parameters to decide whether or not to show the whole job in the list of jobs. It doesn't filter the runs at all.
– Craig Ringer
Nov 13 '18 at 2:07
add a comment |
4
this does not seem to work in the way i expected. I have a job called joba, that accepts a parameter param. If i run this joba twice, once with param=abc and once with param=def. If I create a view using a filter based on the name=param value=abc, the view shows joba, but it shows build #2 with param=def, while I would like only those builds that had param=abc.
– Paul
Feb 26 '16 at 17:33
1
@Paul, me too looking for a plugin like you mentioned here.
– Ramkumar D
Nov 11 '16 at 11:59
This does not satisfy the question's requirements. They want to filter runs within a job. The View Job Filters plugin inspects the most recent run's parameters to decide whether or not to show the whole job in the list of jobs. It doesn't filter the runs at all.
– Craig Ringer
Nov 13 '18 at 2:07
4
4
this does not seem to work in the way i expected. I have a job called joba, that accepts a parameter param. If i run this joba twice, once with param=abc and once with param=def. If I create a view using a filter based on the name=param value=abc, the view shows joba, but it shows build #2 with param=def, while I would like only those builds that had param=abc.
– Paul
Feb 26 '16 at 17:33
this does not seem to work in the way i expected. I have a job called joba, that accepts a parameter param. If i run this joba twice, once with param=abc and once with param=def. If I create a view using a filter based on the name=param value=abc, the view shows joba, but it shows build #2 with param=def, while I would like only those builds that had param=abc.
– Paul
Feb 26 '16 at 17:33
1
1
@Paul, me too looking for a plugin like you mentioned here.
– Ramkumar D
Nov 11 '16 at 11:59
@Paul, me too looking for a plugin like you mentioned here.
– Ramkumar D
Nov 11 '16 at 11:59
This does not satisfy the question's requirements. They want to filter runs within a job. The View Job Filters plugin inspects the most recent run's parameters to decide whether or not to show the whole job in the list of jobs. It doesn't filter the runs at all.
– Craig Ringer
Nov 13 '18 at 2:07
This does not satisfy the question's requirements. They want to filter runs within a job. The View Job Filters plugin inspects the most recent run's parameters to decide whether or not to show the whole job in the list of jobs. It doesn't filter the runs at all.
– Craig Ringer
Nov 13 '18 at 2:07
add a comment |
Created question in monitoring plug-in for Jenkins GitHub site, and found this question...
https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/361
answered Mar 1 '18 at 7:51
DrasiusDrasius
3411522
add a comment |
Created question in monitoring plug-in for Jenkins GitHub site, and found this question...
https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/361
answered Mar 1 '18 at 7:51
DrasiusDrasius
3411522
add a comment |
Created question in monitoring plug-in for Jenkins GitHub site, and found this question...
https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/361
answered Mar 1 '18 at 7:51
DrasiusDrasius
3411522
Created question in monitoring plug-in for Jenkins GitHub site, and found this question...
https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/361
answered Mar 1 '18 at 7:51
DrasiusDrasius
3411522
answered Mar 1 '18 at 7:51
DrasiusDrasius
3411522
answered Mar 1 '18 at 7:51
DrasiusDrasius
3411522
answered Mar 1 '18 at 7:51
DrasiusDrasius
3411522
3411522
add a comment |
add a comment |
Quicksearch of builds (runs) + custom run descriptions
Out of the box Jenkins supports a quicksearch over the build history that matches by label (description). Anything you put in the label can be used in the search:
... so you can use any plugin that can change the build label to add the info you want, then use quicksearch. The above example used the Pipeline plugin with the Groovy postbuild plugin, but you could use anything you feel like; say the description setter plugin or job name setter plugin.
You can then inject things like parameters into the job name. It's ugly, and annoying, and verbose. And there's no convenient way to save canned filters. But it works.
This workaround has a number of deficiencies:
- You can't save filters
- You can't view the build trend for a given filter (parameter, branch, etc)
- You can't view the Pipeline history for just a filter
which is why many people use:
Job templating - create duplicate jobs
If you want canned filters and convenient saved views, the widely used workaround at the moment seems to be to use the Jenkins Job Builder, a job template plugin, etc, to spawn lots of similar jobs. Use separate jobs to manage separate suites of parameters, etc. Then use Views to group up the jobs how you want.
Write a plugin?
I haven't found any pre-existing plugin to do it. You could implement your own Item that provides a custom job display and/or override the "Build History" list, but I haven't found any canned ones yet.
The Build History UI element is the BuildHistoryWidget (BuildHistoryWidget.java). It implements ExtensionPoint so you can override it with an @Extension. You shouldn't need to patch Jenkins.
A Google search for "extends HistoryWidget" -"class BuildHistoryWidget" failed to find any existing implementations.
Extend Pipeline Stage View Plugin
If you use Pipeline (Workflow) jobs, you may wish to consider extending or modifying the Pipeline Stage View Plugin to meet your needs.
It looks like it's designed to be somewhat extensible. See pipeline-staged.hbs.
answered Nov 13 '18 at 2:18
Craig RingerCraig Ringer
194k34392519
add a comment |
Quicksearch of builds (runs) + custom run descriptions
Out of the box Jenkins supports a quicksearch over the build history that matches by label (description). Anything you put in the label can be used in the search:
... so you can use any plugin that can change the build label to add the info you want, then use quicksearch. The above example used the Pipeline plugin with the Groovy postbuild plugin, but you could use anything you feel like; say the description setter plugin or job name setter plugin.
You can then inject things like parameters into the job name. It's ugly, and annoying, and verbose. And there's no convenient way to save canned filters. But it works.
This workaround has a number of deficiencies:
- You can't save filters
- You can't view the build trend for a given filter (parameter, branch, etc)
- You can't view the Pipeline history for just a filter
which is why many people use:
Job templating - create duplicate jobs
If you want canned filters and convenient saved views, the widely used workaround at the moment seems to be to use the Jenkins Job Builder, a job template plugin, etc, to spawn lots of similar jobs. Use separate jobs to manage separate suites of parameters, etc. Then use Views to group up the jobs how you want.
Write a plugin?
I haven't found any pre-existing plugin to do it. You could implement your own Item that provides a custom job display and/or override the "Build History" list, but I haven't found any canned ones yet.
The Build History UI element is the BuildHistoryWidget (BuildHistoryWidget.java). It implements ExtensionPoint so you can override it with an @Extension. You shouldn't need to patch Jenkins.
A Google search for "extends HistoryWidget" -"class BuildHistoryWidget" failed to find any existing implementations.
Extend Pipeline Stage View Plugin
If you use Pipeline (Workflow) jobs, you may wish to consider extending or modifying the Pipeline Stage View Plugin to meet your needs.
It looks like it's designed to be somewhat extensible. See pipeline-staged.hbs.
answered Nov 13 '18 at 2:18
Craig RingerCraig Ringer
194k34392519
add a comment |
Quicksearch of builds (runs) + custom run descriptions
Out of the box Jenkins supports a quicksearch over the build history that matches by label (description). Anything you put in the label can be used in the search:
... so you can use any plugin that can change the build label to add the info you want, then use quicksearch. The above example used the Pipeline plugin with the Groovy postbuild plugin, but you could use anything you feel like; say the description setter plugin or job name setter plugin.
You can then inject things like parameters into the job name. It's ugly, and annoying, and verbose. And there's no convenient way to save canned filters. But it works.
This workaround has a number of deficiencies:
- You can't save filters
- You can't view the build trend for a given filter (parameter, branch, etc)
- You can't view the Pipeline history for just a filter
which is why many people use:
Job templating - create duplicate jobs
If you want canned filters and convenient saved views, the widely used workaround at the moment seems to be to use the Jenkins Job Builder, a job template plugin, etc, to spawn lots of similar jobs. Use separate jobs to manage separate suites of parameters, etc. Then use Views to group up the jobs how you want.
Write a plugin?
I haven't found any pre-existing plugin to do it. You could implement your own Item that provides a custom job display and/or override the "Build History" list, but I haven't found any canned ones yet.
The Build History UI element is the BuildHistoryWidget (BuildHistoryWidget.java). It implements ExtensionPoint so you can override it with an @Extension. You shouldn't need to patch Jenkins.
A Google search for "extends HistoryWidget" -"class BuildHistoryWidget" failed to find any existing implementations.
Extend Pipeline Stage View Plugin
If you use Pipeline (Workflow) jobs, you may wish to consider extending or modifying the Pipeline Stage View Plugin to meet your needs.
It looks like it's designed to be somewhat extensible. See pipeline-staged.hbs.
answered Nov 13 '18 at 2:18
Craig RingerCraig Ringer
194k34392519
Quicksearch of builds (runs) + custom run descriptions
Out of the box Jenkins supports a quicksearch over the build history that matches by label (description). Anything you put in the label can be used in the search:
... so you can use any plugin that can change the build label to add the info you want, then use quicksearch. The above example used the Pipeline plugin with the Groovy postbuild plugin, but you could use anything you feel like; say the description setter plugin or job name setter plugin.
You can then inject things like parameters into the job name. It's ugly, and annoying, and verbose. And there's no convenient way to save canned filters. But it works.
This workaround has a number of deficiencies:
- You can't save filters
- You can't view the build trend for a given filter (parameter, branch, etc)
- You can't view the Pipeline history for just a filter
which is why many people use:
Job templating - create duplicate jobs
If you want canned filters and convenient saved views, the widely used workaround at the moment seems to be to use the Jenkins Job Builder, a job template plugin, etc, to spawn lots of similar jobs. Use separate jobs to manage separate suites of parameters, etc. Then use Views to group up the jobs how you want.
Write a plugin?
I haven't found any pre-existing plugin to do it. You could implement your own Item that provides a custom job display and/or override the "Build History" list, but I haven't found any canned ones yet.
The Build History UI element is the BuildHistoryWidget (BuildHistoryWidget.java). It implements ExtensionPoint so you can override it with an @Extension. You shouldn't need to patch Jenkins.
A Google search for "extends HistoryWidget" -"class BuildHistoryWidget" failed to find any existing implementations.
Extend Pipeline Stage View Plugin
If you use Pipeline (Workflow) jobs, you may wish to consider extending or modifying the Pipeline Stage View Plugin to meet your needs.
It looks like it's designed to be somewhat extensible. See pipeline-staged.hbs.
answered Nov 13 '18 at 2:18
Craig RingerCraig Ringer
194k34392519
edited Nov 13 '18 at 2:45
answered Nov 13 '18 at 2:18
Craig RingerCraig Ringer
194k34392519
answered Nov 13 '18 at 2:18
Craig RingerCraig Ringer
194k34392519
answered Nov 13 '18 at 2:18
Craig RingerCraig Ringer
194k34392519
194k34392519
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f29768722%2fjenkins-filter-build-history-by-label-or-parameter%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
looking for same kind of plugin or method to do.
– Ramkumar D
Nov 11 '16 at 11:57
Related: stackoverflow.com/q/29768722/398670
– Craig Ringer
Nov 13 '18 at 2:11
Related: issues.jenkins-ci.org/browse/JENKINS-21056
– Craig Ringer
Nov 13 '18 at 2:12