[JIRA] [ws-cleanup-plugin] (JENKINS-28151) if node switched off after execution some garbage generated
Roman G created JENKINS-28151 if node switched off after execution some garbage generated Issue Type: Bug Assignee: vjuranek Components: ws-cleanup-plugin Created: 29/Apr/15 12:24 PM Description: because of specifics of our project we need reboot node just after jenkins build completed After updating I observe that some garbage generated if we enable workspace clean up e.g. I see many dirs like this /local/home/jenkins/fsroot/workspace/my project_ws-cleanup_1430299254267 I suppose that it's connected to asynchronously deletion and deletion is not completed until node reboot Project: Jenkins Priority: Minor Reporter: Roman G 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] [cppcheck-plugin] (JENKINS-26456) Using cppcheck with CI with gerrit is dispirit
Roman G created JENKINS-26456 Using cppcheck with CI with gerrit is dispirit Issue Type: Improvement Assignee: Gregory Boissinot Components: cppcheck-plugin Created: 16/Jan/15 7:31 AM Description: cppcheck is oriented on linear history and provide useful feature for it: trend color highlighting for diff between current and previous checks gerrit usage mean that CI will be done on non-series commit, non-linear history and diff highlighting in gerrit case is pretty dispirit It will be very nice to have possibility to switch off diff and diff highlighting and see only cppchecks warnings from current runs Environment: jenkins 1.5x cppcheck 1.2x Project: Jenkins Priority: Minor Reporter: Roman G 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-23398) Phase stopped on 'Notifying upstream projects of job completion'
Roman G
created JENKINS-23398
Phase stopped on Notifying upstream projects of job completion
Issue Type:
Bug
Assignee:
Unassigned
Components:
jenkins-multijob-plugin
Created:
11/Jun/14 7:55 AM
Description:
Multijobcannot receive message fromphase job and wait in loop
Multijob is waiting phase
Starting build job xxx
Phase job set geen ball but cannot complete/notify multijob
{{Archiving artifacts
Description set: betazoid/B1126/C-BETAZOID
Notifying upstream projects of job completion}}
log from catalina.out is clear until abort job and shows exception only after it
{{
INFO: betazoid-kvm-cluster-create #190 main build action completed: SUCCESS
Jun 11, 2014 12:22:24 AM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener onCompleted
INFO: Completed. Build: betazoid-kvm-cluster-create #190 Cause: null
Jun 11, 2014 12:26:49 AM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Download metadata
Jun 11, 2014 12:26:49 AM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Download metadata. 0 ms
getConfigPage - /pyenv_wrapper/config
Jun 11, 2014 12:35:45 AM hudson.model.Run execute
INFO: betazoid #185 aborted
java.lang.InterruptedException
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(Unknown Source)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source)
at java.util.concurrent.ArrayBlockingQueue.take(Unknown Source)
at com.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:148)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.Build$BuildExecution.build(Build.java:199)
at hudson.model.Build$BuildExecution.doRun(Build.java:160)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134)
at hudson.model.Run.execute(Run.java:1676)
at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
WD is /usr/share/tomcat6/.jenkins/jobs/betazoid/workspaceJun 11, 2014 12:35:45 AM com.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener
}}
Environment:
Jenkins ver. 1.554.1
MultiJob 1.13
Tomcat 7.0.50
Project:
Jenkins
Priority:
Critical
Reporter:
Roman G
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-23398) Phase stopped on 'Notifying upstream projects of job completion'
Roman G
updated JENKINS-23398
Phase stopped on Notifying upstream projects of job completion
Change By:
Roman G
(11/Jun/14 7:57 AM)
Description:
MultijobcannotreceivemessagefromphasejobandwaitinloopMultijobiswaitingphase{
{
Startingbuildjobxxx}
}
Phasejobsetgeenballbutcannotcomplete/notifymultijob{
{
ArchivingartifactsDescriptionset:betazoid/B1126/C-BETAZOIDNotifyingupstreamprojectsofjobcompletion}
}
logfromcatalina.outisclearuntilabortjobandshowsexceptiononlyafterit{
{
INFO:betazoid-kvm-cluster-create#190mainbuildactioncompleted:SUCCESSJun11,201412:22:24AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListeneronCompletedINFO:Completed.Build:betazoid-kvm-cluster-create#190Cause:nullJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:StartedDownloadmetadataJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:FinishedDownloadmetadata.0msgetConfigPage-/pyenv_wrapper/configJun11,201412:35:45AMhudson.model.RunexecuteINFO:betazoid#185abortedjava.lang.InterruptedException atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(UnknownSource) atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(UnknownSource) atjava.util.concurrent.ArrayBlockingQueue.take(UnknownSource) atcom.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:148) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) athudson.model.Build$BuildExecution.build(Build.java:199) athudson.model.Build$BuildExecution.doRun(Build.java:160) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) athudson.model.Run.execute(Run.java:1676) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)WDis/usr/share/tomcat6/.jenkins/jobs/betazoid/workspaceJun11,201412:35:45AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener}
}
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-23398) Phase stopped on 'Notifying upstream projects of job completion'
Roman G
updated JENKINS-23398
Phase stopped on Notifying upstream projects of job completion
Change By:
Roman G
(11/Jun/14 7:59 AM)
Description:
MultijobcannotreceivemessagefromphasejobandwaitinloopMultijobiswaitingphase{
quote}
Startingbuildjobxxx
{quote
}Phasejobsetgeenballbutcannotcomplete/notifymultijob{
quote}
ArchivingartifactsDescriptionset:betazoid/B1126/C-BETAZOIDNotifyingupstreamprojectsofjobcompletion
{quote
}logfromcatalina.outisclearuntilabortjobandshowsexceptiononlyafterit{
quote}
INFO:betazoid-kvm-cluster-create#190mainbuildactioncompleted:SUCCESSJun11,201412:22:24AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListeneronCompletedINFO:Completed.Build:betazoid-kvm-cluster-create#190Cause:nullJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:StartedDownloadmetadataJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:FinishedDownloadmetadata.0msgetConfigPage-/pyenv_wrapper/configJun11,201412:35:45AMhudson.model.RunexecuteINFO:betazoid#185abortedjava.lang.InterruptedException atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(UnknownSource) atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(UnknownSource) atjava.util.concurrent.ArrayBlockingQueue.take(UnknownSource) atcom.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:148) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) athudson.model.Build$BuildExecution.build(Build.java:199) athudson.model.Build$BuildExecution.doRun(Build.java:160) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) athudson.model.Run.execute(Run.java:1676) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)WDis/usr/share/tomcat6/.jenkins/jobs/betazoid/workspaceJun11,201412:35:45AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener
{quote
}
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-23398) Phase stopped on 'Notifying upstream projects of job completion'
Roman G
updated JENKINS-23398
Phase stopped on Notifying upstream projects of job completion
Change By:
Roman G
(11/Jun/14 7:59 AM)
Description:
MultijobcannotreceivemessagefromphasejobandwaitinloopMultijobiswaitingphase{quote}Startingbuildjobxxx{quote}Phasejobsetgeenballbutcannotcomplete/notifymultijob{quote}ArchivingartifactsDescriptionset:
betazoid/B1126/C-BETAZOID
xxx
Notifyingupstreamprojectsofjobcompletion{quote}logfromcatalina.outisclearuntilabortjobandshowsexceptiononlyafterit{quote}INFO:betazoid-kvm-cluster-create#190mainbuildactioncompleted:SUCCESSJun11,201412:22:24AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListeneronCompletedINFO:Completed.Build:betazoid-kvm-cluster-create#190Cause:nullJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:StartedDownloadmetadataJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:FinishedDownloadmetadata.0msgetConfigPage-/pyenv_wrapper/configJun11,201412:35:45AMhudson.model.RunexecuteINFO:betazoid#185abortedjava.lang.InterruptedException atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(UnknownSource) atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(UnknownSource) atjava.util.concurrent.ArrayBlockingQueue.take(UnknownSource) atcom.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:148) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) athudson.model.Build$BuildExecution.build(Build.java:199) athudson.model.Build$BuildExecution.doRun(Build.java:160) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) athudson.model.Run.execute(Run.java:1676) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)WDis/usr/share/tomcat6/.jenkins/jobs/betazoid/workspaceJun11,201412:35:45AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener{quote}
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-23398) Phase stopped on 'Notifying upstream projects of job completion'
Roman G
updated JENKINS-23398
Phase stopped on Notifying upstream projects of job completion
Change By:
Roman G
(11/Jun/14 8:00 AM)
Description:
MultijobcannotreceivemessagefromphasejobandwaitinloopMultijobiswaitingphase{quote}Startingbuildjobxxx{quote}Phasejobsetgeenballbutcannotcomplete/notifymultijob{quote}ArchivingartifactsDescriptionset:xxxNotifyingupstreamprojectsofjobcompletion{quote}logfromcatalina.outisclearuntilabortjobandshowsexceptiononlyafterit{quote}INFO:betazoid-kvm-cluster-create#190mainbuildactioncompleted:SUCCESSJun11,201412:22:24AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListeneronCompletedINFO:Completed.Build:betazoid-kvm-cluster-create#190Cause:nullJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:StartedDownloadmetadataJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:FinishedDownloadmetadata.0msgetConfigPage-/pyenv_wrapper/configJun11,201412:35:45AMhudson.model.RunexecuteINFO:betazoid#185abortedjava.lang.InterruptedException atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(UnknownSource) atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(UnknownSource) atjava.util.concurrent.ArrayBlockingQueue.take(UnknownSource) atcom.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:148) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) athudson.model.Build$BuildExecution.build(Build.java:199) athudson.model.Build$BuildExecution.doRun(Build.java:160) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) athudson.model.Run.execute(Run.java:1676) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)WDis/usr/share/tomcat6/.jenkins/jobs/betazoid/workspaceJun11,201412:35:45AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListener
INFO:Completed.Build:betazoid#185Cause:null
{quote}
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-23398) Phase stopped on 'Notifying upstream projects of job completion'
Roman G
updated JENKINS-23398
Phase stopped on Notifying upstream projects of job completion
Change By:
Roman G
(11/Jun/14 8:01 AM)
Description:
Multijobcannot
Multijobcannot
receivemessage
fromphase
fromphase
jobandwaitinloopMultijobiswaitingphase{quote}Startingbuildjobxxx{quote}Phasejobsetgeenballbutcannotcomplete/notifymultijob{quote}ArchivingartifactsDescriptionset:xxxNotifyingupstreamprojectsofjobcompletion{quote}logfromcatalina.outisclearuntilabortjobandshowsexceptiononlyafterit{quote}INFO:betazoid-kvm-cluster-create#190mainbuildactioncompleted:SUCCESSJun11,201412:22:24AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListeneronCompletedINFO:Completed.Build:betazoid-kvm-cluster-create#190Cause:nullJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:StartedDownloadmetadataJun11,201412:26:49AMhudson.model.AsyncPeriodicWork$1runINFO:FinishedDownloadmetadata.0msgetConfigPage-/pyenv_wrapper/configJun11,201412:35:45AMhudson.model.RunexecuteINFO:betazoid#185abortedjava.lang.InterruptedException atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(UnknownSource) atjava.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(UnknownSource) atjava.util.concurrent.ArrayBlockingQueue.take(UnknownSource) atcom.tikal.jenkins.plugins.multijob.MultiJobBuilder.perform(MultiJobBuilder.java:148) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) athudson.model.Build$BuildExecution.build(Build.java:199) athudson.model.Build$BuildExecution.doRun(Build.java:160) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) athudson.model.Run.execute(Run.java:1676) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)WDis/usr/share/tomcat6/.jenkins/jobs/betazoid/workspaceJun11,201412:35:45AMcom.sonyericsson.hudson.plugins.gerrit.trigger.gerritnotifier.ToGerritRunListenerINFO:Completed.Build:betazoid#185Cause:null{quote}
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-14603) Drag jobs in the config from phase to phase
Roman G commented on JENKINS-14603 Drag jobs in the config from phase to phase I found workaround - using Oracle java instead of OpenJDK in slaves 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] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
Roman G commented on JENKINS-20243 Upgrade to Jenkins GIT plugin 2.0 from 1.5 brakes Gerrit triggered builds I observe the stacktrace but in same time correct hash was checkout from gerrit I checked sources and see that it happens getFirstParent function. Looks like this functionality touch only changelog but not. I could assume that it happens because gerrit patchsets are placed in detached head and parent commit cannot be simple found 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] [git] (JENKINS-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
Roman G edited a comment on JENKINS-20243 Upgrade to Jenkins GIT plugin 2.0 from 1.5 brakes Gerrit triggered builds I observe the stacktrace but in same time correct hash was checkout from gerrit I checked sources and see that it happens getFirstParent function. Looks like this functionality touch only changelog but not code checkout. I could assume that it happens because gerrit patchsets are placed in detached head and parent commit cannot be simple found 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] [extended-choice-parameter] (JENKINS-17518) When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter
Roman G commented on JENKINS-17518 When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter I don't see this fix in plugin in main Jenkins repo. Any issues with it? 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] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Roman G commented on JENKINS-18736 PAM authertication over NIS server does not work I confirm - I execute jenkins as root 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] [pam-auth] (JENKINS-18736) PAM authertication over NIS server does not work
Roman G edited a comment on JENKINS-18736 PAM authertication over NIS server does not work Hi, I got success with PAM/SSS and sshd on RHEL 6.2/JRE 1.7u45/Winston I suggest to dig secure /var/log/secure for understanding possible issues of java and PAM 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] [build-flow] (JENKINS-17155) Allow users to run a specific combination axis in matrix builds
Roman G commented on JENKINS-17155 Allow users to run a specific combination axis in matrix builds I think matrix reload plugin could be used as workaround 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] (JENKINS-13820) please create possibility to automatically set order of execution of matrix subtasks based on previously tracked time
Roman G commented on JENKINS-13820 please create possibility to automatically set order of execution of matrix subtasks based on previously tracked time looks like plugin allows execution on only one slave node sequentially and doesn't allow parallel execution on few nodes 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
