[JIRA] (JENKINS-20468) Multijob should provide configuration option to be a flyweight tasks
Title: Message Title Tim De Backer updated an issue Jenkins / JENKINS-20468 Multijob should provide configuration option to be a flyweight tasks Change By: Tim De Backer Comment: This would be very helpful indeed. We have a set-up in which only one job may run at the same time. We are combining this plugin with the NodeLabel Parameter plugin so all jobs of the MultiJob are run on the same node. However, the MultiJob itself takes up the single executor on that node! Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17827) An intuïtive way to pass a variable/parameter (e.g. multijob build number) to all its downstream jobs.
Title: Message Title Tim De Backer updated an issue Jenkins / JENKINS-17827 An intuïtive way to pass a variable/parameter (e.g. multijob build number) to all its downstream jobs. Change By: Tim De Backer Comment: Is there any progress on this already? Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-plugin] (JENKINS-26807) Create 'Remote SSH host' Job parameter type, whose value can be used by Remote Execution build step
Tim De Backer created JENKINS-26807 Create Remote SSH host Job parameter type, whose value can be used by Remote Execution build step Issue Type: New Feature Assignee: Unassigned Components: ssh-plugin Created: 05/Feb/15 1:26 PM Description: Build step 'Execute shell script remotely on host using ssh' takes one of the configured remote hosts as value. This makes the job configuration vary static. It would be nice if this could be parameterized. Implementing this requires two features: Special type of Job parameter allows the user to select one of the configures remote hosts. Optionally, he could select subset of SSH hosts using a regex Optionally, he could select default SSH host Behavior is very similar to Subversion branch selection parameter The 'Execute shell script remotely' builder must be able to take such a parameter Project: Jenkins Labels: parameter parameterized ssh remote host Priority: Major Reporter: Tim De Backer 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [label-verifier] (JENKINS-24058) Allow label auto-detection in addition to verifying existing labels using the same validation command.
Tim De Backer created JENKINS-24058 Allow label auto-detection in addition to verifying existing labels using the same validation command. Issue Type: New Feature Assignee: Oleg Nenashev Components: label-verifier Created: 31/Jul/14 7:37 AM Description: The current plug-in looks at the labels of a slave that comes online and verifies if those labels are still valid. That same validation script/command can also be used to auto-detect whether some label is applicable to any slave that comes online. For example, Jenkins could check the installed python version whenever a slave comes online and update (i.e. add, remove or replace) that slave's labels accordingly. If python 3.3 was found, label 'python-2.6' is no longer valid and should be removed and label 'python-3.3' is valid and should be added. The general 'python' label will still be valid and remains unchanged. In the label configuration page, the user may then choose between the verification and auto-detect option for each individual label. Project: Jenkins Labels: slave slaves Priority: Major Reporter: Tim De Backer 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [label-verifier] (JENKINS-24058) Allow label auto-detection in addition to verifying existing labels using the same validation command.
Tim De Backer updated JENKINS-24058 Allow label auto-detection in addition to verifying existing labels using the same validation command. Change By: Tim De Backer (31/Jul/14 7:46 AM) Description: Thecurrentplug-inlooksatthelabelsofaslavethatcomesonlineandverifiesifthoselabelsarestillvalid.Thatsamevalidationscript/commandcanalsobeusedtoauto-detectwhethersomelabelisapplicabletoanyslavethatcomesonline.Forexample,Jenkinscouldchecktheinstalledpythonversionwheneveraslavecomesonlineandupdate(i.e.add,removeorreplace)thatslaveslabelsaccordingly.Ifpython3.3wasfound,labelpython-2.6isnolongervalidandshouldberemovedandlabelpython-3.3isvalidandshouldbeadded.Thegeneralpythonlabelwillstillbevalidandremainsunchanged.Inthelabelconfigurationpage,theusermaythenchoosebetweentheverificationandauto-detectoptionforeachindividuallabel. Edit:Aloggingfeaturemaybedesired,sotheadministratorknowswhichlabelswereaddedorstrippedautomaticallybytheplug-in. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [label-verifier] (JENKINS-24058) Allow label auto-detection in addition to verifying existing labels using the same validation command.
Tim De Backer
updated JENKINS-24058
Allow label auto-detection in addition to verifying existing labels using the same validation command.
Change By:
Tim De Backer
(31/Jul/14 7:48 AM)
Labels:
labellabels
slaveslaves
Description:
Thecurrentplug-inlooksatthelabelsofaslavethatcomesonlineandverifiesifthoselabelsarestillvalid.Thatsamevalidationscript/commandcanalsobeusedto
*
auto-detect
*
whethersomelabelisapplicabletoanyslavethatcomesonline
and*automaticallyupdate*itslabelsaccordingly
.
{quote}
Forexample,Jenkinscouldchecktheinstalledpythonversionwheneveraslavecomesonlineandupdate(i.e.add,removeorreplace)thatslaveslabelsaccordingly.Ifpython3.3wasfound,labelpython-2.6isnolongervalidandshouldberemovedandlabelpython-3.3isvalidandshouldbeadded.Thegeneralpythonlabelwillstillbevalidandremainsunchanged.
{quote}
Inthelabel
*
configurationpage
*
,theusermaythenchoosebetweentheverificationandauto-detectoptionforeachindividuallabel.
Edit:
A
*
logging
*
featuremaybedesired,sotheadministratorknowswhichlabelswereaddedorstrippedautomaticallybytheplug-in.
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [label-verifier] (JENKINS-24058) Allow label auto-detection in addition to verifying existing labels using the same validation command.
Tim De Backer
updated JENKINS-24058
Allow label auto-detection in addition to verifying existing labels using the same validation command.
Change By:
Tim De Backer
(31/Jul/14 8:16 AM)
Description:
Thecurrentplug-inlooksatthelabelsofaslavethatcomesonlineandverifiesifthoselabelsarestillvalid.Thatsamevalidationscript/commandcanalsobeusedto*auto-detect*whethersomelabelisapplicabletoanyslavethatcomesonlineand*automaticallyupdate*itslabelsaccordingly.{quote}Forexample,Jenkinscouldchecktheinstalledpythonversionwheneveraslavecomesonlineandupdate(i.e.add,removeorreplace)thatslaveslabelsaccordingly.Ifpython
2.6wasreplacedbypython
3.3
was
onthesystemandthereforeonlypythonversion3.3is
found,labelpython-2.6isnolongervalidandshouldberemovedandlabelpython-3.3
is
becomes
validandshouldbeadded.Thegeneralpythonlabelwillstillbevalidandremainsunchanged.{quote}Inthelabel*configurationpage*,theusermaythenchoosebetweentheverificationandauto-detectoptionforeachindividuallabel.A*logging*featuremaybedesired,sotheadministratorknowswhichlabelswereaddedorstrippedautomaticallybytheplug-in.
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-20468) Multijob should provide configuration option to be a flyweight tasks
Tim De Backer commented on JENKINS-20468 Multijob should provide configuration option to be a flyweight tasks This would be very helpful indeed. We have a set-up in which only one job may run at the same time. We are combining this plugin with the NodeLabel Parameter plugin so all jobs of the MultiJob are run on the same node. However, the MultiJob itself takes up the single executor on that node! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-20723) Add an option to include or exclude disabled jobs in the 'Unstable jobs' widget.
Tim De Backer commented on JENKINS-20723 Add an option to include or exclude disabled jobs in the Unstable jobs widget. Is there any progress on this? Thanks! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-17827) An intuïtive way to pass a variable/parameter (e.g. multijob build number) to all its downstream jobs.
Tim De Backer commented on JENKINS-17827 An intuïtive way to pass a variable/parameter (e.g. multijob build number) to all its downstream jobs. Is there any progress on this already? Thanks! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-23510) Support for NodeLabel Parameter plugin in the Configuration Slicing plugin
Tim De Backer created JENKINS-23510 Support for NodeLabel Parameter plugin in the Configuration Slicing plugin Issue Type: Improvement Assignee: mdonohue Components: configurationslicing, nodelabelparameter Created: 20/Jun/14 1:31 PM Description: The NodeLabel parameter plugin provides a new type of parameter. It would be nice to support this parameter type in the Configuration Slicing plugin! Project: Jenkins Priority: Major Reporter: Tim De Backer 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-20723) Add an option to include or exclude disabled jobs in the 'Unstable jobs' widget.
Tim De Backer created JENKINS-20723 Add an option to include or exclude disabled jobs in the Unstable jobs widget. Issue Type: Improvement Affects Versions: current Assignee: Peter Hayes Components: dashboard-view Created: 22/Nov/13 2:08 PM Description: In a situation with many jobs (where the list of unstable jobs is particularly handy) there are often a few disabled jobs as well. The current 'Unstable jobs' widget handles disabled jobs like any other. Disabled jobs are thus included in the list if their last build failed or was unstable. At this moment, the user can already choose to include or exclude the (non-failed) unstable jobs, using a simple checkbox. A similar checkbox should be added to let the user include or exclude (failed/unstable) disabled jobs. Project: Jenkins Priority: Major Reporter: Tim De Backer 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17826) Support for automatic test result aggregation of downstream jobs
Tim De Backer
created JENKINS-17826
Support for automatic test result aggregation of downstream jobs
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core, jenkins-multijob-plugin
Created:
02/May/13 8:52 AM
Description:
It is possible in Jenkins to aggregate tests results from downstream jobs. It requires the downstream jobs to expose their test reports as artifacts and create fingerprints for them.
However, in the parent job it is quite hard to retrieve the correct results for aggregation. In particular the binding between the multijob (batch) build and the the correct downstream builds to retrieve the artifacts.
The multijob plugin is suited to do this kind of batch Unit Testing. It would therefore be a great improvement if it supported test result aggregation out of the box.
Ofcourse the downstream jobs must still be configured correctly: test result exposed as artifacts and fingerprints created.
The MultiJob could for example gather all artifacts (i.e. test reports) in a fixed directory (e.g. ${WORKSPACE}/reports) across all downstream jobs.
Project:
Jenkins
Labels:
jenkins
plugin
multi-job
testing
artifact
unittests
aggregation
Priority:
Major
Reporter:
Tim De Backer
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [envinject] (JENKINS-17827) An intuïtive way to pass a variable/parameter (e.g. multijob build number) to all its downstream jobs.
Tim De Backer
created JENKINS-17827
An intuïtive way to pass a variable/parameter (e.g. multijob build number) to all its downstream jobs.
Issue Type:
Improvement
Assignee:
Gregory Boissinot
Components:
envinject, jenkins-multijob-plugin, parameters
Created:
02/May/13 9:02 AM
Description:
The current multijob implementation passes parameters to the specific downstream job builds that are part of it. The master value overwrites the default values of the downstream jobs for that parameters.
It would be handy if the multijob plugin has an intuïtive way to pass select information to these specific downstream builds.
This would allow the batch to overwrite a downstream job parameter with a value that is fixed (non-interactive) at the multijob level. Or it would allow to pass the multijob build number as a value with a specific name (e.g. BATCH_NUMBER) chosen by the user.
The downstream jobs can then check if this value exists, otherwise it will be an unresolvable macro and just stay empty.
Use case:
Using the build-name-setter plugin, the downstream build numbers could be set to ${BUILD_NUMBER}${BATCH_NUMBER}, where batch number is either empty (when the downstream job is run on its own) or " - Batch ${BUILD_NUMBER}" (when the variable was set in the upstream multijob project).
Project:
Jenkins
Labels:
multi-job
parameter
variable
downstream
upstream
Priority:
Major
Reporter:
Tim De Backer
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
