[JIRA] [findbugs] (JENKINS-24289) FindBugs Plugin does not honor setting Only use stable builds as reference being off
Markus Schlegel commented on JENKINS-24289 FindBugs Plugin does not honor setting Only use stable builds as reference being off JENKINS-13458 is kind of what I was looking for, if specific to FindBugs (means setting the flag for findbugs does not set it for all others too). I voted for it. Maybe the tooltip on the flag "Only use stable builds as reference" could better reflect the current behavior. 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-23645) Archiving artifacts does not preserve timestamps if archived on master
Timmy Brolin commented on JENKINS-23645 Archiving artifacts does not preserve timestamps if archived on master Yes, preventing jobs from running on the master solves the problem. 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] [repository-connector] (JENKINS-23946) Artifact Resolver failed to expand tokens for [Artifact...
Benoit Le Gall commented on JENKINS-23946 Artifact Resolver failed to expand tokens for [Artifact... the new version 1.0.1 erase the configuration of the Artifact Resolver :'( 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] [repository-connector] (JENKINS-23946) Artifact Resolver failed to expand tokens for [Artifact...
Dominik Bartholdi commented on JENKINS-23946 Artifact Resolver failed to expand tokens for [Artifact... when upgrading from "1.0.0 to 1.0.1" or "0.8.2 to 1.0.1"? can you please open a new ticket with some more details? 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-jpi-plugin] (JENKINS-24298) Localizer is not generating Messages classes
Daniel Spilker created JENKINS-24298 Localizer is not generating Messages classes Issue Type: Bug Assignee: abayer Components: gradle-jpi-plugin Created: 18/Aug/14 8:38 AM Description: The Gradle JPI plugin is not re-generating the Messages classes in all cases. E.g. when switching branches which contain different Messages.properties. Gradle skips the tasks because it seems to be up-to-date: :job-dsl-plugin:localizer UP-TO-DATE Environment: gradle-jpi-plugin 0.5.0, Gradle 1.8 Project: Jenkins Priority: Critical Reporter: Daniel Spilker 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-jpi-plugin] (JENKINS-24298) Localizer is not generating Messages classes
SCM/JIRA link daemon commented on JENKINS-24298 Localizer is not generating Messages classes Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/build.gradle http://jenkins-ci.org/commit/job-dsl-plugin/22cc1be93a94b68b126594082c6bb76a5c153018 Log: fixed JENKINS-24297 by adding a workaround for JENKINS-24298 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] [job-dsl-plugin] (JENKINS-24297) Jobs DSL Plugin Master Branch tests failing
SCM/JIRA link daemon commented on JENKINS-24297 Jobs DSL Plugin Master Branch tests failing Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/build.gradle http://jenkins-ci.org/commit/job-dsl-plugin/22cc1be93a94b68b126594082c6bb76a5c153018 Log: fixed JENKINS-24297 by adding a workaround for JENKINS-24298 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] [repository-connector] (JENKINS-23946) Artifact Resolver failed to expand tokens for [Artifact...
Benoit Le Gall commented on JENKINS-23946 Artifact Resolver failed to expand tokens for [Artifact... when updating from O.8.2 to 1.0.0 then 1.0.0 to 1.0.1. As for more details : the configuration of the part Artifact Resolver is reseted, without the custom 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] [job-dsl-plugin] (JENKINS-24297) Jobs DSL Plugin Master Branch tests failing
Daniel Spilker resolved JENKINS-24297 as Fixed Jobs DSL Plugin Master Branch tests failing This is an issue in the Gradle JPI plugin, see JENKINS-24298. I added a workaround to always clean the generated Messages classes. Change By: Daniel Spilker (18/Aug/14 8:47 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] [maven] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Tim Brust commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap I have updated Guava myself and FindBugs works fine again. There was an update to Guava 15 in Oct 13 https://github.com/jenkinsci/jenkins/commit/d45d18ed4e43057c42c363fe306f3945113f8f80 However, it was reverted again: https://github.com/jenkinsci/jenkins/commit/cfe4b82994f261fe7623becfd2c7505679284026 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] [template-project] (JENKINS-21787) use all the publishers from this project is not triggering a new build
William Bernardet commented on JENKINS-21787 use all the publishers from this project is not triggering a new build The fix for JENKINS-23710 will also covert this issue. 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-timeout] (JENKINS-24299) Maven project build fails to terminate hanging build process
Tobias Oberlies created JENKINS-24299 Maven project build fails to terminate hanging build process Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: build-timeout, maven Created: 18/Aug/14 9:06 AM Description: A "maven project" job started a Maven build which ran into an OOM/PermGen. So after 15 Minutes, the build should have been canceled by the build-timeout-plugin, but this doesn't happen. Jenkins seems to be waiting for some reaction from the zombie process instead of killing it. This is the end of the console output at about 1h after the job started, so 45 min after it should have been terminated: [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ mm-content --- [INFO] Building jar: /Disk1/home/hudson/hudson/jobs/__jobname__/workspace/mm/distribution/dist-mm-sharedcontent/target/mm-content-9.56.0-SNAPSHOT.jar Exception in thread "Channel reader thread: channel" java.lang.OutOfMemoryError: PermGen space Build timed out (after 15 minutes). Marking the build as failed. The forked process it is waiting for is running at 100% CPU load, but it is no longer responding to jstack calls. jstack -F however works and shows the following: hudson@cihudson:~ jstack 7439 7439: Unable to open socket file: target process not responding or HotSpot VM not loaded The -F option can be used when the target process is not responding hudson@cihudson:~ jstack -F 7439 Attaching to process ID 7439, please wait... Debugger attached successfully. Server compiler detected. JVM version is 20.51-b01 Deadlock Detection: java.lang.NullPointerException at sun.jvm.hotspot.oops.InstanceKlass.computeSubtypeOf(InstanceKlass.java:426) at sun.jvm.hotspot.oops.Klass.isSubtypeOf(Klass.java:137) at sun.jvm.hotspot.oops.Oop.isA(Oop.java:100) at sun.jvm.hotspot.runtime.DeadlockDetector.print(DeadlockDetector.java:93) at sun.jvm.hotspot.runtime.DeadlockDetector.print(DeadlockDetector.java:39) at sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:52) at sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:45) at sun.jvm.hotspot.tools.JStack.run(JStack.java:60) at sun.jvm.hotspot.tools.Tool.start(Tool.java:221) at sun.jvm.hotspot.tools.JStack.main(JStack.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.tools.jstack.JStack.runJStackTool(JStack.java:118) at sun.tools.jstack.JStack.main(JStack.java:84) Can't print deadlocks:null Thread 3869: (state = BLOCKED) - org.eclipse.equinox.internal.util.impl.tpt.threadpool.ThreadPoolManagerImpl.timer(int) @bci=0, line=168 (Interpreted frame) - org.eclipse.equinox.internal.util.impl.tpt.timer.TimerQueueNode.run() @bci=38, line=125 (Interpreted frame) - org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run() @bci=101, line=70 (Interpreted frame) Thread 7638: (state = BLOCKED) - sun.misc.Unsafe.park(boolean, long) @bci=0 (Interpreted frame) - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, line=156 (Interpreted frame) - java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await() @bci=42, line=1987 (Interpreted frame) - java.util.concurrent.LinkedBlockingQueue.take() @bci=29, line=399 (Interpreted frame) - java.util.concurrent.ThreadPoolExecutor.getTask() @bci=78, line=957 (Interpreted frame) - java.util.concurrent.ThreadPoolExecutor$Worker.run() @bci=23, line=917 (Interpreted frame) - java.lang.Thread.run() @bci=11, line=662 (Interpreted frame) Thread 7637: (state = BLOCKED) - sun.misc.Unsafe.park(boolean, long) @bci=0 (Interpreted frame) - java.util.concurrent.locks.LockSupport.park(java.lang.Object) @bci=14, line=156 (Interpreted frame) -
[JIRA] [openid] (JENKINS-24288) Noclassdef found in openID plugin
junaid shaikh updated JENKINS-24288 Noclassdef found in openID plugin Change By: junaid shaikh (18/Aug/14 9:18 AM) Assignee: KohsukeKawaguchi Component/s: plugin 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] [gerrit-trigger] (JENKINS-24074) Cannot review for build completed to default Gerrit via REST API
rin_ne updated JENKINS-24074 Cannot review for build completed to default Gerrit via REST API Change By: rin_ne (18/Aug/14 9:41 AM) URL: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/ 167 169 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] [tasks-plugin] (JENKINS-22744) cp1251 encoding issue when viewing Details tab
Dennis F. commented on JENKINS-22744 cp1251 encoding issue when viewing Details tab Ulli, thank you for the fix! Tested in my real environment, works just perfect! The issue can be 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] [buildtriggerbadge] (JENKINS-22366) BuildTriggerBadge should have a dedicated icon for Gerrit Trigger
Baptiste Mathus commented on JENKINS-22366 BuildTriggerBadge should have a dedicated icon for Gerrit Trigger Wouah, didn't even see/remember I was actually the reporter of this issue . Just went back from vacations. Now I remember, I logged it to remember to do it. I'll gather the information in the upcoming days if all goes well. Thanks for pinging. 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] [walldisplay] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Stefan Verhoeff created JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name Issue Type: Bug Assignee: Christian Pelster Components: walldisplay Created: 18/Aug/14 10:23 AM Description: We experienced a crashing Jenkins server after Walldisplay started to report "timeout". Requests to the jobs view API URL at /view/view-name/api/json where timing out. CPU was a 100% and there were many hanging RequestHandler threads. In the logs we found IOExceptions on a job that contains whitespace which lead to a StackOverflowError. After renaming the job to not contain whitespace the issue was solved. Detailed Stacktrace from jenkins.log: Aug 18, 2014 10:21:34 AM hudson.model.RunMap retrieve WARNING: could not load /var/lib/jenkins/jobs/Deploy to dev and run QG/builds/2014-07-22_02-59-43 java.io.IOException: Unable to read /var/lib/jenkins/jobs/Deploy to dev and run QG/builds/2014-07-22_02 -59-43/build.xml at hudson.XmlFile.unmarshal(XmlFile.java:167) at hudson.model.Run.reload(Run.java:323) at hudson.model.Run.init(Run.java:311) at hudson.model.AbstractBuild.init(AbstractBuild.java:177) at hudson.model.Build.init(Build.java:103) at hudson.model.FreeStyleBuild.init(FreeStyleBuild.java:38) at sun.reflect.GeneratedConstructorAccessor94.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl. java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at jenkins.model.lazy.LazyBuildMixIn.loadBuild(LazyBuildMixIn.java:155) at jenkins.model.lazy.LazyBuildMixIn$1.create(LazyBuildMixIn.java:136) at hudson.model.RunMap.retrieve(RunMap.java:218) at hudson.model.RunMap.retrieve(RunMap.java:56) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:671) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:470) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:547) at jenkins.model.lazy.LazyBuildMixIn.getBuildByNumber(LazyBuildMixIn.java:235) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:956) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:144) at hudson.model.Cause$UpstreamCause.onLoad(Cause.java:189) at hudson.model.CauseAction.onLoad(CauseAction.java:124) at hudson.model.Run.onLoad(Run.java:342) at hudson.model.RunMap.retrieve(RunMap.java:219) at hudson.model.RunMap.retrieve(RunMap.java:56) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:671) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:470) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:547) at jenkins.model.lazy.LazyBuildMixIn.getBuildByNumber(LazyBuildMixIn.java:235) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:956) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:144) at hudson.model.Cause$UpstreamCause.onLoad(Cause.java:189) at hudson.model.CauseAction.onLoad(CauseAction.java:124) at hudson.model.Run.onLoad(Run.java:342) at hudson.model.RunMap.retrieve(RunMap.java:219) at hudson.model.RunMap.retrieve(RunMap.java:56) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:671) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:470) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:547) at
[JIRA] [parameterized-trigger] (JENKINS-12204) Add extension point for copy artifact to be able to copy the downstream build instead of the last successful
ikedam assigned JENKINS-12204 to ikedam Add extension point for copy artifact to be able to copy the downstream build instead of the last successful Change By: ikedam (18/Aug/14 10:25 AM) Assignee: huybrechts ikedam 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-12204) Add extension point for copy artifact to be able to copy the downstream build instead of the last successful
ikedam resolved JENKINS-12204 as Duplicate Add extension point for copy artifact to be able to copy the downstream build instead of the last successful Sounds completely same to JENKINS-10861 Change By: ikedam (18/Aug/14 10:26 AM) 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] [jacoco] (JENKINS-23708) Unable to view JaCoCo report and history graph
Tobias Stoeckmann updated JENKINS-23708 Unable to view JaCoCo report and history graph Quick fix, adding a dummy logger. Change By: Tobias Stoeckmann (18/Aug/14 10:35 AM) Attachment: JacocoBuildAction.diff 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-14650) Please add specified by permalink:Latest promotion to the which build option for MATRIX projects
ikedam resolved JENKINS-14650 as Fixed Please add specified by permalink:Latest promotion to the which build option for MATRIX projects Copyartifact 1.31 allows you input the permalink manually. Have a look at JENKINS-22590 for details. Change By: ikedam (18/Aug/14 10:37 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] [jacoco] (JENKINS-23708) Unable to view JaCoCo report and history graph
Tobias Stoeckmann edited a comment on JENKINS-23708 Unable to view JaCoCo report and history graph Hi, we face the same problem. I assume that the issue lies in the transient logger that was introduced with a fix for JENKINS-20440. The code relies on the fact that logger is not null, but after deserialization, it will be null because it is just transient. My quick fix (or to show where the problem is located) just adds a dummy logger, so CoverageReport access a "null object". Works again. But I don't want to imply that it's the correct 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] [docker-build-step] (JENKINS-23704) Control over ports with docker build steps
vjuranek commented on JENKINS-23704 Control over ports with docker build steps Hi, I added two evn. variables: DOCKER_HOST_BIND_PORTS - containes comma separated list of ports to which are bound docker container ports DOCKER_HOST_PORT_$SCHEMA_$PORT - which docker conatiner port is bound to this port (e.g. DOCKER_HOST_PORT_TCP_80 would conatin value 8080 in case that conatiner port 8080 is bound to port 80 on host) Is this what you need? Any suggestion before I release it what to better, to be more user friendly? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-23752) Duplicated Warnings links when used with Flexible Publish plugin
Ulli Hafner updated JENKINS-23752 Duplicated Warnings links when used with Flexible Publish plugin Change By: Ulli Hafner (18/Aug/14 11:17 AM) Component/s: flexible-publish Component/s: warnings 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] [plugin] (JENKINS-24301) Plugins disappearing after update
Christopher Mielke created JENKINS-24301 Plugins disappearing after update Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 18/Aug/14 12:22 PM Description: If I try to update any of the plugins included in the Windows native package, the plugins disappear after restarting Jenkins. Even though the plugins are put into the right directory through Jenkins. The only way to get working plugins, is to manually install the old versions which were already included. This also happens with non-included plugins. Environment: Jenkins Version 1.575 on MS Windows Server 2008 R2 Service Pack 1 Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Christopher Mielke 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-23146) StringIndexOutOfBoundsException on subversion checkout
Nico K. commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout I agree to Shannon and would appreciate a bug fix in 2.4.x. 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] [managed-scripts] (JENKINS-20963) Allow managed scripts to be called from a post build task
Dominik Ruf commented on JENKINS-20963 Allow managed scripts to be called from a post build task Sorry I forgot about this. I haven't worked on this for a while. But here is what I did. https://github.com/domruf/managed-scripts-plugin/tree/trigger_n_postbuild This also allows you to use script triggers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Walter Kacynski updated JENKINS-24287 EnvInject exposes password hashes Change By: Walter Kacynski (18/Aug/14 12:33 PM) Attachment: EnvInject.png Attachment: config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Walter Kacynski commented on JENKINS-24287 EnvInject exposes password hashes I think that I forgot to mention that you need to configure a global password or use job level passwords from this plugin. Doing these options will show the environment variable as injected which cause this security problem. 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-24301) Plugins disappearing after update
Daniel Beck updated JENKINS-24301 Plugins disappearing after update Change By: Daniel Beck (18/Aug/14 12:52 PM) Component/s: core Component/s: plugin 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-24301) Plugins disappearing after update
Daniel Beck commented on JENKINS-24301 Plugins disappearing after update Please provide more information, e.g. Jenkins log 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] [thinBackup] (JENKINS-24302) backup ends before all jobs are backed-up if option Backup build results is switched on
Markus Schlegel created JENKINS-24302 backup ends before all jobs are backed-up if option Backup build results is switched on Issue Type: Bug Assignee: Thomas Fürer Attachments: Jenkins_2014-08-18_14-57-55.jpg Components: thinBackup Created: 18/Aug/14 12:59 PM Description: I am unable to backup my jenkins config using thinBackup as far as I enable the option "Backup build results". I only get one (very old and disabled) job backed up. All newer jobs do not appear in the backup folder. If I uncheck the option "Backup build results", it works (but of course without the build results). Project: Jenkins Priority: Critical Reporter: Markus Schlegel 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-24303) Discarding old data can block several threads removing/reporting unreadable data.
Oliver Gondža commented on JENKINS-24303 Discarding old data can block several threads removing/reporting unreadable data. This old attempt to resolve that is of no use: https://github.com/jenkinsci/jenkins/commit/9fb65a9910df420e064d0bb53baba9eee82453e2#commitcomment-7423766 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-24303) Discarding old data can block several threads removing/reporting unreadable data.
Oliver Gondža created JENKINS-24303 Discarding old data can block several threads removing/reporting unreadable data. Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Aug/14 1:06 PM Description: OldDataMonitor#doUpgrade and OldDataMonitor#doDiscard has a potential to block OldDataMonitor for quite some time. Threads that interact with the monitor via OldDataMonitor.*Listener can get blocked for unacceptable amount of time. Project: Jenkins Priority: Major Reporter: Oliver Gondža 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-24301) Plugins disappearing after update
Christopher Mielke commented on JENKINS-24301 Plugins disappearing after update Here is the Jenkins.err.log Output after trying to update several plugins to their latest release through the Jenkins Interface. INFO: Started initialization Aug 18, 2014 3:41:08 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Inspecting plugin C:\Program Files (x86)\Jenkins\plugins\antisamy-markup-formatter.jpi java.io.IOException: Failed to expand C:\Program Files (x86)\Jenkins\plugins\antisamy-markup-formatter.jpi at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:485) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:151) at hudson.PluginManager$1$3$1.run(PluginManager.java:240) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:885) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: Error while expanding C:\Program Files (x86)\Jenkins\plugins\antisamy-markup-formatter.jpi java.util.zip.ZipException: archive is not a ZIP archive at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:192) at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:132) at hudson.ClassicPluginStrategy.unzipExceptClasses(ClassicPluginStrategy.java:557) at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:482) ... 10 more Caused by: java.util.zip.ZipException: archive is not a ZIP archive at org.apache.tools.zip.ZipFile.positionAtCentralDirectory(ZipFile.java:481) at org.apache.tools.zip.ZipFile.populateFromCentralDirectory(ZipFile.java:320) at org.apache.tools.zip.ZipFile.init(ZipFile.java:186) at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:170) ... 13 more Aug 18, 2014 3:41:08 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Inspecting plugin C:\Program Files (x86)\Jenkins\plugins\credentials.jpi java.io.IOException: Failed to expand C:\Program Files (x86)\Jenkins\plugins\credentials.jpi at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:485) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:151) at hudson.PluginManager$1$3$1.run(PluginManager.java:240) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:885) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: Error while expanding C:\Program Files (x86)\Jenkins\plugins\credentials.jpi java.util.zip.ZipException: archive is not a ZIP archive at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:192) at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:132) at hudson.ClassicPluginStrategy.unzipExceptClasses(ClassicPluginStrategy.java:557) at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:482) ... 10 more Caused by: java.util.zip.ZipException: archive is not a ZIP archive at org.apache.tools.zip.ZipFile.positionAtCentralDirectory(ZipFile.java:481) at org.apache.tools.zip.ZipFile.populateFromCentralDirectory(ZipFile.java:320) at org.apache.tools.zip.ZipFile.init(ZipFile.java:186) at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:170) ... 13 more Aug 18, 2014 3:41:08 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Inspecting plugin C:\Program Files (x86)\Jenkins\plugins\cvs.jpi java.io.IOException: Failed to expand C:\Program Files (x86)\Jenkins\plugins\cvs.jpi at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:485) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:151) at hudson.PluginManager$1$3$1.run(PluginManager.java:240) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Jesse Glick commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Fix is merged to trunk, so why is this not Resolved/Fixed? Is there some outstanding case that remains unfixed? Working on a backport. 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] [gerrit-trigger] (JENKINS-24074) Cannot review for build completed to default Gerrit via REST API
SCM/JIRA link daemon commented on JENKINS-24074 Cannot review for build completed to default Gerrit via REST API Code changed in jenkins User: rinrinne Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/Config.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/config/IGerritHudsonTriggerConfig.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/job/rest/BuildCompletedRestCommandJob.java src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer/index.jelly src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/mock/MockGerritHudsonTriggerConfig.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/21993d2f2f369667693b01465745ab45e67a190e Log: Include selected labels to review input for REST API Message for REST API always includes labels for both code review and verified. But current Gerrit does not have ones for verified by default. It causes that review would be denied if label for verified is not added to gerrit. This patch can add user selected labels to message for REST API. Fix for JENKINS-24074 Task-Url: https://issues.jenkins-ci.org/browse/JENKINS-24074 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-18574) changelog use external path for affected path, not workspace related
SCM/JIRA link daemon commented on JENKINS-18574 changelog use external path for affected path, not workspace related Code changed in jenkins User: Daniel Beck Path: src/main/java/hudson/scm/DirAwareSVNXMLLogHandler.java src/main/java/hudson/scm/SubversionChangeLogSet.java src/main/resources/hudson/scm/SubversionChangeLogSet/index.jelly http://jenkins-ci.org/commit/subversion-plugin/7979b652011cd661f0c0fffec4c4b173838c5784 Log: JENKINS-18574 Fixes for multiple locations in same repo (cherry picked from commit 08ed6c99c7d762b32243bf3121f08b4229e98c8b) 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-13130) Gradle Plugin - Gradle distribution URL has changed
Gregory SSI-YAN-KAI resolved JENKINS-13130 as Fixed Gradle Plugin - Gradle distribution URL has changed Change By: Gregory SSI-YAN-KAI (18/Aug/14 2:15 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] [core] (JENKINS-13093) Update Gradle backend-crawler to new artifacts location
Gregory SSI-YAN-KAI resolved JENKINS-13093 as Fixed Update Gradle backend-crawler to new artifacts location This issue has been fixed with commit: https://github.com/jenkinsci/backend-crawler/commit/7517d64e7eeec2775c86441e6fe32760626d096f#diff-3c3161ef96eeb66ea8060f56589c8437 Change By: Gregory SSI-YAN-KAI (18/Aug/14 2:15 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] [gradle] (JENKINS-21653) Gradle build command not working as Gradle version is unavailable for selection in Configure
Gregory SSI-YAN-KAI commented on JENKINS-21653 Gradle build command not working as Gradle version is unavailable for selection in Configure @Navin, you have to go under Jenkins | Manage Jenkins | Configure system | Gradle 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] [walldisplay] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Christian Pelster commented on JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name I can't reproduce this bug with the current plugin version, do you have some more information about the environment? Which Browser (Version) Jenkins Version Really helpful would be the original request that the browser made to access the jobs API. Regards 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] [walldisplay] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Christian Pelster commented on JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name On the second look on the stacktrace I can see the naginator being active on your system, would it be possible to deactivate it and see if the problem vanishes? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Daniel Beck commented on JENKINS-24287 EnvInject exposes password hashes This still doesn't explain how other users that have Config access to a difference folder on the same master, ... can use this password hash to expose the password and take control of the account 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-24301) Plugins disappearing after update
Daniel Beck commented on JENKINS-24301 Plugins disappearing after update Check the files it's trying to extract. My guess is a proxy configured to not send proper error codes but a "user friendly" error page. If so, fix your proxy settings in Manage Plugins Advanced. 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-24304) Enable/Disable verbose Git command logging in Jenkins build log
Scott Hebert
created JENKINS-24304
Enable/Disable verbose Git command logging in Jenkins build log
Issue Type:
Improvement
Assignee:
Nicolas De Loof
Components:
git
Created:
18/Aug/14 2:58 PM
Description:
The git plugin currently prints out the git commands that it executes.
git rev-parse master^{commit} # timeout=10
In some cases, these commands can be numerous and thus distract the user from other pertinent information in the build log.
It would be very valuable to be able to enable or disable this verbose output via a option in the job configuration.
Project:
Jenkins
Priority:
Minor
Reporter:
Scott Hebert
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Walter Kacynski commented on JENKINS-24287 EnvInject exposes password hashes They can use the CLI to retrieve the config.xml and then paste this hash into the document and then update the job back to jenkins. 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-23146) StringIndexOutOfBoundsException on subversion checkout
Daniel Beck commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Jesse: Fix is incomplete as mentioned in a comment to PR 85, here, here, and here. 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] [maven] (JENKINS-24198) Frequent Stackoverflow
Sven Appenrodt commented on JENKINS-24198 Frequent Stackoverflow I don't know if it's the same root cause but i get a StackOverflow too. Win7, Jenkins 1.575 - latest plugins. Downgrade to 1.574 with same plugins works perfect... The strange thing - it only affects some freestyle projects. ... Caused by: java.lang.StackOverflowError at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:282) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:104) at java.io.PrintStream.write(PrintStream.java:430) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202) at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:263) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:106) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:116) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:203) at java.io.Writer.write(Writer.java:140) at java.util.logging.StreamHandler.publish(StreamHandler.java:192) at java.util.logging.ConsoleHandler.publish(ConsoleHandler.java:88) at java.util.logging.Logger.log(Logger.java:478) at java.util.logging.Logger.doLog(Logger.java:500) at java.util.logging.Logger.log(Logger.java:589) at hudson.model.RunMap.retrieve(RunMap.java:235) at hudson.model.RunMap.retrieve(RunMap.java:56) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:671) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:470) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:547) at jenkins.model.lazy.LazyBuildMixIn.getBuildByNumber(LazyBuildMixIn.java:235) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:956) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:144) at hudson.model.Cause$UpstreamCause.onLoad(Cause.java:189) at hudson.model.CauseAction.onLoad(CauseAction.java:124) at hudson.model.Run.onLoad(Run.java:342) at hudson.model.RunMap.retrieve(RunMap.java:219) at hudson.model.RunMap.retrieve(RunMap.java:56) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:671) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:470) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:547) at jenkins.model.lazy.LazyBuildMixIn.getBuildByNumber(LazyBuildMixIn.java:235) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:956) at hudson.model.AbstractProject.getBuildByNumber(AbstractProject.java:144) at hudson.model.Cause$UpstreamCause.onLoad(Cause.java:189) at hudson.model.CauseAction.onLoad(CauseAction.java:124) at hudson.model.Run.onLoad(Run.java:342) at hudson.model.RunMap.retrieve(RunMap.java:219) at hudson.model.RunMap.retrieve(RunMap.java:56) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:671) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:470) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:547) at jenkins.model.lazy.LazyBuildMixIn.getBuildByNumber(LazyBuildMixIn.java:235) ... 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-23704) Control over ports with docker build steps
Harald Albers commented on JENKINS-23704 Control over ports with docker build steps Thanks, DOCKER_HOST_PORT_$SCHEMA_$PORT is exactly what I need. There is an issue with env resolution, though, see https://github.com/jenkinsci/docker-build-step-plugin/pull/11 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-reviewbot] (JENKINS-24305) ReviewBot can't apply the diff and failed to patch file
Alex Kor
created JENKINS-24305
ReviewBot cant apply the diff and failed to patch file
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
jenkins-reviewbot
Created:
18/Aug/14 3:23 PM
Description:
Hello!
Please help to find solution for the following issue (bug?):
ReviewBot can't apply diff and patch file if modifications has been done in the middle of the file (Jenkins build failed).
In case of addition modifications only to the new line in the END of the file - all is OK. (Jenkins build passed).
Here are details:
1. I've added only one word "#comment" at 3rd line:
1: #!/bin/bash
2: echo "Hello"
3: echo "I am script# 1" #comment --Only word "#comment" has been added.
4: exit
Then git commit and git push.
2. See git log from GIT client:
root@sochi-1:/opt/git_client# git log -p -1 dev
commit f4d46f33fe2f4c5cd41cb938d5152fcff896d473
Author: akoryag
Date: Mon Aug 18 18:17:23 2014 +0400
reviewgroup #review-grouprefs #11: only comment added
diff --git a/_ak.sh b/_ak.sh
index 87295da..39ab760 100644
a/_ak.sh
+++ b/_ak.sh
@@ -1,4 +1,4 @@
#!/bin/bash
echo "Hello"
-echo "I am script# 1"
+echo "I am script# 1" #comment
exit
\ No newline at end of file
3. Check git diff:
root@sochi-1:/opt/git_client# git diff 87295da 39ab760
diff --git a/87295da b/39ab760
index 87295da..39ab760 100644
a/87295da
+++ b/39ab760
@@ -1,4 +1,4 @@
#!/bin/bash
echo "Hello"
-echo "I am script# 1"
+echo "I am script# 1" #comment
exit
\ No newline at end of file
4. Check generated diff file from ReviewBoard "rb17.patch" (the same as above):
diff --git a/_ak.sh b/_ak.sh
index 87295daca19ff8d315fc6079bc2e9628e88b83ca..39ab7607fb59590e2e16e26fcbd77c58a2c27a6a 100644
a/_ak.sh
+++ b/_ak.sh
@@ -1,4 +1,4 @@
#!/bin/bash
echo "Hello"
-echo "I am script# 1"
+echo "I am script# 1" #comment
exit
\ No newline at end of file
5. Jenkins try to build this small script, but fails due to "Failed to apply patch":
Started by command line by anonymous
Building in workspace /opt/jenkins-1.575-0/apps/jenkins/jenkins_home/jobs/freestylesoftwareproject/workspace
Cloning the remote Git repository
Cloning repository git@192.168.207.26:/opt/git/mera-ci-test.git
/usr/bin/git init /opt/jenkins-1.575-0/apps/jenkins/jenkins_home/jobs/freestylesoftwareproject/workspace # timeout=10
Fetching upstream changes from git@192.168.207.26:/opt/git/mera-ci-test.git
/usr/bin/git --version # timeout=10
/usr/bin/git fetch --tags --progress git@192.168.207.26:/opt/git/mera-ci-test.git +refs/heads/:refs/remotes/origin/
/usr/bin/git config remote.origin.url git@192.168.207.26:/opt/git/mera-ci-test.git # timeout=10
/usr/bin/git config remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10
/usr/bin/git config remote.origin.url git@192.168.207.26:/opt/git/mera-ci-test.git # timeout=10
Fetching upstream changes from git@192.168.207.26:/opt/git/mera-ci-test.git
/usr/bin/git fetch --tags --progress git@192.168.207.26:/opt/git/mera-ci-test.git +refs/heads/:refs/remotes/origin/
/usr/bin/git rev-parse refs/remotes/origin/dev^{commit} # timeout=10
/usr/bin/git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10
Checking out Revision f4d46f33fe2f4c5cd41cb938d5152fcff896d473 (refs/remotes/origin/dev)
/usr/bin/git config core.sparsecheckout # timeout=10
/usr/bin/git checkout -f f4d46f33fe2f4c5cd41cb938d5152fcff896d473
/usr/bin/git rev-list 8751e4151bd8839df9ac93b75b7995aa10ed546d # timeout=10
Applying the diff
Failed to apply patch due to:
java.io.IOException: Failed to patch /opt/jenkins-1.575-0/apps/jenkins/jenkins_home/jobs/freestylesoftwareproject/workspace/_ak.sh
at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:250)
at
[JIRA] [git-client] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Scott Hebert updated JENKINS-24304 Enable/Disable verbose Git command logging in Jenkins build log Change By: Scott Hebert (18/Aug/14 3:26 PM) Component/s: git-client Component/s: git 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] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10
Jesse Glick commented on JENKINS-24214 Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10 Ah, the test mail. Sorry I missed that. 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] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10
Jesse Glick started work on JENKINS-24214 Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10 Change By: Jesse Glick (18/Aug/14 3:33 PM) Status: Open InProgress 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] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10
Jesse Glick assigned JENKINS-24214 to Jesse Glick Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10 Change By: Jesse Glick (18/Aug/14 3:33 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Daniel Beck commented on JENKINS-24287 EnvInject exposes password hashes Thanks for the explanation, makes sense. passwords should probably be hidden from this output completely, or just have the value (password hidden) or similar. 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] [maven] (JENKINS-24198) Frequent Stackoverflow
Daniel Beck resolved JENKINS-24198 as Duplicate Frequent Stackoverflow Duplicates JENKINS-24161 Change By: Daniel Beck (18/Aug/14 3:38 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] [maven] (JENKINS-24198) Frequent Stackoverflow
Daniel Beck updated JENKINS-24198 Frequent Stackoverflow Missed the UpstreamCause, was actually a core issue. 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-19304) Gradle plugins seems to ignore JDK configured for job
Gregory SSI-YAN-KAI commented on JENKINS-19304 Gradle plugins seems to ignore JDK configured for job I did not reproduced with Jenkins 1.571 and Gradle plugin 1.24 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] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10
James Nugent commented on JENKINS-24214 Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10 Re: above tests, the script returns my password correctly. I didn't realise it was actually sending emails as was setting it up for the first time, but that's useful to know! 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] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10
Daniel Beck commented on JENKINS-24214 Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10 Jesse: Looks like just a wrong @QueryParameter name? 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] [walldisplay] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Daniel Beck resolved JENKINS-24300 as Fixed Stackoverflow after IOException due to whitespace in Job name Resolved in https://github.com/jenkinsci/naginator-plugin/commit/6789567dd81904efa775019c7b114144238612ec Just needs a new plugin release. Change By: Daniel Beck (18/Aug/14 3:52 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] [gradle] (JENKINS-17441) can't build plugin with java 7
Gregory SSI-YAN-KAI resolved JENKINS-17441 as Fixed cant build plugin with java 7 I've sucessfully built gradle plugin 1.24 and 1.25-SNAPSHOT with jdk1.7.0_51-64b Change By: Gregory SSI-YAN-KAI (18/Aug/14 3:54 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] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10
SCM/JIRA link daemon commented on JENKINS-24214 Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10 Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/tasks/Mailer.java src/main/resources/hudson/tasks/Mailer/global.jelly http://jenkins-ci.org/commit/mailer-plugin/afbe1ff7d12991d3b749660542aa24af9a576b70 Log: FIXED JENKINS-24214 SECURITY-152 fix broke test email sending. 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] [naginator] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Daniel Beck updated JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name Change By: Daniel Beck (18/Aug/14 3:54 PM) Assignee: ChristianPelster NicolasDeLoof Component/s: naginator Component/s: walldisplay 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-20965) SSH CLI -v (console output) option causes high master CPU utilization
Jesse Glick commented on JENKINS-20965 SSH CLI -v (console output) option causes high master CPU utilization @walterk82 any particular reason you assigned this to yourself? Steven did the 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] [core] (JENKINS-20965) SSH CLI -v (console output) option causes high master CPU utilization
Walter Kacynski commented on JENKINS-20965 SSH CLI -v (console output) option causes high master CPU utilization @jglick Nope, I was the reporter so I just closed 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] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10
Jesse Glick commented on JENKINS-24214 Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10 Fixed in 1.11. 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-20965) SSH CLI -v (console output) option causes high master CPU utilization
Jesse Glick commented on JENKINS-20965 SSH CLI -v (console output) option causes high master CPU utilization Somehow you assigned it to yourself in the process. Not sure if we really use the “closed” status in JIRA for anything. Generally once a bug is resolved, it is left that way forever. 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-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Andreas Katzig commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials We still encounter this issue, although I read through all comments and have configured everything accordingly and correct (in my opinion). We use Jenkins Jenkins ver. 1.565.1 with Subversion plugin 2.4.1. We're using externals, build servers nodes, I added additional credentials for them, took care of the correct naming with its correct realm and brackets. Every random build does fail with the following exception, and this issue is really getting very very frustrating because the next build is working fine then. The Subversion plugin should be updated to improve the user experience (and functionality). no change for svn://xxx:3688/user/yyy/aaa since the previous build hudson.util.IOException2: revision check failed on svn://xxx:3688/zzz/code/trunk at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:191) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:735) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:873) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.createSaslClient(SVNSaslAuthenticator.java:306) at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.authenticate(SVNSaslAuthenticator.java:92) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.authenticate(SVNConnection.java:194) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.authenticate(SVNRepositoryImpl.java:1275) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1253) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:168) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:179) ... 11 more Finished: FAILURE 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
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Jesse Glick resolved JENKINS-24244 as Incomplete Polling of Mercurial scm stoped working Without information to reproduce it is hard to say what is at fault. Did polling not get triggered at all? Are you using version 1.50 of the plugin, or 1.51-beta-2 (on experimental update center) that has special integration with 1.568+? Seems like you are not using caching. Does polling work for other SCMs? Just checked 1.570 with 1.50 on Linux and polling is working fine (against a Bitbucket test repo) even after a restart. Change By: Jesse Glick (18/Aug/14 4:16 PM) 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] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Richard Mortimer commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I've added a bit of debug to list connected devices (if any) whilst waiting for the emulator to boot up. android-emulator-2.12-SNAPSHOT.hpi Can someone who can reproduce this problem please test this and post the build console output. The code used to produce this build can be found at https://github.com/jenkinsci/android-emulator-plugin/pull/39 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-24306) Jenkins 1.575 regression? Empty build list, but trend shows builds. Stackoverflow in console
Steve Roth created JENKINS-24306 Jenkins 1.575 regression? Empty build list, but trend shows builds. Stackoverflow in console Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 18/Aug/14 4:19 PM Description: Since upgrading to Jenkins 1.575 I have now seen two cases in which jobs are shown with an empty build list (complete with a more... button), yet the trend link shows builds. When the main project page is loaded, I also see stack overflows in the console. The console shows the following stack overflow (repeatable): Aug 18, 2014 8:41:28 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: it.renderList in /view/aaa/view/bbb/view/ccc/job/ddd.MAIN/buildHistory/all. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor742.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:94) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
[JIRA] [core] (JENKINS-24306) Jenkins 1.575 regression? Empty build list, but trend shows builds. Stackoverflow in console
Steve Roth
commented on JENKINS-24306
Jenkins 1.575 regression? Empty build list, but trend shows builds. Stackoverflow in console
On reverting to Jenkins 1.574, the jobs which previously experienced this issue are once again showing build records. So this appears it may be a regression in 1.575.
Possibly relevant: We are using a separate build record root directory, on a NFS server.
Jenkins is configured to use it as follows:
Workspace Root Directory: /foo/jenkinsworkspace/${ITEM_FULLNAME}
This is a local directory
Build Record Root Directory: /foo/jenkinsarchive/${ITEM_FULLNAME}/builds
where /foo/jenkinsarchive is a symlink to a NFS server directory. So the Build Record Root directory is actually on our NFS server.
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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
drazzib commented on JENKINS-17060 Jenkins errors when Remember me on this computer is checked. This issues seems to be a duplicate of JENKINS-23208 and should be closed now 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-24251) No JDK named ‘(Default)’ found
Jesse Glick started work on JENKINS-24251 No JDK named ‘(Default)’ found Change By: Jesse Glick (18/Aug/14 4:38 PM) Status: Open InProgress 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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Kanstantsin Shautsou commented on JENKINS-17060 Jenkins errors when Remember me on this computer is checked. PWAuth-plugin is not fixed as i see, part about crowd2-plugin is resolved. I can look on PWAuth if somebody will test changes. 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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Kanstantsin Shautsou edited a comment on JENKINS-17060 Jenkins errors when Remember me on this computer is checked. PWAuth-plugin is not fixed as i see, part about crowd2-plugin is resolved. I can look at PWAuth if somebody will test changes. 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] [thinBackup] (JENKINS-24302) backup ends before all jobs are backed-up if option Backup build results is switched on
Thomas Fürer commented on JENKINS-24302 backup ends before all jobs are backed-up if option Backup build results is switched on Hi markus, Could it be that you have symbolic links in your buildresult folder? currently not all OS (e.g. windows) do not support symbolic links... 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] [naginator] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Stefan Verhoeff updated JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name Jenkins version is the latest: Jenkins ver. 1.575. Browser is Chrome 36, although this looks like a backend issue. I'm not convinced the issue is caused by Naginator. There are two exceptions in the trace I provided. I split them to make that more clear. The first is says "java.io.IOException: Unable to read" that seems to be caused by the directory named "Deploy to dev and run QG" contains whitespace. The second exception is where Naginator shows up, but that could be just to retry the failed build. The exception that triggered it is "java.io.IOException: Failed to write firstBuild". The NPE fix for Naginator is still a good one, but i'm not sure it fixed the root cause. Change By: Stefan Verhoeff (18/Aug/14 4:43 PM) Affects Version/s: current Description: WeexperiencedacrashingJenkinsserverafterWalldisplaystartedtoreporttimeout.RequeststothejobsviewAPIURLat/view/view-name/api/jsonwheretimingout.CPUwasa100%andthereweremanyhangingRequestHandlerthreads.InthelogswefoundIOExceptionsonajobthatcontainswhitespacewhichleadtoaStackOverflowError.Afterrenamingthejobtonotcontainwhitespacetheissuewassolved.Detailed Stacktrace Stacktrace
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Andreas: Try the following: Create a new log recorder at Manage Jenkins » System Log and add the logger hudson.scm.CredentialsSVNAuthenticationProviderImpl at level FINE. Retry. Check the log output. Anything interesting? 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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Martin Cassidy commented on JENKINS-17060 Jenkins errors when Remember me on this computer is checked. I've just updated and can cofnirm the problem is resolved. 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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Kanstantsin Shautsou commented on JENKINS-17060 Jenkins errors when Remember me on this computer is checked. Resolved what? PWAuth? 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] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Kanstantsin Shautsou updated JENKINS-17060 Jenkins errors when Remember me on this computer is checked. Change By: Kanstantsin Shautsou (18/Aug/14 4:53 PM) Description: Jenkins1.500requiresprincipaltobeUserDetails. StatusCode:500Exception:Stacktrace:java.lang.IllegalArgumentException:Objectofclass[java.lang.String]mustbeaninstanceofinterfaceorg.acegisecurity.userdetails.UserDetails atorg.springframework.util.Assert.isInstanceOf(Assert.java:337) atorg.springframework.util.Assert.isInstanceOf(Assert.java:319) athudson.security.TokenBasedRememberMeServices2.loginSuccess(TokenBasedRememberMeServices2.java:76) atorg.acegisecurity.ui.AbstractProcessingFilter.successfulAuthentication(AbstractProcessingFilter.java:488) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:266) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) athudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) athudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) athudson.plugins.pwauth.PWauthFilter.doFilter(PWauthFilter.java:50) athudson.plugins.pwauth.PWauthFilter.doFilter(PWauthFilter.java:37) athudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) atorg.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) athudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) atwinstone.FilterConfiguration.execute(FilterConfiguration.java:194) atwinstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) atwinstone.RequestDispatcher.forward(RequestDispatcher.java:331) atwinstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) atwinstone.RequestHandlerThread.run(RequestHandlerThread.java:150) atjava.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atwinstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) atjava.lang.Thread.run(Thread.java:722)GeneratedbyWinstoneServletEnginev0.9.10atMonMar0416:59:54EST2013 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] [naginator] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Daniel Beck commented on JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name Err... sorry about that. I just scrolled down to the end Looks like it may be a duplicate of JENKINS-24161, deeply nested UpstreamCauses could be at fault here. Fix is scheduled for 1.576, which should arrive this week. 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] [crowd2] (JENKINS-16703) Too many periodic requests to Crowd server
Kanstantsin Shautsou assigned JENKINS-16703 to Kanstantsin Shautsou Too many periodic requests to Crowd server Change By: Kanstantsin Shautsou (18/Aug/14 4:59 PM) Assignee: ThorstenHeit KanstantsinShautsou 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] [crowd2] (JENKINS-22775) Crowd2 seems to destroy user session when using SSO
Kanstantsin Shautsou assigned JENKINS-22775 to Kanstantsin Shautsou Crowd2 seems to destroy user session when using SSO Change By: Kanstantsin Shautsou (18/Aug/14 4:59 PM) Assignee: ThorstenHeit KanstantsinShautsou 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] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
Kanstantsin Shautsou resolved JENKINS-22136 as Not A Defect Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security Change By: Kanstantsin Shautsou (18/Aug/14 5:02 PM) Status: Open Resolved Assignee: ThorstenHeit KanstantsinShautsou Resolution: NotADefect 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] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Kanstantsin Shautsou started work on JENKINS-17957 Crowd plugin - remember me doesnt work Change By: Kanstantsin Shautsou (18/Aug/14 5:03 PM) Status: Open InProgress 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] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - remember me doesnt work Results of testing refactored plugin: remember me works, need implement SSO auth part and test 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] [naginator] (JENKINS-24300) Stackoverflow after IOException due to whitespace in Job name
Stefan Verhoeff commented on JENKINS-24300 Stackoverflow after IOException due to whitespace in Job name The stack trace does look very similar to JENKINS-24161. It might have been a coincidence that renaming the job fixed the issue for us. That job did not have any problems for the past 4000 builds. We upgraded Jenkins a week ago. I will update the ticket if this issue occurs again with the version 1.576. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
knalli commented on JENKINS-17957 Crowd plugin - remember me doesnt work Regarding the refactored version, may I check a "pre-release" again? 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] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Kanstantsin Shautsou commented on JENKINS-17957 Crowd plugin - remember me doesnt work Next week I will add SSO part and then provide new version. 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] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work
Kanstantsin Shautsou edited a comment on JENKINS-17957 Crowd plugin - remember me doesnt work Next week I will add SSO part and then provide new version for 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/d/optout.
[JIRA] [git-client] (JENKINS-20677) HTTP URLs with variables are not supported when using credentials
Florian Zschocke closed JENKINS-20677 as Wont Fix HTTP URLs with variables are not supported when using credentials I'm closing this issue as it doesn't seem to be relevant anymore. While it is not fixed in the git-client plugin, the behaviour was fixed in the git plugin 2.2.3 which now expands variables in the git repository url before adding credentials. This is an indirect fix that only works for the git plugin. But even if that will still pose a problem for other plugins, the git plugin is the most likely candidate to use the feature and other plugins could just as well expand urls. Change By: Florian Zschocke (18/Aug/14 5:35 PM) Status: Open Closed Resolution: WontFix 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-24251) No JDK named ‘(Default)’ found
SCM/JIRA link daemon resolved JENKINS-24251 as Fixed No JDK named ‘(Default)’ found Change By: SCM/JIRA link daemon (18/Aug/14 5:35 PM) Status: InProgress 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] [core] (JENKINS-24251) No JDK named ‘(Default)’ found
SCM/JIRA link daemon commented on JENKINS-24251 No JDK named ‘(Default)’ found Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/AbstractProject.java core/src/main/java/hudson/model/JDK.java core/src/main/java/jenkins/model/Jenkins.java core/src/main/resources/hudson/model/AbstractProject/configure-common.jelly core/src/main/resources/hudson/model/AbstractProject/configure-common.properties core/src/main/resources/hudson/model/AbstractProject/configure-common_pt_BR.properties http://jenkins-ci.org/commit/jenkins/a2341e6b4c854a0cc183b601acdba7572ad79152 Log: FIXED JENKINS-24251 Do not issue bogus warning about missing default JDK. Compare: https://github.com/jenkinsci/jenkins/compare/c6c64f704c8a...a2341e6b4c85 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] [htmlpublisher] (JENKINS-24307) Publish HTML show 404 http error
HERB SCRUGGS created JENKINS-24307 Publish HTML show 404 http error Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: htmlpublisher Created: 18/Aug/14 5:41 PM Description: Trying to get HTML publisher to work. Console output looks correct that it found the index.html. EnvInject - Loading node environment variables. Building on master in workspace C:\Program Files (x86)\Jenkins\jobs\inheritance\workspace htmlpublisher Archiving HTML reports... htmlpublisher Archiving at PROJECT level c:\report to C:\Program Files (x86)\Jenkins\jobs\inheritance\htmlreports\Test_Report Finished: SUCCESS However when clicking the HTML Link on the job it returns: HTTP ERROR 404 Problem accessing /view/SandBox/job/inheritance/Test_Report/index.html. Reason: Not Found Environment: Windows 7 32 Bit Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: HERB SCRUGGS 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-19326) Groovy script should execute with workspace dir as working directory.
Matt Ferrante commented on JENKINS-19326 Groovy script should execute with workspace dir as working directory. I'm adding a build variable, the AbstractBuild. PR here: https://github.com/jenkinsci/postbuildscript-plugin/pull/12 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] [msbuild] (JENKINS-24276) MSBuild targeting both Debug and Release configurations fails
James Talton closed JENKINS-24276 as Not A Defect MSBuild targeting both Debug and Release configurations fails Please ignore this. I was working off some misinformation. Change By: James Talton (18/Aug/14 5:46 PM) Status: Open Closed Resolution: NotADefect 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.
