[JIRA] [azure-slave-plugin] (JENKINS-26248) Impossible to find working Management Service Certificate in Windows Azure Pack
Markus Strand commented on JENKINS-26248 Impossible to find working Management Service Certificate in Windows Azure Pack The plugin is accepting ASCII certificates and when we are able to find are binary files. 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] [azure-slave-plugin] (JENKINS-26248) Impossible to find working Management Service Certificate in Windows Azure Pack
Markus Strand created JENKINS-26248 Impossible to find working Management Service Certificate in Windows Azure Pack Issue Type: Bug Assignee: Unassigned Components: azure-slave-plugin Created: 30/Dec/14 2:10 PM Description: How to find Management Service Certificate in Windows Azure Pack? The help goes to Azure, but if the user has a WAP installation and would like to use that as his Azure cloud it is impossible to find the certificate. Environment: Windows servers and Windows Azure Pack Project: Jenkins Priority: Minor Reporter: Markus Strand 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] [build-failure-analyzer-plugin] (JENKINS-25723) Add the ability to rescan some specific builds
Markus Strand created JENKINS-25723 Add the ability to rescan some specific builds Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 21/Nov/14 6:21 AM Description: At the moment there are options to resan build: "Scan non-scanned builds" option scans only non-scanned builds. "Scan/Rescan all the builds" option scans all the builds including scanned and non-scanned builds. But there is no way to rescan a specific build. If the build history is very long the scan/rescan all wastes time and resources if only build #2345 would be interesting to rescan. Project: Jenkins Priority: Minor Reporter: Markus Strand 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] [build-failure-analyzer] (JENKINS-24925) When using BFA with MongoDB the causes gives the oops page and a traceback.
Markus Strand commented on JENKINS-24925 When using BFA with MongoDB the causes gives the oops page and a traceback. The new version of the plugin fixed the bug. Thank you very much. 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] [build-failure-analyzer] (JENKINS-24925) When using BFA with MongoDB the causes gives the oops page and a traceback.
Markus Strand resolved JENKINS-24925 as Fixed When using BFA with MongoDB the causes gives the oops page and a traceback. Version 1.10.2 fixed the issue Change By: Markus Strand (09/Oct/14 7:25 AM) 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 -- 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] [build-failure-analyzer] (JENKINS-24925) When using BFA with MongoDB the causes gives the oops page and a traceback.
Markus Strand commented on JENKINS-24925 When using BFA with MongoDB the causes gives the oops page and a traceback. Could you check where the release it pending? And in the meantime, could you send me a .hpi file as I can't get my environment to successfully compile the sources. 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] [build-failure-analyzer] (JENKINS-24925) When using BFA with MongoDB the causes gives the oops page and a traceback.
Markus Strand commented on JENKINS-24925 When using BFA with MongoDB the causes gives the oops page and a traceback. I don't see any new versions in the update center nor the repositories 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] [build-failure-analyzer] (JENKINS-24925) When using BFA with MongoDB the causes gives the oops page and a traceback.
Markus Strand created JENKINS-24925 When using BFA with MongoDB the causes gives the oops page and a traceback. Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer Created: 30/Sep/14 11:48 AM Description: When using BFA with MongoDB the causes gives the "oops page" and a traceback. javax.servlet.ServletException: com.mongodb.MongoException$Network: can't call something : salmongo01.rnd.nokia.com/10.220.197.139:27017/BuildFailureAnalyzer at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at org.jenkinsci.plugins.suppress_stack_trace.SuppressionFilter.doFilter(SuppressionFilter.java:34) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.jenkins.ha.HAHealthCheckFilter.doFilter(HAHealthCheckFilter.java:52) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling Logging was essential, I had PrioritySorter.Queue.Items and PrioritySorter.Queue.sorter logging with "ALL" lOGS showed that priority sorter was applying priority based on first JobGroup (id=0) - this one was NOT configured to use BuildParameterStrategy - only second JobGroup(id=1) was, and didn't match the view. So By setting the JobGroups and the vieWs and the jobs all in sync solved the issue. Without the finest level of logs it was really hard to understand what happened. 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] [core] (JENKINS-24737) updateCenter fails to restart Jenkins
Markus Strand closed JENKINS-24737 as Duplicate updateCenter fails to restart Jenkins Works with latest jenkins.exe Change By: Markus Strand (18/Sep/14 10:32 PM) Status: Resolved Closed 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand closed JENKINS-22294 as Fixed Priority is not used in the scheduling Nicolas De Loof (CloudBees Support) helped me to figure out the correct Configuration settings. It was not that obvious how to configure JobGroup with BuildParameterStrategy. Change By: Markus Strand (18/Sep/14 10:58 PM) Status: Open Closed 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 -- 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] [core] (JENKINS-24737) updateCenter fails to restart Jenkins
Markus Strand created JENKINS-24737 updateCenter fails to restart Jenkins Issue Type: Bug Assignee: Unassigned Components: core Created: 17/Sep/14 4:55 AM Description: When the "Restart Jenkins when installation is complete and no jobs are running" is checked and anonymous has no rights to the master the log says: " Sep 17, 2014 7:41:47 AM jenkins.model.Jenkins$24 run INFO: Restart in 10 seconds Sep 17, 2014 7:41:57 AM jenkins.model.Jenkins$24 run SEVERE: Restarting VM as requested by anonymous " but the master stays in restart forever. A manual login to the master and a "%JENKINS_HOME%\jenkins.exe restart" is needed. Environment: window 2012r2 Jenkins 1.565.2 Project: Jenkins Priority: Major Reporter: Markus Strand 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling Interesting. the Problem is not with static priorities, but with the priority parameter. I start the builds in "reverse priority order". The build queue in the job page shows them sorted in priority order: pending #27 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=6 pending #26 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=4 pending #25 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=3 pending #24 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=2 pending #23 cancel this build (pending—Waiting for next available executor on foobar) BuildPriority=1 In progress Console Output #22 Aug 25, 2014 7:56:28 AM cancel The queue is all with the same priority: Aug 25, 2014 7:57:27 AM FINER PrioritySorter.Queue.Sorter Queue: -- Item Id Job Name Priority Weight -- 5921 testPriorityN 5 5.0 5922 testPriorityN 5 5.0 5923 testPriorityN 5 5.0 5924 testPriorityN 5 5.0 -- Aug 25, 2014 7:57:29 AM FINE PrioritySorter.Queue.Sorter Sorted 4 Buildable Items with Min Weight 5 and Max Weight 5 Aug 25, 2014 7:57:29 AM FINER PrioritySorter.Queue.Sorter Queue: -- Item Id Job Name Priority Weight -- 5921 testPriorityN 5 5.0 5922 testPriorityN 5 5.0 5923 testPriorityN 5 5.0 5924 testPriorityN 5 5.0 -- Aug 25, 2014 7:57:29 AM FINE PrioritySorter.Queue.Items Starting: Id: 5921, JobName: testPriorityN, jobGroupId: 0, reason: , priority: 5, weight: 5.0, status: BUILDABLE Aug 25, 2014 7:57:29 AM FINE PrioritySorter.Queue.Sorter Sorted 3 Buildable Items with Min Weight 5 and Max Weight 5 Aug 25, 2014 7:57:29 AM FINER PrioritySorter.Queue.Sorter Queue: -- Item Id Job Name Priority Weight -- 5922 testPriorityN 5 5.0 5923 testPriorityN 5 5.0 5924 testPriorityN 5 5.0 -- Aug 25, 2014 7:57:32 AM FINE PrioritySorter.Queue.Sorter Sorted 3 Buildable Items with Min Weight 5 and Max Weight 5 Aug 25, 2014 7:57:32 AM FINER PrioritySorter.Queue.Sorter 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] [scm-sync-configuration] (JENKINS-24339) SCM sync Configuration plugin seems to wrongly expect all files to be under JENKINS_HOME
Markus Strand
created JENKINS-24339
SCM sync Configuration plugin seems to wrongly expect all files to be under JENKINS_HOME
Issue Type:
Bug
Assignee:
Frédéric Camblor
Components:
scm-sync-configuration
Created:
20/Aug/14 5:47 AM
Description:
SCM sync Configuration plugin seems to expect all files to be under JENKINS_HOME and does not take into account that the "Build Record Root Directory" can be set in config.xml
Below Build Record Root Directory is E:\build_e\njen\jobs\${ITEM_FULLNAME}\builds and JENKINS_HOME is C:\APPS\njen.
And the error in Jenkins.err.log is :
java.lang.IllegalArgumentException: Err ! File E:\build_e\njen\jobs\admin_check_memory\builds\2014-08-19_14-25-09\build.xml seems not to reside in C:\APPS\njen !
at hudson.plugins.scm_sync_configuration.JenkinsFilesHelper.buildPathRelativeToHudsonRoot(JenkinsFilesHelper.java:12)
at hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matches(PatternsEntityMatcher.java:25)
at hudson.plugins.scm_sync_configuration.strategies.AbstractScmSyncStrategy.isSaveableApplicable(AbstractScmSyncStrategy.java:53)
at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getStrategyForSaveable(ScmSyncConfigurationPlugin.java:279)
at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationSaveableListener.onChange(ScmSyncConfigurationSaveableListener.java:22)
at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78)
at org.jvnet.hudson.plugins.DownstreamBuildViewRunListener.save(DownstreamBuildViewRunListener.java:83)
at org.jvnet.hudson.plugins.DownstreamBuildViewRunListener.onCompleted(DownstreamBuildViewRunListener.java:73)
at org.jvnet.hudson.plugins.DownstreamBuildViewRunListener.onCompleted(DownstreamBuildViewRunListener.java:45)
at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199)
at hudson.model.Run.execute(Run.java:1715)
at hudson.model.Build.run(Build.java:113)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)
Environment:
WindowsServer2012R2
Project:
Jenkins
Priority:
Major
Reporter:
Markus Strand
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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling I don't think the Throttle plugin or not allowing parallel executioin would work for me. I have 100 executors that can execute my build and I always have 50 jobs in queue and I want to somehow say "run this job in next possible slot". Or always run these jobs before those jobs. 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] [recipe] (JENKINS-23696) When exporting a job recipe with a NodeParameterDefinition the ignoreOfflineNodes is not handled correctly
Markus Strand created JENKINS-23696 When exporting a job recipe with a NodeParameterDefinition the ignoreOfflineNodes is not handled correctly Issue Type: Bug Assignee: Unassigned Components: recipe Created: 07/Jul/14 9:33 AM Description: When exporting a recipe with a NodeParameterDefinition the ignoreOfflineNodes is not exported or imported correctly when set to ignore offline slaves. Environment: Jenkins LTS 1.509.3 and 1.532.1 enterprise on windows2012R2 server and Windows7. recipe 1.2 and NodeLabel+Parameter+Plugin 1.5.1 Project: Jenkins Priority: Major Reporter: Markus Strand 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling No that is not the problem in this case. I have parallel execution allowed. I have only one executor that is able to execute the job. I also tested with two jobs running on the same executor, one with high and one with low priority. Both are equally executed. 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand commented on JENKINS-22294 Priority is not used in the scheduling I have two jobs test_priority_high (priority: 1) and test_priority_low (priority: 5) both do "sleep 70" and build periodically (* * * * *) which means that there is always one of each in the queue. Both jobs are forced to running on the same executor. I would expect that only the test_priority_high would be executed as it has higher priority and there is always one in the queue when the executor is free. Not the jobs are run in the order in which they are started. This is what the log says (started with FINE but switched to FINER): New Item: Id: 13626, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: WAITING Mar 27, 2014 7:25:51 AM FINE PrioritySorter.Queue.Items New Item: Id: 13627, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: WAITING Mar 27, 2014 7:25:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13626, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:25:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13627, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:26:01 AM FINE PrioritySorter.Queue.Items Starting: Id: 13626, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:26:51 AM FINE PrioritySorter.Queue.Items New Item: Id: 13628, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: WAITING Mar 27, 2014 7:26:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13628, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:27:16 AM FINE PrioritySorter.Queue.Items Starting: Id: 13627, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:27:51 AM FINE PrioritySorter.Queue.Items New Item: Id: 13629, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: WAITING Mar 27, 2014 7:27:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13629, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:28:26 AM FINE PrioritySorter.Queue.Items Starting: Id: 13628, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:28:51 AM FINER PrioritySorter.Queue.Items New Item: Id: 13630, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: WAITING Using priority taken directly from the Job Mar 27, 2014 7:28:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13630, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:29:39 AM FINE PrioritySorter.Queue.Items Starting: Id: 13629, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:29:51 AM FINER PrioritySorter.Queue.Items New Item: Id: 13631, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: WAITING Using priority taken directly from the Job Mar 27, 2014 7:29:51 AM FINE PrioritySorter.Queue.Items Buildable: Id: 13631, JobName: test_priority_low, jobGroupId: -1, reason: , priority: 5, weight: 5.0, status: BUILDABLE Mar 27, 2014 7:30:49 AM FINE PrioritySorter.Queue.Items Starting: Id: 13630, JobName: test_priority_high, jobGroupId: -1, reason: , priority: 1, weight: 1.0, status: BUILDABLE Mar 27, 2014 7:30:51 AM FINER PrioritySorter.Queue.Items 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] [prioritysorter] (JENKINS-22294) Priority is not used in the scheduling
Markus Strand created JENKINS-22294 Priority is not used in the scheduling Issue Type: Bug Affects Versions: current Assignee: bklarson Components: prioritysorter Created: 21/Mar/14 9:15 AM Description: When using build paramater set on the main config (http://master:8080/advanced-build-queue/?) "BuildPriority" and in the job set it in the job config the same parameter When running the build with parameteres the job is still executed in the starting order even when the priority goes from 5,4,3,2,1 The build queue shows them in right order. It is the execution that happens in wrong order Environment: Windows2012Server Jenkins LTS 1.532 Java7 Project: Jenkins Priority: Major Reporter: Markus Strand 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] [recipe] (JENKINS-22241) Recipe export does not properly quote non-ASCII characters in the job description field
Markus Strand created JENKINS-22241 Recipe export does not properly quote non-ASCII characters in the job description field Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: recipe Created: 18/Mar/14 11:35 AM Description: The job description field can have any HTML text. eg that looks like the The export works fine, but the import of the recipe fails with " Exception: Invalid byte 1 of 1-byte UTF-8 sequence. Stacktrace: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence. at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(Unknown Source) at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(Unknown Source) ... " Project: Jenkins Priority: Major Reporter: Markus Strand 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] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
Markus Strand commented on JENKINS-11219 Add the option to run the script after all the sub elements of a matrix project build have finished Also the env inject plugin works strangely when the post build script plugin is used in matrix context. Could be a good test case for acceptance testing. 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] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
Markus Strand commented on JENKINS-11219 Add the option to run the script after all the sub elements of a matrix project build have finished Now with version 0.12 the execution happens optionally on the matrix configurations, but there is no way to not run it on the head. I would agree with the requirement that it should be optional to: 1) Run a script at the end of each element of a matrix build. This is the current functionality. 2) Run a script at the end of a entire matrix build (ie. after all matrix elements have built). 3) A combination of 1 and 2. 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] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
Markus Strand commented on JENKINS-11219 Add the option to run the script after all the sub elements of a matrix project build have finished To me it looks like the PostBuildScript execution happens only on the entire matrix build and not at all for the elements. 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-16637) problems exposing P4CLIENT and P4PASSWD to env
Markus Strand created JENKINS-16637 problems exposing P4CLIENT and P4PASSWD to env Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 05/Feb/13 9:21 AM Description: If the environment variable is assigned a value before the Jenkins slave starts the value is not changed by the plugin. The P4CLIENT problem is visible, when a system level P4CLIENT is defined and the slave is run as a service as a user (MYDOMAIN\BUILDUSER) not as SYSTEM. If the build now uses this slave, perforce plugin cannot override P4CLIENT variable. Environment: Windows Project: Jenkins Priority: Major Reporter: Markus Strand 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-16313) Can't restart Jenkins if downstream jobs are used
Markus Strand created JENKINS-16313 Cant restart Jenkins if downstream jobs are used Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Jan/13 9:32 AM Description: With the safeRestart option Jenkins will go to shutdown mode and will not trigger new builds. Jobs depending on downstream jobs (which will not be triggered once Jenkins is in shutdown mode) will never end. Builds will never finish if the downstream jobs can't start and Jenkins will never restart... Best option might be to let downstream builds to be triggered in shutdown mode but not to start new upstream builds. Project: Jenkins Priority: Major Reporter: Markus Strand 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
[JIRA] (JENKINS-15904) Perforce plugin issues wrong error message when exception occurs on remote end
Markus Strand commented on JENKINS-15904 Perforce plugin issues wrong error message when exception occurs on remote end Our engineers are trying to isolate from our private branch the changes needed to show the actual exception. It basically catches the possible errors in calling the command. 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
[JIRA] (JENKINS-15904) Perforce plugin issues wrong error message when it can't start cmd.exe to run p4.exe
Markus Strand
commented on JENKINS-15904
Perforce plugin issues wrong error message when it cant start cmd.exe to run p4.exe
The error handling completely hides certain types of errors, and just says 'No output for...'
src\main\java\com\tek42\perforce\parse\AbstractPerforceTemplate.java:
throw new PerforceException("No output for: " + debugCmd);
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
[JIRA] (JENKINS-15904) Perforce plugin issues wrong error message when it can't start cmd.exe to run p4.exe
Markus Strand created JENKINS-15904 Perforce plugin issues wrong error message when it cant start cmd.exe to run p4.exe Issue Type: Bug Assignee: Unassigned Components: perforce Created: 23/Nov/12 5:41 AM Description: When there is an error in the global configuration that injects broken environment variables (blank name for the variable) the Perforce-plugin fails with: Started by user testuser EnvInject - Loading node environment variables. Building remotely on testslave in workspace E:\build_e\workspace\Test_Component Using remote perforce client: testclient-12345678 Test_Component $ C:\apps\perforce\p4.exe workspace -o -S //test/test_stream testclient-12345678 Caught exception communicating with perforce. No output for: C:\apps\perforce\p4.exe workspace -o -S //test/test_stream testclient-12345678 com.tek42.perforce.PerforceException: No output for: C:\apps\perforce\p4.exe workspace -o -S //test/test_stream testclient-12345678 at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:384) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1528) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1489) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:795) at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468) at hudson.model.Run.run(Run.java:1408) at hudson.model.Build.run(Build.java:110) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) ERROR: Unable to communicate with perforce. No output for: C:\apps\perforce\p4.exe workspace -o -S //test/test_stream testclient-12345678 Finished: FAILURE The correct error would be something like, can't "run the command". Because the actual error is something like: Caused by: java.io.IOException: Cannot run program "cmd.exe" (in directory "E:\build_e\workspace\Test_Component"): CreateProcess error=87, The parameter is incorrect at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) Environment: Windows Project: Jenkins Priority: Major Reporter: Markus Strand 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
[JIRA] (JENKINS-15561) Downstream buildview does not show multiple instancies of a same job
Markus Strand created JENKINS-15561 Downstream buildview does not show multiple instancies of a same job Issue Type: Bug Assignee: shinodkm Components: downstream-buildview Created: 18/Oct/12 7:03 AM Description: If build A#1 triggers build B#1 on a buildstep and then build B#2 on another buildstep, only the latter B#2 will be shown on the downstream buildview. Project: Jenkins Priority: Major Reporter: Markus Strand 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
[JIRA] (JENKINS-15378) TokenMacro.expandAll fails
Markus Strand created JENKINS-15378 TokenMacro.expandAll fails Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: token-macro Created: 02/Oct/12 7:06 AM Description: I get a stacktrace: 15:17:13 FATAL: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/AbstractBuild;Lhudson/model/TaskListener;Ljava/lang/String;)Ljava/lang/String; 15:17:13 java.lang.NoSuchMethodError: org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(Lhudson/model/AbstractBuild;Lhudson/model/TaskListener;Ljava/lang/String;)Ljava/lang/String; 15:17:13 at org.jvnet.jenkins.plugins.nodelabelparameter.parameterizedtrigger.NodeLabelBuildParameter.getAction(NodeLabelBuildParameter.java:38) 15:17:13 at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.getBaseActions(BuildTriggerConfig.java:170) 15:17:13 at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform2(BuildTriggerConfig.java:240) 15:17:13 at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform2(BlockableBuildTriggerConfig.java:56) 15:17:13 at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:96) 15:17:13 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 15:17:13 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) 15:17:13 at hudson.model.Build$BuildExecution.build(Build.java:199) 15:17:13 at hudson.model.Build$BuildExecution.doRun(Build.java:160) 15:17:13 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) 15:17:13 at hudson.model.Run.execute(Run.java:1502) 15:17:13 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 15:17:13 at hudson.model.ResourceController.execute(ResourceController.java:88) 15:17:13 at hudson.model.Executor.run(Executor.java:236) Environment: Jenkins core 1.482 and token-macro 1.5.1 and nodelabelparameter 1.2.1 OS Name: Microsoft Windows 7 Enterprise And OS Name: Microsoft Windows Server 2008 R2 Standard Project: Jenkins Priority: Major Reporter: Markus Strand 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
[JIRA] (JENKINS-15066) Long wait between last build step and first post build step
Markus Strand updated JENKINS-15066 Long wait between last build step and first post build step jstack from a jammed build Change By: Markus Strand (17/Sep/12 6:56 AM) Attachment: jstack_jammed.log 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
[JIRA] (JENKINS-15066) Long wait between last build step and first post build step
Markus Strand edited a comment on JENKINS-15066 Long wait between last build step and first post build step jstack from a jammed build It is the sawnwp110_image1 slave that is running the jammed job. 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
[JIRA] (JENKINS-15066) Long wait between last build step and first post build step
Markus Strand created JENKINS-15066 Long wait between last build step and first post build step Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Sep/12 7:46 AM Description: Were are struggling with our builds that are occasionally jamming in between the last build step and first post-build action. The more builds we are running in parallel the more likely we'll face this issue. We are running Jenkins 1.454 and "execute concurrent builds" option to run multiple instances of the same job. Our master is Windows server 2008 and so are the slaves. All the builds are happening on the slaves, master is just dispatching the jobs. Slaves are virtual machines. We are not running out of memory. Any help is appreciated. For example what log recorders we could use to debug this issue? Jenkins default log doesn't provide any further info and neither does the console log. Project: Jenkins Priority: Major Reporter: Markus Strand 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
