[JIRA] [core] (JENKINS-24614) "unknown format type" on console output
Nir Bar commented on JENKINS-24614 "unknown format type" on console output This translation is correct. 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] [show-build-parameters] (JENKINS-24698) ShowParametersBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionabl
Per Arnold Blaasmo created JENKINS-24698 ShowParametersBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionabl Issue Type: Bug Assignee: Peter Hayes Components: show-build-parameters Created: 14/Sep/14 9:51 AM Description: These exceptions are being written to the log file at regular intervalls. According to JENKINS-24458 it might have to do with some REST API call done by the plugin. WARNING: null org.kohsuke.stapler.export.NotExportableException: class jenkins.plugins.show_build_parameter s.ShowParametersBuildAction doesn't have @ExportedBean so cannot write hudson.model.Actionabl e.actions at org.kohsuke.stapler.export.Model.(Model.java:73) at org.kohsuke.stapler.export.ModelBuilder.get(ModelBuilder.java:51) at org.kohsuke.stapler.export.Property.writeValue(Property.java:231) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Property.writeValue(Property.java:241) at org.kohsuke.stapler.export.Property.writeValue(Property.java:187) at org.kohsuke.stapler.export.Property.writeValue(Property.java:139) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:190) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:185) at org.kohsuke.stapler.export.Model.writeTo(Model.java:157) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doJson(Api.java:205) at sun.reflect.GeneratedMethodAccessor353.invoke(Unknown Source) 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:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) : Environment: Jenkins 1.579 Project: Jenkins Priority: Major Reporter: Per Arnold Blaasmo
[JIRA] [core] (JENKINS-5253) artifacts archiving: add option for treating patterns in case insensitive way
Daniel Beck commented on JENKINS-5253 artifacts archiving: add option for treating patterns in case insensitive way Dominique Brice: This is about artifact archiving, a post-build step. You specify an Ant-style pattern like **/*.hpi and apparently that's case sensitive and no way to make it case insensitive. 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-20035) see "exclusively" and "possible assigned jobs (by tags)" in node view
Daniel Beck commented on JENKINS-20035 see "exclusively" and "possible assigned jobs (by tags)" in node view I think that page is quite close, except that the report is about the node's index page (/computer/foo), not a label. May be sufficient to add a node's self label to that page (it's missing currently, only explicitly assigned labels are shown). 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] [gradle] (JENKINS-24682) Gradle Wrapper not working when gradle version was previously selected
Mario Mohr updated JENKINS-24682 Gradle Wrapper not working when gradle version was previously selected Change By: Mario Mohr (14/Sep/14 11:03 AM) Attachment: jenkins-24682.zip Attachment: config-1.JPG Attachment: config-2.JPG 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-24614) "unknown format type" on console output
SCM/JIRA link daemon commented on JENKINS-24614 "unknown format type" on console output Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/Run/console_he.properties http://jenkins-ci.org/commit/jenkins/07fd5fa45d4b818fc11de97ce99ab6b3423aca85 Log: [FIXED JENKINS-24614] Broken format string in Hebrew console output 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-24614) "unknown format type" on console output
SCM/JIRA link daemon resolved JENKINS-24614 as Fixed "unknown format type" on console output Change By: SCM/JIRA link daemon (14/Sep/14 11:06 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] [gradle] (JENKINS-24682) Gradle Wrapper not working when gradle version was previously selected
Mario Mohr commented on JENKINS-24682 Gradle Wrapper not working when gradle version was previously selected No, I'm not manipulating the build programmatically. I switched a build from a fixed version to gradlew like shown in the two screenshots attached. After the change, the gradleName property is still set in the config file. The current logic in Gradle.java is still trying to use the tool version, although it should use the wrapper and the gradle version that comes with it. See the attached jenkins-24682.zip file for a minimal example that fails with the current code and is fixed in my pull request. 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] [gradle] (JENKINS-24682) Gradle Wrapper not working when gradle version was previously selected
Mario Mohr commented on JENKINS-24682 Gradle Wrapper not working when gradle version was previously selected BTW: A workaround with the current release is to to set the gradle version to default before switching to gradlew, but this is not really intuitive. 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] [parameterized-trigger] (JENKINS-14108) Multiple parameterized upstreams with joined in one "blocked while.." job result in multiple executions rather one only
ikedam resolved JENKINS-14108 as Won't Fix Multiple parameterized upstreams with joined in one "blocked while.." job result in multiple executions rather one only It's the current designated behavior of Jenkins. Change By: ikedam (14/Sep/14 2:02 PM) Status: Open Resolved Resolution: Won't Fix 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] [parameterized-trigger] (JENKINS-14108) Multiple parameterized upstreams with joined in one "blocked while.." job result in multiple executions rather one only
Daniel Beck commented on JENKINS-14108 Multiple parameterized upstreams with joined in one "blocked while.." job result in multiple executions rather one only One possible solution would be checking out the orchestration plugins, e.g. Build Flow, Workflow (still in development), ... but that's something to discuss on the jenkinsci-users list, and not in Jira. 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] [docker-build-step] (JENKINS-24699) Create image build step fails with Jenkins prior to 1.553
Harald Albers created JENKINS-24699 Create image build step fails with Jenkins prior to 1.553 Issue Type: Bug Assignee: vjuranek Components: docker-build-step Created: 14/Sep/14 3:24 PM Description: The Create image command fails on Jenkins prior to 1.553: java.lang.NoSuchMethodError: org.apache.commons.io.FileUtils.getTempDirectoryPath()Ljava/lang/String; This can easily be reproduced if you start Jenkins from the docker build step plugin sources with mvn hpi:run, then create and execute a job with a Create image build step. docker-java relies on FileUtil.getTempDirectoryPath(), which was introduced in commons-io 2.0. The first Jenkins version to ship with commons-io 2.4 is 1.553 (commit). Resolution: any of upgrade core dependency to 1.553 upgrade core dependency to 1.554.1 document the minimum Jenkins version required to run the Create image command Project: Jenkins Priority: Minor Reporter: Harald Albers 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] [docker-build-step] (JENKINS-24414) Port bindings are ignored with Docker v1.2
Harald Albers commented on JENKINS-24414 Port bindings are ignored with Docker v1.2 created PR 13 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] [docker-build-step] (JENKINS-24699) Create image build step fails with Jenkins prior to 1.553
SCM/JIRA link daemon resolved JENKINS-24699 as Fixed Create image build step fails with Jenkins prior to 1.553 Change By: SCM/JIRA link daemon (14/Sep/14 5:05 PM) 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] [docker-build-step] (JENKINS-24699) Create image build step fails with Jenkins prior to 1.553
SCM/JIRA link daemon commented on JENKINS-24699 Create image build step fails with Jenkins prior to 1.553 Code changed in jenkins User: Vojtech Juranek Path: pom.xml http://jenkins-ci.org/commit/docker-build-step-plugin/178a692c55609db98ae39e16e41b4aafb3b5e639 Log: [FIXED JENKINS-24699] Bump to LTS which has commons-io 2.0 as docker-java relies on 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/d/optout.
[JIRA] [docker-build-step] (JENKINS-24551) Docker URL contains invalid version information
Harald Albers commented on JENKINS-24551 Docker URL contains invalid version information Have you tried restarting Jenkins after changing the API version? Currently, the docker client is not properly updated after changes to its configuration. Some changes do apply at once, others require a Jenkins restart. I could reproduce your bungled URLs after removing a previously configured API version. After restarting Jenkins, valid URLs without any version string were produced. 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] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Toru Takahashi commented on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list For example, in traditional Unix OS is not using "UTF-8" but "EUC-JP" or other encoding as Japanese environment. Recently, especially for Linux, uses "UTF-8" encoding as Japanese environment. I have tried the warnings plugin with defaultEncoding modified for encodings of EUC-JP, UTF-8, and Windows-31J. These three cases are Ok for counting ant javac warning messages both english and localized(Japanese). Without any fix, parsing can only handle ASCII characters on the platform other than UTF-8 because many encodings contain ASCII code. And advanced default encoding configuration is ignored. 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] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Daniel Beck commented on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list For example, in traditional Unix OS is not using "UTF-8" but "EUC-JP" or other encoding as Japanese environment. Recently, especially for Linux, uses "UTF-8" encoding as Japanese environment. OS X is UTF-8 for the last few years as well. For some perspective, based on anonymous usage stats, use of Unixes other than Linux and OS X is really low. Of the ~105600 nodes with known OS, only 2250, or ~2.5%, are not Windows, Linux, or OS X; and of those, more than half are Solaris (SunOS). 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] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Daniel Beck edited a comment on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list For example, in traditional Unix OS is not using "UTF-8" but "EUC-JP" or other encoding as Japanese environment. Recently, especially for Linux, uses "UTF-8" encoding as Japanese environment. OS X is UTF-8 for the last few years as well (not claiming it's "traditional Unix", just an extra data point). For some perspective, based on anonymous usage stats, use of Unixes other than Linux and OS X is really low. Of the ~105600 nodes with known OS, only 2250, or ~2.5%, are not Windows, Linux, or OS X; and of those, more than half are Solaris (SunOS). 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] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Ulli Hafner commented on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list I'm not talking about the linux or unix console. My question is if the console log file created by Jenkins uses the default locale and not UTF-8? But since you tested it the suggested fix will be ok indeed! 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] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
SCM/JIRA link daemon resolved JENKINS-24611 as Fixed Warnings plugin, missing AntJavaParser in the parser selection list Change By: SCM/JIRA link daemon (14/Sep/14 9:29 PM) 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] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
SCM/JIRA link daemon commented on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list Code changed in jenkins User: Ulli Hafner Path: .idea/libraries/Maven__org_apache_commons_commons_lang3_3_1.xml analysis-core tasks http://jenkins-ci.org/commit/analysis-suite-plugin/db3e86644600ecedef1315cc00291d2003f154b6 Log: [FIXED JENKINS-24611] Use default encoding when reading the console 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 -- 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] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
SCM/JIRA link daemon commented on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/WarningsPublisher.java warnings.iml http://jenkins-ci.org/commit/warnings-plugin/6f457dce7e88581d733a1bf93da0f1091831d852 Log: [FIXED JENKINS-24611] Use default encoding when reading the console 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 -- 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] [warnings] (JENKINS-24611) Warnings plugin, missing AntJavaParser in the parser selection list
Ulli Hafner commented on JENKINS-24611 Warnings plugin, missing AntJavaParser in the parser selection list If you still want to add a good Japanese test case feel free to add a pull request... 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-24614) "unknown format type" on console output
dogfood commented on JENKINS-24614 "unknown format type" on console output Integrated in jenkins_main_trunk #3680 [FIXED JENKINS-24614] Broken format string in Hebrew console output (Revision 07fd5fa45d4b818fc11de97ce99ab6b3423aca85) Result = SUCCESS daniel-beck : 07fd5fa45d4b818fc11de97ce99ab6b3423aca85 Files : core/src/main/resources/hudson/model/Run/console_he.properties 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-16033) Workspace cleaning locks up all workspaces
Daniel Beck commented on JENKINS-16033 Workspace cleaning locks up all workspaces Please consider upgrading Jenkins, e.g. to a recent LTS release. This ensures that we don't waste time investigating long resolved issues. Go to Manage Jenkins » System Log and create a new log recorder. Add the logger hudson.Util on level FINE and save. Then install the Support Core plugin. On 1.563 and up, you can also set the system property hudson.util.RingBufferLogHandler.defaultSize to increase how many messages are retained on the UI as described here. If this happens again, check the log recorder for permissions related messages. Support Core stores custom loggers' logs in Jenkins home, so if too much gets logged and relevant messages disappear too quickly you can still access it from 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] [core] (JENKINS-16451) Workspace cleanup chmods the top-level directory to complete crap
Daniel Beck resolved JENKINS-16451 as Duplicate Workspace cleanup chmods the top-level directory to complete crap This duplicates JENKINS-16033, so resolving as such. I've posted instructions there that may help investigate the cause, so if you're affected by this issue, please go there and take a look. Change By: Daniel Beck (14/Sep/14 9:44 PM) Status: Open Resolved Resolution: Duplicate 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-24700) Dashboard gets broken when creating a new Pipeline View.
Damian Fernandez created JENKINS-24700 Dashboard gets broken when creating a new Pipeline View. Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Sep/14 10:52 PM Description: That happens when I'm creating a new Pipeline view with https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin. It gets fixed when I accept all the changes in the view, but meanwhile the dashboard view gets broken. Could be related to https://issues.jenkins-ci.org/browse/JENKINS-24360? javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.578.jar!/hudson/model/View/index.jelly:42:43: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.578.jar!/lib/hudson/projectView.jelly:67:24: null at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) 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:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
[JIRA] [core] (JENKINS-11982) Separate "Jenkins URL" setting into multiple more specifies URLs (e.g. PUBLIC URL for web access, e-mail link; and PRIVATE URL for slave connection...)
Daniel Beck resolved JENKINS-11982 as Not A Defect Separate "Jenkins URL" setting into multiple more specifies URLs (e.g. PUBLIC URL for web access, e-mail link; and PRIVATE URL for slave connection...) Sigh... What a waste of time this issue was. Open the slave's config form, select Advanced below the launch method, and enter the real host name, followed by a colon, in Tunnel connection through. This was added in 1.253. Change By: Daniel Beck (14/Sep/14 11:33 PM) Status: Open Resolved Resolution: Not A Defect 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-24700) Dashboard gets broken when creating a new Pipeline View.
Daniel Beck resolved JENKINS-24700 as Duplicate Dashboard gets broken when creating a new Pipeline View. Duplicates JENKINS-23749. (Fix is unreleased as of now.) Change By: Daniel Beck (14/Sep/14 11:37 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-24700) Dashboard gets broken when creating a new Pipeline View.
Daniel Beck updated JENKINS-24700 Dashboard gets broken when creating a new Pipeline View. Not a core issue. Change By: Daniel Beck (14/Sep/14 11:37 PM) Component/s: dashboard-view Component/s: core 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] [subversion] (JENKINS-8059) Subversion Plugin does break native svn command line authentication, credentials missing after rewriting auth cache file
Daniel Beck resolved JENKINS-8059 as Fixed Subversion Plugin does break native svn command line authentication, credentials missing after rewriting auth cache file As mentioned in a comment here and JENKINS-12478, this seems to have been fixed around Subversion plugin 1.45. No disputing reports since. If this or a similar issue occurs in Subversion plugin 2.x, please file a new issue. Change By: Daniel Beck (15/Sep/14 12:40 AM) Status: Reopened 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] [git] (JENKINS-24467) ssh not found by git because PATH has been unexpectedly changed
Mark Waite commented on JENKINS-24467 ssh not found by git because PATH has been unexpectedly changed The fix has been merged to the 2.2.x branch and the master branch. It should be first available in the git plugin 2.2.6 release. 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] [master-slave] (JENKINS-4929) windows 7 x86_64 slave fails to launch via DCOM
Daniel Beck resolved JENKINS-4929 as Incomplete windows 7 x86_64 slave fails to launch via DCOM It looks like there's no recent issues with this type of slave launch that isn't covered by the wiki page (the WBEM one was mentioned at least twice in the comments here already), therefore I'm resolving as Incomplete. If you encounter a similar issue on a recent Jenkins version and tried everything on the linked wiki page with no success, please file a new issue and add a link back to this one. Change By: Daniel Beck (15/Sep/14 1:06 AM) Status: Open Resolved Resolution: Incomplete 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] [emma] (JENKINS-6566) Hudson slave agents die/terminate after upgrading to Hudson ver. 1.358 and taking Emma plugin upgrade
Daniel Beck updated JENKINS-6566 Hudson slave agents die/terminate after upgrading to Hudson ver. 1.358 and taking Emma plugin upgrade Change By: Daniel Beck (15/Sep/14 1:08 AM) Labels: remoting 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-18781) Configurable channel timeout for slaves
Daniel Beck updated JENKINS-18781 Configurable channel timeout for slaves Change By: Daniel Beck (15/Sep/14 1:07 AM) Labels: remoting 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-1948) Intermittent slave disconnections with secondary symptoms
Daniel Beck updated JENKINS-1948 Intermittent slave disconnections with secondary symptoms Change By: Daniel Beck (15/Sep/14 1:08 AM) Labels: remoting robustness slave 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-24516) git polling results exception because ssh is not found
Mark Waite commented on JENKINS-24516 git polling results exception because ssh is not found The change from Rob Langley is now on the master branch and the 2.2.x branch and should be in the git plugin 2.2.6 release. 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-24516) git polling results exception because ssh is not found
Mark Waite resolved JENKINS-24516 as Fixed git polling results exception because ssh is not found Change By: Mark Waite (15/Sep/14 2:24 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] [git] (JENKINS-24467) ssh not found by git because PATH has been unexpectedly changed
Mark Waite resolved JENKINS-24467 as Fixed ssh not found by git because PATH has been unexpectedly changed Change By: Mark Waite (15/Sep/14 2:29 AM) Status: Reopened 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] [git] (JENKINS-19029) Add support for gitlist in git scm browser
SCM/JIRA link daemon commented on JENKINS-19029 Add support for gitlist in git scm browser Code changed in jenkins User: Mark Waite Path: src/main/java/hudson/plugins/git/browser/GitList.java src/main/resources/hudson/plugins/git/browser/GitList/config.jelly src/main/resources/hudson/plugins/git/browser/GitList/help-url.html src/test/java/hudson/plugins/git/browser/GitListTest.java http://jenkins-ci.org/commit/git-plugin/3f155233d0964f3c822ce4bb921bd6492672f90e Log: Merge pull request #255 from fauxpark/2.2.x [FIXED JENKINS-19029] GitList browser support Compare: https://github.com/jenkinsci/git-plugin/compare/050de72ae12c...3f155233d096 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-19029) Add support for gitlist in git scm browser
SCM/JIRA link daemon commented on JENKINS-19029 Add support for gitlist in git scm browser Code changed in jenkins User: fauxpark Path: src/main/java/hudson/plugins/git/browser/GitList.java src/main/resources/hudson/plugins/git/browser/GitList/config.jelly src/main/resources/hudson/plugins/git/browser/GitList/help-url.html src/test/java/hudson/plugins/git/browser/GitListTest.java http://jenkins-ci.org/commit/git-plugin/fa7baf40b1643cc4e5319a70a69c69c0cd2b0d5a Log: [FIXED JENKINS-19029] GitList browser support 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-19029) Add support for gitlist in git scm browser
SCM/JIRA link daemon resolved JENKINS-19029 as Fixed Add support for gitlist in git scm browser Change By: SCM/JIRA link daemon (15/Sep/14 3:55 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] [hp-application-automation-tools-plugin] (JENKINS-23180) How to use "HP Application Automation Tools" (Jenkins plugin) through proxy
Amit Bezalel commented on JENKINS-23180 How to use "HP Application Automation Tools" (Jenkins plugin) through proxy what actually happens is that the HpToolsLauncher invokes the HP ALM Scheduler process via COM, which in turn connects to UFT, and starts the run (no ALM connection yet). Now UFT will connect to ALM, download the needed files, run the test and report back to ALM. the plugin doesn't connect to ALM for the running of the test, it only connects to ALM for reading the status of the test during the run. If the test is run, and there is a problem with status reporting you have a problem with the plugin, but i think this is not the case. In any case, to use ALM via proxy you can try the following: (this is info taken from looking in ALM support forums on the web) use WebGateCustomization to bypass the proxy (http://qc_serve:port/qcbin/Apps/WebGateCustomization.exe) add ALM server's url to trusted sites Hope this helps, Amit. 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] [copyartifact] (JENKINS-24626) Parameter values of build selector change when upgrading CopyArtifact
Tom Ghyselinck commented on JENKINS-24626 Parameter values of build selector change when upgrading CopyArtifact Hi ikedam, Thank you for the update! I would be great if you can find a workaround or an alternative way for it! Is it an option to provide the values string-based instead of xml-based? Using custom encoder / decoder? Or provide a custom dumper which does not add the version info? This would allow for some backward compatibility. 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.
