[JIRA] (JENKINS-46067) Pipeline task scheduled on uninitialized node
Title: Message Title Ben Hines commented on JENKINS-46067 Re: Pipeline task scheduled on uninitialized node We are relatively updated now, and hit this again when restarting our agents. Jenkins 2.154 / Remoting 3.27. The node had just connected via JNLP. For us i think it would be pretty easy to reproduce if we made a task that continually restarts agents while a job is scheduled via pipeline to run on them. Cannot contact : hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from /:56650 failed. The channel is closing down or has closed down Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-38576) Long build parameters result in shell scripts crashing
Title: Message Title Ben Hines commented on JENKINS-38576 Re: Long build parameters result in shell scripts crashing Yes, the withEnv() wrapper works for fixing 'sh', but it does not work for scm steps such as git. You need to override the specific environment variable(s) which are too long. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-38576) Long build parameters result in shell scripts crashing
Title: Message Title Ben Hines commented on JENKINS-38576 Re: Long build parameters result in shell scripts crashing We ended up using the 'file parameter' workaround. However, due to a separate jenkins issue (file parameters don't work with pipeline currently), we are using this OTHER workaround to support that https://issues.jenkins-ci.org/browse/JENKINS-27413 https://bitbucket.org/janvrany/jenkins-27413-workaround-library Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-38576) Long build parameters result in shell scripts crashing
Title: Message Title Ben Hines commented on JENKINS-38576 Re: Long build parameters result in shell scripts crashing We encountered this as well. I bet Jenkins could detect parameters over a certain length and warn about this, at least, which would avoid the pain involved in tracking down the cryptic error message. (took us a while to figure out this was the problem Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-34021) NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140)
Title: Message Title Ben Hines commented on JENKINS-34021 Re: NPE: Failed to abort CpsFlowExecutiontask.DurableTaskStep$Execution.stop(DurableTaskStep.java:140) We are also experiencing this error log spam, i suspect after hard killing a job too, but i wasn't able to reproduce the error log spam using Antonio's test script and /kill on the job. Though that was on a different instance of Jenkins with some slightly different plugin versions. Tried both 2.3 and 2.4 of basic steps. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41612) Job DSL plugin does not function on Windows agents
Title: Message Title
Ben Hines created an issue
Jenkins / JENKINS-41612
Job DSL plugin does not function on Windows agents
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2017/Feb/01 1:09 AM
Priority:
Critical
Reporter:
Ben Hines
Latest version of the job dsl plugin fails on Windows, 100%. ERROR: invalid script name 'Z:\export\jenkins\workspace\test_generate_jenkins_jobs\dev\dev.dsl; script names may only contain letters, digits and underscores, but may not start with a digit The same exact job name works on Linux. The job-dsl plugin is presumably using the full pathname to the workspace to create the class which has a colon in it on windows. Our config looks like: {{ dsl/*.dsl false false false false false DELETE DELETE JENKINS_ROOT }}
Add Comment
[JIRA] (JENKINS-38291) Logstash fails to report buils to Elasticsearch 2 if a buildVariable contain dot in the name
Title: Message Title Ben Hines commented on JENKINS-38291 Re: Logstash fails to report buils to Elasticsearch 2 if a buildVariable contain dot in the name Duplicate of JENKINS-33633 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-33633) Change Key values to "_" vs "." as this breaks ES 2.0 and later
Title: Message Title Ben Hines commented on JENKINS-33633 Re: Change Key values to "_" vs "." as this breaks ES 2.0 and later Is this still a problem? I wanted to try out this plugin with the latest ELK. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39465) JNLP4 Agent preference is not saved
Title: Message Title Ben Hines commented on JENKINS-39465 Re: JNLP4 Agent preference is not saved Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39465) JNLP4 Agent preference is not saved
Title: Message Title Ben Hines updated an issue Jenkins / JENKINS-39465 JNLP4 Agent preference is not saved Change By: Ben Hines Environment: jenkins 2.28 / remoting 3 , centos 6 , java 1.8, tomcat 8.6 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39465) JNLP4 Agent preference is not saved
Title: Message Title Ben Hines created an issue Jenkins / JENKINS-39465 JNLP4 Agent preference is not saved Issue Type: Bug Assignee: Unassigned Components: remoting Created: 2016/Nov/03 2:41 AM Environment: jenkins 2.28 / remoting 3 centos 6 Priority: Minor Reporter: Ben Hines 1. Enable JNLP4 in the agent settings 2. Restart jenkins -> JNLP4 turns itself off I'd like to try out jnlp4 but it keeps turning itself off which is frustrating. Add Comment
[JIRA] (JENKINS-20913) [jar caching] - winp.x64.dll access conflicts
Title: Message Title Ben Hines commented on JENKINS-20913 Re: [jar caching] - winp.x64.dll access conflicts We are also seeing this error pretty often. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34188) jenkins.log noise: "script parameter ... is not an instance of Java.util.Map."
Title: Message Title Ben Hines commented on JENKINS-34188 Re: jenkins.log noise: "script parameter ... is not an instance of Java.util.Map." Could you do a release just to fix this? It's literally 90% of the logs for my entire jenkins server. (or maybe a log4j guru could provide a config to filter this spam) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-38418) Failed to load persisted workflow state (remote-loader)
Title: Message Title Ben Hines commented on JENKINS-38418 Re: Failed to load persisted workflow state (remote-loader) We are also seeing this issue on Jenkins 2.21 when using the remote loader. We're going to try not using remoteloader to workaround. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34386) NPE from ScriptApproval.hash
Title: Message Title Ben Hines commented on JENKINS-34386 Re: NPE from ScriptApproval.hash Figured out my issue – i had a varnish cache running in front of Jenkins, which was apparently caching something bad that was breaking the UI after i changed the version of the pipeline plugin. And causing the pipeline entry box not to display. This tells me that Jenkins might not sending the proper cache-control headers for one of the configuration page responses. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] [script-security-plugin] (JENKINS-34386) NPE from ScriptApproval.hash
Title: Message Title Ben Hines commented on JENKINS-34386 Re: NPE from ScriptApproval.hash Also noticed this error in the job configuration console: "NetworkError: 404 Not Found - http:///jenkins/$stapler/bound/5c424e6d-b6c6-4fa1-a20b-99c0516b8539/render" "NetworkError: 404 Not Found - http:///jenkins/$stapler/bound/0e1fffc7-0411-4784-bdea-de3e634962a1/render" The error on submit could possibly just be related to the failure of the GUI to draw the boxes with which to input the pipeline script. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [script-security-plugin] (JENKINS-34386) NPE from ScriptApproval.hash
Title: Message Title Ben Hines commented on JENKINS-34386 Re: NPE from ScriptApproval.hash Here's the crash in text form so it can be searched easier: Jun 10, 2016 5:09:39 PM org.apache.catalina.core.ApplicationContext log SEVERE: Error while serving http://.../jenkins/job/t4stestete/configSubmit java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:100) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:604) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:543) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:461) at org.apache.catalina.core.StandardHostValve.throwable(StandardHostValve.java:412) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:201) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:683) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.hash(ScriptApproval.java:364) at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.configuring(ScriptApproval.java:416) at org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition.(CpsFlowDefinition.java:70) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
[JIRA] [script-security-plugin] (JENKINS-34386) NPE from ScriptApproval.hash
Title: Message Title Ben Hines commented on JENKINS-34386 Re: NPE from ScriptApproval.hash I have this problem with 2.6+2.8. I even tried wiping ALL plugins and reinstalling my set of plugins from scratch using the update center. I also wiped the tomcat work and temp directories. Same error. There are no plugin load errors in the catalina.out. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines closed an issue as Not A Defect Jenkins / JENKINS-35195 Unable to run Blue Ocean within tomcat Change By: Ben Hines Status: Resolved Closed Assignee: Tom FENNELLY Ben Hines Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat Thanks , Adrian. Got it working! It seems maven not creating a blueocean-plugin.jpi for me, but this was because i had a couple failing tests. After fixing the tests and a minor build issue with my environment, it packaged installed the blueocean.hpi and put it in the local mvn repo. Indeed it would be nice if there were a nightly binary build set up somewhere (preferably to an update center, but raw downloads would be fine too) that we could test with, but i'd also like to get it building and deployed into a separate Jenkins instance so we can potentially contribute. I'll close this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines resolved as Not A Defect Jenkins / JENKINS-35195 Unable to run Blue Ocean within tomcat Change By: Ben Hines Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines commented on JENKINS-35195 Re: Unable to run Blue Ocean within tomcat I believe I installed all the dependent plugins. (until i did so, they would not load at all – and printed errors in catalina.out.) - jenkins/blue does not work 17:00:49 root@jenkins /var/lib/jenkins/plugins $ ls *.hpi *.jpi ace-editor.jpi git.jpi promoted-builds.jpi active-directory.jpi git-server.jpi publish-over-cifs.jpi ansicolor.jpi groovy.jpi rebuild.jpi antisamy-markup-formatter.jpi groovy-postbuild.jpi run-condition.jpi ant.jpi handlebars.jpi rundeck.jpi blueocean-commons.hpi icon-shim.jpi scm-api.jpi blueocean-dashboard.hpi jackson2-api.jpi scriptler.jpi blueocean-rest.hpi javadoc.jpi script-security.jpi blueocean-web.hpi jenkinswalldisplay.jpi setenv.jpi bootstrap.hpi jquery-detached.jpi shelve-project-plugin.jpi branch-api.jpi jquery.jpi sse-gateway.jpi build-flow-plugin.jpi junit.jpi ssh-credentials.jpi buildgraph-view.jpi ldap.jpi ssh-slaves.jpi build-history-metrics-plugin.jpi mailer.jpi storable-configs-plugin.jpi build-timeout.jpi mapdb-api.jpi structs.jpi cloudbees-folder.jpi matrix-auth.jpi subversion.jpi conditional-buildstep.jpi matrix-project.jpi timestamper.jpi console-column-plugin.jpi maven-plugin.jpi token-macro.jpi cors-filter.jpi metrics.jpi translation.jpi credentials.jpi momentjs.jpi uno-choice.jpi cvs.jpi msbuild.jpi validating-string-parameter.jpi dropdown-viewstabbar-plugin.jpi nodelabelparameter.jpi variant.jpi durable-task.jpi pam-auth.jpi versionnumber.jpi dynamicparameter.jpi parameterized-trigger.jpi windows-slaves.jpi email-ext.jpi perforce.jpi workflow-aggregator.jpi envinject.jpi pipeline-build-step.jpi workflow-api.jpi extended-choice-parameter.jpi pipeline-input-step.jpi workflow-basic-steps.jpi extensible-choice-parameter.jpi pipeline-rest-api.jpi workflow-cps-global-lib.jpi external-monitor-job.jpi pipeline-stage-step.jpi workflow-cps.jpi favorite.hpi pipeline-stage-view.jpi workflow-durable-task-step.jpi filesystem-list-parameter-plugin.jpi plain-credentials.jpi workflow-job.jpi git-client.jpi plot.jpi workflow-multibranch.jpi github-api.jpi postbuildscript.jpi workflow-scm-step.jpi github-branch-source.jpi postbuild-task.jpi workflow-step-api.jpi github.jpi powershell.jpi workflow-support.jpi github-organization-folder.jpi PrioritySorter.jpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [blueocean-plugin] (JENKINS-35195) Unable to run Blue Ocean within tomcat
Title: Message Title Ben Hines created an issue Jenkins / JENKINS-35195 Unable to run Blue Ocean within tomcat Issue Type: Bug Assignee: Tom FENNELLY Components: blueocean-plugin Created: 2016/May/27 9:54 PM Priority: Major Reporter: Ben Hines I built the 4 blueocean plugins and copied them to my jenkins (2.6) plugin dir, and i see them in the plugin manager, but i am unable to hit the /jenkins/blue endpoint. It just returns 404. They work fine when run via the hpi:run method. I'm using Jenkins running within Tomcat 7.0.54. There are no errors in catalina.out. Is there anything I need to do to set this up properly? Add Comment
[JIRA] [active-choices-plugin] (JENKINS-34188) jenkins.log noise: "script parameter ... is not an instance of Java.util.Map."
Title: Message Title Ben Hines commented on JENKINS-34188 Re: jenkins.log noise: "script parameter ... is not an instance of Java.util.Map." We also have this issue, it's super annoying. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Ben Hines updated an issue Jenkins / JENKINS-23271 Intermittent Invalid Object ID in remoting module Change By: Ben Hines Environment: 1.544.2, 1.563 - Windows XP or Linux Master, various slaves Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Ben Hines commented on JENKINS-27223 Clicking Login when you have 30+ slaves defaults you to the bottom of the web page We have hundreds of slaves, and this is super annoying. 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] [rundeck] (JENKINS-21802) Rundeck plugin crashes jenkins on startup
Ben Hines commented on JENKINS-21802 Rundeck plugin crashes jenkins on startup Is this plugin being maintained? Crashing jenkins on a clean centos with the standard openjdk is a pretty big deal. 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-14550) Checksum mismatch while updating with Subversion Plugin 1.42
Ben Hines commented on JENKINS-14550 Checksum mismatch while updating with Subversion Plugin 1.42 this still occurs with 1.44 /jenkins 1.498 btw. Very frustrating 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
